Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Troubleshoot common problems on Surface Hub devices running Teams Rooms on Windows.
Common issues are listed in the following table, along with potential workarounds.
| Issue | Description | Workaround |
|---|---|---|
| Microphone not usable on Surface Hub 2S and Hub 3 devices | Incompatibility of the Hub audio driver with a new Voice Clarity Audio Processing Object (APO) introduced in Windows 24H2 (build 26100.5074 or newer) caused the microphone to become unusable and stuck at 0% volume. | To address this issue: 1. Launch the Device Manager 2. Expand the Audio Processing Objects category 3. Right-click on Voice Clarity, and select Uninstall device 4. When prompted, select the option to Attempt to remove the driver for this device The problematic APO (AudioProcessingObject - 10.0.26100.5074) is no longer offered to Surface Hub devices on Windows Update and won't be reinstalled. |
| Surface Hub 2S device listed in wrong category within the Teams admin center | After migrating your Surface Hub 2S to the Microsoft Teams Rooms on Windows platform, it still appears in the Surface Hubs (Legacy) section of the Teams admin center. | Within the Teams admin center, go to Teams Devices > Surface Hubs (Legacy), select the relevant devices, and click "Remove" in the action bar at the top. The devices re-register themselves automatically and then appear in the Teams Rooms on Windows category. |
| Surface Hub 2S device has a "stale" Intune object | If your Hub 2S was Intune-enrolled before migrating to the Microsoft Teams Rooms on Windows platform, the prior Windows 10 device record would still exist in Intune. | Within the Intune admin center, go to Devices > All devices, and identify stale device objects based on your established device naming conventions, and an OS build number containing 19045 (for Windows 10 Team). You can delete each such object, as they no longer correspond to the migrated device, which would be Windows 11-based and show up with its own device object if it was Intune-enrolled. |
Contact Support
If you have questions or need help, you can create a support request.