Forum Discussion
Solved
Microsoft Teams Room version 5.2.115.0 bug: Teams Room account can't login
Hello, I work as an AV integrator and we currently have roughly 100 Microsoft Teams Room machines installed. Since last Tuesday we have been notified of multiple rooms (10 so far) where the Micr...
Hi all!
The below detail will be published as a known issue shortly on our public pages, it's specific to a small group of devices where the Teams Rooms device was unable to automatically install Edge WebView 2 or the Teams Rooms "Skype" user account was modified in an unsupported fashion. If neither of the below solutions resolve your issue, please open a support case with Microsoft.Issue: Teams Rooms console shows "Teams is experiencing an error" immediately after updating to 5.2.xDescription: After updating to Teams Rooms 5.2.115.0, an error message appears on the console which says, "Teams is experiencing an error" and even after subsequent reboots, the application does not recover. NOTE: there are other scenarios this error message could appear, this is specifically for if the device has just updated to 5.2.115.0 and was operating normally prior.Workaround:Manually install "Edge WebView2 Runtime" which is required for Teams Rooms functionality:- On the Teams Rooms device console, select More > Settings.
- Select Windows Settings.
- Sign in as an administrator.
- Open Edge and browse here: https://developer.microsoft.com/en-us/microsoft-edge/webview2/?form=MA13LH#download
- Scroll down and select "x64" under the "Evergreen Standalone Installer"
- Browse to your downloaded .exe, right click it and select "Run as administrator"
- Complete the installation of WebView2 and restart your Teams Rooms device
If the local "Skype" user account on your Teams Room device has been modified: renamed, disabled and replaced with a different account, or replaced with an AD/Microsoft Entra ID account, this has broken your Teams Room device. Modifications to the Skype user account are not supported, the Teams Room device will need to be reset with the factory recovery media and after doing so, the Skype user account must not be modified to ensure proper functionality. This is documented here: Microsoft Teams Rooms security - Microsoft Teams | Microsoft Learn
Hi Everyone
I have similar issues after installing 5.2.115.0.
I installed the update via Teams Room Pro Management portal.
The device is now stuck on the Teams Room sign-in process
There is a message that I have seen before ' It's taking longer than expected. We'll keep trying. You can restart or contact your admin'
This is usually resolved with a reboot, but not this time. Like a few people above I see the message telling me that there is a newer version of Edge installed when I try the Webview 2 fix. I have not modified the local Skype account.
My device is just a lab environment, and it's running on a Surface Pro 6 in a Logitech Smart dock with a base OS that I installed and not a 'supported' build so I can expect some issues, but the fact is the setup has worked fine since I built it in May 2023.
Anyway I will watch this post and also the known issues page for any updates, and will post here if I manage to fix it.
I have similar issues after installing 5.2.115.0.
I installed the update via Teams Room Pro Management portal.
The device is now stuck on the Teams Room sign-in process
There is a message that I have seen before ' It's taking longer than expected. We'll keep trying. You can restart or contact your admin'
This is usually resolved with a reboot, but not this time. Like a few people above I see the message telling me that there is a newer version of Edge installed when I try the Webview 2 fix. I have not modified the local Skype account.
My device is just a lab environment, and it's running on a Surface Pro 6 in a Logitech Smart dock with a base OS that I installed and not a 'supported' build so I can expect some issues, but the fact is the setup has worked fine since I built it in May 2023.
Anyway I will watch this post and also the known issues page for any updates, and will post here if I manage to fix it.
I have exactly the same problem on 2 machines. I’ve installed the updated WebViewer to no avail.