After a clean install, I can start Teams, login and use it normally for the first run only. But when I close the application and try to restart it later, there is a delay of around 55 seconds, which ends with a request timeout.
I tried to delete the files in the Teams folder and found that the error wouldn't happen the following file was deleted:
%AppData%\Microsoft\Teams\settings.json
However, every time Teams is started, the file is created or overwritten again.
The next step was to find the exact setting within the settings.json file. After I change the enableProcessIntegrityLevel property-value from true to false and save the file, Teams starts once, without the timeout error:
"enableProcessIntegrityLevel":false
What does this value exactly do and how can I fix the problem?
Teams version 1.0 did not have this issue, but I updated to a newer version and cannot downgrade to the version that worked for me.
Some Details:
Teams version: 1.2.00.8864 x64 (last, from 30.03.2019)
Tried on:
- Windows Server 2016 x64 1607 Build (14393.1884)
- Windows Server 2008 R2 x64 7601 Build SP1
- Windows 7 x64 / Windows 10 x64
Error message:
Oh no ... we can't connect to the internet. Check your connection
Error code - Request timeout
Failed to connect to settings endpoint
Teams-Log:
Teams try 7 times to connect somewhere but this fails.
In this tech community thread are some more log files instances from when this error occurs.
EDIT:
Hi, today I found a workaround for the issue :)
Sign out and close any instances of Microsoft Teams running.
Navigate to the following path: %userprofile%\appdata\Roaming\Microsoft\Teams
Create a json file called hooks.json
Use your favourite notepad editor, add the following line to the newly created file:
{"enableProcessIntegrityLevel": false}
Save and close the file.
Now, re-open Microsoft Teams and sign in.
Source: thread on answers.microsoft.com
We will now distribute the hooks.json file via a policy.