Known issues with Teams Rooms on Windows

Article
05/23/2024
Applies to:

Microsoft Teams

Software issues

Issue	Description	Workaround
Teams Rooms app out of date	The Teams Rooms console displays the system config out of date error.	To fix this issue, use the Microsoft Teams Rooms recovery tool.
Can't access Windows Settings from the desktop right-click menu.	On Teams Rooms devices that are running app version 3.1.98.0 or later versions, any user account that has the Teams Rooms app installed can access Windows Settings only by using the Start menu. If you try to access Windows Settings by using another method, the Teams Rooms app will open instead.	Use one of the following workarounds to access Windows Settings: Select the Settings option from the Start menu. Uninstall the Teams Rooms app for the affected user. Locate the app on the Start menu, right-click it and select Uninstall.
Teams Rooms device loses internet connectivity after installing a feature update for Windows	A Teams Rooms device that is connected to a network, which requires a proxy can't connect to the internet after installing a feature update for Windows, including an upgrade to Windows 11. This issue occurs if the proxy setting for internet access on the affected device is configured for the LocalSystem instead of a system-wide proxy. The Windows feature update deletes the LocalSystem settings. This behavior is by design.	If your device has proxy settings set for the LocalSystem user, transfer those settings to the system-wide proxy settings that are set and maintained through Mobile Device Management (MDM). Alternatively, you can use the Set-WinInetProxy PowerShell cmdlet to configure the system-wide proxy settings. When you use system-wide proxy settings, they won't be affected when you install Windows feature updates on the device in future.
Test service plans display in Teams Rooms Pro and Teams Rooms Basic licenses	IT Admins who assign user licenses in the Microsoft Teams admin center or in Microsoft Entra ID see the following test service plans in Teams Rooms Pro and Teams Rooms Basic licenses: Teams Rooms Test 1 Teams Rooms Test 2	No workaround is required. These service plans don't have any capabilities and can be ignored. They'll continue to display for the lifetime of the two SKUs.
Teams Rooms device console display shows only a Refresh button.	On devices that are running version 4.17.x.x of the Teams Rooms for Windows app, you might see a black screen with a Refresh button on the console intermittently after the system has been idle for some time.	Select the Refresh button to restore the console display. If you see the black screen both in the front-of-room display and on the console, select the Refresh button on the console display to restore both affected displays.
Mismatch between time and calendar display on Teams Rooms device and Front of Room display	If a Teams Rooms device on Windows is idle for more than 2 hours, the time and calendar display on the device freezes. As a result, there's a mismatch between the time and calendar information in the Front of Room display and on the console. This issue occurs intermittently.	To fix the issue, upgrade the Teams Rooms app to version 4.19.57.0.

Issues with the new Teams Rooms app

Issue	Description	Workaround
New features in the new Teams Rooms app aren't available.	You won't be able to use the new Teams Rooms app unless you install WebView2 runtime version 110.0.1587.63 or higher for all users on your device.	Install WebView2 runtime by using the following steps: Download the Evergreen Bootstrapper file to a location on the device that can be accessed by a local admin account. Right-click the `MicrosoftEdgeWebview2Setup.exe` file and select Run as Administrator. Alternatively, open an elevated remote PowerShell session and run the following command: `.\MicrosoftEdgeWebview2Setup.exe /install /silent`. Restart the device.
Screen sharing from a video teleconferencing device to a Teams Rooms for Windows device doesn't work.	On a Teams Rooms for Windows device that's assigned a Microsoft Teams Pro license and uses SIP and H.323 dialing, the screen shared from a video teleconferencing device might not display after you upgrade to the new Teams Rooms app. This issue occurs when a screen sharing session is stopped and then restarted.	No workaround is available at this time.
Text in QR code displays outside the box.	In the home screen on Teams Rooms on Windows devices that use Germany as the locale, the text in the QR code box to join a meeting overflows the boundary of the box. This issue is purely visual and doesn't impact the functionality of the QR code.	No workaround required.
Home screen display is blank.	On a Teams Rooms for Windows device, when you upgrade the Teams Rooms app from version 4.19.xxx.0 to 5.0.111.0, you might see a blank home screen on the display and a small, black app window on the console. However, both the Microsoft Teams admin center and the Pro Management Portal identify the device as healthy. This issue occurs in Teams Rooms devices that are assigned a legacy Teams Rooms Premium license. Those devices have a Custom theme setting defined by default.	Change the theme from the Custom setting to any other choice that's available. See Make changes to Teams Rooms devices for more information. Restart the Teams Rooms device.
The display from an external video source is blurry.	You have a Teams Rooms on Windows device that is connected to an external video source by an HDMI. When the device is not in a meeting, the video display from the external source is blurry on the home screen of the device. This issue occurs after you upgrade the Teams Rooms on Windows app on the device to version 5.0.111.0.	Restart the Teams Rooms device. The restart will download a configuration update when you sign in to the device which will resolve the issue.
Teams Rooms app doesn't sign in.	In Teams Rooms for Windows devices that are running version 5.0 111.0 of the Teams Rooms app, the assigned Autopilot profile is detected but Autologin fails.	To work around the issue, use one of the following options: Sign in to version 5.0.111.0 of the Teams Rooms app manually. Switch to version 4.19. xxx.0 of the Teams Rooms app.

Hardware issues

Issue	Description	Workaround
During a Coordinated meeting, when the meeting volume is changed by using a room remote, the speaker on a Surface Hub or Teams Rooms device turns on.	For a trusted device such as a Surface Hub or Teams Rooms device that is set up to automatically join a Coordinated meeting when the primary device joins, the speaker turns on when a room remote is used to change the meeting volume. This issue occurs even though the audio settings on the device are turned off, and whether they're enabled or disabled.	Turn off proximity join and room remote capabilities on the trusted devices that automatically join a Coordinated meeting.
When setting up a new Teams Rooms device, the display becomes unresponsive after you initiate the setup process.	The Out of Box Experience (OOBE) for a new Teams Rooms for Windows device freezes in the following scenarios: On a device that uses an OTP, when you select the Get Started button, the UI becomes unresponsive and the button becomes disabled. On a device that's enrolled in Windows Autopilot, the setup process doesn't proceed beyond the opening screen. This issue occurs on devices that have version 4.19.82.0 of the Teams Rooms app. The cause of the issue might be one of the following reasons: The device is not certified for use with Teams Rooms on Windows. The HDMI ingest module on the certified device is not recognized.	Devices that are not certified for use with Teams Rooms on Windows are not supported. If your device is certified for use with Teams Rooms on Windows, unplug the device and plug it in again to retry the recognition process for the HDMI ingest module. If the issue still persists, contact the OEM. Note: This issue is fixed in Teams Rooms devices that have version 5.0.111.0 of the Teams Rooms app.

Issue

Description

Workaround

During a Coordinated meeting, when the meeting volume is changed by using a room remote, the speaker on a Surface Hub or Teams Rooms device turns on.

For a trusted device such as a Surface Hub or Teams Rooms device that is set up to automatically join a Coordinated meeting when the primary device joins, the speaker turns on when a room remote is used to change the meeting volume. This issue occurs even though the audio settings on the device are turned off, and whether they're enabled or disabled.

Turn off proximity join and room remote capabilities on the trusted devices that automatically join a Coordinated meeting.

When setting up a new Teams Rooms device, the display becomes unresponsive after you initiate the setup process.

The Out of Box Experience (OOBE) for a new Teams Rooms for Windows device freezes in the following scenarios:

On a device that uses an OTP, when you select the Get Started button, the UI becomes unresponsive and the button becomes disabled.
On a device that's enrolled in Windows Autopilot, the setup process doesn't proceed beyond the opening screen.

This issue occurs on devices that have version 4.19.82.0 of the Teams Rooms app. The cause of the issue might be one of the following reasons:

The device is not certified for use with Teams Rooms on Windows.
The HDMI ingest module on the certified device is not recognized.

Devices that are not certified for use with Teams Rooms on Windows are not supported.

If your device is certified for use with Teams Rooms on Windows, unplug the device and plug it in again to retry the recognition process for the HDMI ingest module.

If the issue still persists, contact the OEM.

Note: This issue is fixed in Teams Rooms devices that have version 5.0.111.0 of the Teams Rooms app.

Limitations

Teams Rooms doesn't support High-Bandwidth Digital Content Protection (HDCP) input. Using HDCP input might cause issues that affect High-Definition Multimedia Interface (HDMI) ingest functionality, such as video and audio. To avoid these issues, make sure that the HDCP options are turned off for switches that are connected to Teams Rooms.
When you use the Call app on a Teams Rooms device to dial the toll number or conference ID for a Teams meeting, the conference bridge triggers multiple call flows. Because the Teams Rooms app is designed to support only one active call at a time, the call fails.

Instead of using the Call app, join the meeting by using the Join with an ID option and entering the meeting ID.
If you're in a call with another user who is on a Teams Rooms device, you can't transfer the call. This is because the Teams Rooms app is designed to support only one call at a time.

Support for third-party Teams devices

For issues with Teams devices offered by third-party providers, contact their individual sites for support:

Logitech: Logitech Support
Crestron: Crestron Support
Poly: Poly Support

Third-party contact disclaimer

Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

Share via