Share via


Known issues with Teams Rooms on Windows

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 opens 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.
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.
Xbox application window appears on a Teams Rooms device. In a Teams Rooms on Windows device, when you select Room Controls on the console, an Xbox app window appears. In some cases, this window is followed by a pop-up window that displays the following warning message:

In some cases, this window is followed by a pop-up window that displays the following warning message:

Gaming Services required

The Xbox app is included as part of Windows but shouldn't start automatically.
If you see the warning message, use the following steps to work around the issue:
  1. In the Teams Rooms device console, select More > Settings.
  2. Select Windows Settings.
  3. Sign in as an administrator.
  4. Search for and select Microsoft Store.
  5. Select Library in the navigation menu.
  6. Select Get updates.
  7. After all the applications, including the Xbox app finish updating, restart the Teams Rooms device.


If you don't see a warning message, use the following steps to prevent the Xbox app from starting automatically:
  1. In the Xbox app window that appears, select Sign in > Settings in the menu.
  2. Select General.
  3. Uncheck the Automatically launch app at startup option.
  4. Close the Xbox app window.
Unable to join some Webex meetings When you select the Join button to join a Cisco Webex meeting from a Teams Rooms on Windows device, you're not connected to the meeting and see the home screen on the device instead. No workaround is available at this time. Cisco is investigating the issue.
Automatic remediation in Pro Management portal keeps failing. The built-in remediation in the Microsoft Teams Rooms Pro Management portal to disable the USB peripheral power draining option under Windows USB settings keeps failing with the error message:

Auto Remediation was unable to resolve this issue.
To resolve the issue, implement a manual fix as described in USB Peripheral Power Drain signal is unhealthy.
Lenovo Teams Rooms devices display BitLocker recovery screen. When you try to update Windows from 23H2 to 24H2 on a Lenovo Teams Rooms for Windows device that has BitLocker enabled, the update might fail and you see a BitLocker recovery screen instead. The Windows update to 24H2 on Lenovo devices is blocked due to this issue.

You can safely upgrade the versions of the Teams Rooms app to 5.3.205.0 and 5.4.210.0 on the affected devices that will remain on Windows version 23H2.

If one of these versions of the Teams Rooms app is already installed and the device displays the BitLocker recovery screen, enter the BitLocker recovery key to restore functionality.
Video participants missing from Front row. The Front row view doesn't show all the video participants, and they're missing from the overflow area as well.

The Front row view displays a maximum of five attendees on a single screen, and up to nine attendees on a dual screen. When the maximum number of attendees are already shown on the screen, the extra attendees are represented in the overflow view area. However, when two or more participants turn on their cameras, the remaining video streams might not fit in the Front-of-Room display, and they are not accounted for in the overflow area as well. This issue causes those video participants to appear as "missing" from the meeting.
Use a different meeting view than the Front row view.
All video streams turn off on Front row during a meeting. When you use the Front row view on a Teams Rooms on Windows device, all video streams including the meeting room's video and incoming content turn off in the Front-of-Room display. This issue occurs intermittently when a remote participant turns off their video while content is being shared. Leave and rejoin the Teams meeting from the Teams Rooms device.
USB devices fail intermittently on Teams Rooms devices. On Teams Rooms on Windows devices that use Intel PCH 500, 600, or 700 systems, you hear occasional glitches or unexpected clicking or popping noises in an audio stream. You might also see glitches in a video stream momentarily, and occasionally a USB audio or video device might stop working.

These issues occur if your device experiences USB split transaction issues.
Switch to Admin mode on your Teams Rooms on Windows device and perform step 3 listed in the Resolution section of USB-connected audio or video devices malfunction when connected to specific Intel-based devices. If the script that you run determines that your device is impacted, perform step 4 to add the registry entry as described.
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.
Screen shared from laptop looks blurry on Teams Rooms display. When you start a full screen share from a laptop that has its resolution set to 1920x1200, the display connected to a Teams Room on Windows device is blurry. To work around the issue, set the display resolution on the laptop to 1920x1080.
Settings window doesn't display on the console. On a Teams Rooms on Windows device, when you select the Settings menu on the console, the console display becomes blank and the Settings menu opens in the Front of Room display instead.

This issue occurs on devices that are running version 5.5.129 of the Teams Rooms app, and their console display is not connected permanently to the compute system.
To work around the issue, use the following steps:
  1. Disconnect all Front of Room displays, but keep the console connected.
  2. Select the Settings menu and verify that it displays on the console.
  3. Connect the Front of Room displays again.
File Explorer view appears when Google Meet starts. When you join a Google Meet meeting by using a Teams Rooms on Windows device, the display shows a view of File Explorer briefly before the Google Meet interface appears. No workaround is needed. The view of File Explorer disappears automatically when the meeting finishes loading.
Brief spike in volume after disconnecting from Google Meet. You join a Google Meet meeting by using a Teams Rooms on Windows device. Another user joins the meeting by using a different device such as a laptop, and shares a presentation involving audio. The volume of the presentation audio heard on the Teams Rooms device is low.

If you disconnect the Teams Rooms device while the presentation is ongoing, then for a brief moment while the device disconnects from the meeting, you hear a significant increase in the volume of the presentation audio.
No workaround is available at this time.
Teams Rooms device hangs when trying to join a breakout room. You're invited to a meeting that includes pre-created breakout rooms in the meeting invite. You join the meeting by using a Teams Rooms on Windows device. During the meeting, you join a breakout room and then return to the main meeting. After you switch between the breakout room and the main meeting a few times, the Teams Rooms device becomes unresponsive. It is unable to switch to the breakout room and remains in the main meeting.

This issue might occur on single-display, dual-display and all-in-one (AIO) configurations of Teams Rooms on Windows devices.
The Teams Rooms device will return to regular operation after it restarts. The device restarts as part the nightly maintenance window, but admins can initiate a restart sooner from the Pro Management Portal to fix the issue.

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.
The central part of the console on a Teams Rooms device doesn't respond to touch and mouse input. On some Microsoft Teams Rooms devices such as the Crestron Dell Optiplex 7080 that use a 4k monitor connected as the front-of-room display, the central portion of the display intermittently stops responding to touch and mouse controls.

Despite this issue, the Teams Rooms app is functional and accepts inputs from a connected keyboard.
Contact Microsoft Support for assistance to work around this issue.
Poor audio quality from a Teams Rooms device. You might experience any of the following audio quality issues from a USB microphone or speaker that is connected to your Teams Rooms device:
  • - Echo sent to remote participants on the call.
  • - Low audio quality sent to remote participants on the call.
  • - Decrease in audio quality as the call progresses.
  • - Low volume in speakers within the room.

This issue might be caused when a setting in the audio driver configuration to enhance audio quality is enabled.
To fix the audio quality issue, disable the audio enhancement setting for the attached Teams-certified USB audio device by using the following steps:
  1. Select Settings on the Teams Rooms device console.
  2. Select Windows Settings, and sign in to the Teams Rooms device as an administrator.
  3. Open Control Panel.
  4. Select Hardware and Sound > Sound.
  5. On the Playback tab, select the affected audio device and then select Properties.
  6. Select the Advanced tab.
  7. In the Signal Enhancements section, uncheck Enable audio enhancements, and then select OK.
  8. Select the Recording tab and repeat steps 5, 6 & 7 for the same audio device
  9. Select OK and then close **Control Panel.
  10. Restart the Teams Rooms device.

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 issue occurs because the Teams Rooms app is designed to support only one call at a time.

  • If your organization configured policies to block legacy authentication for the Teams Rooms app, then Teams Rooms on Windows devices, can't join Teams meetings.

  • When you use multiple connected USB cameras of the same make and model with Teams Rooms on Windows, you experience the following issues:

    • Inability to reliably select or control a specific physical camera.
    • Unexpected changes in camera selection, framing behavior, and source switching.
    • Change to the active camera setting after it is disconnected and reconnected, or after the Teams Rooms app or the meeting restart.
    • Intelligent or enhanced framing experiences target the wrong camera.

Support for non-Microsoft Teams devices

For issues with Teams devices offered by providers other than Microsoft, contact their individual sites for 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.