Known issues: Windows 10 Team 2020 Update

This article lists known issues for Windows 10 Team 2020 Update, the current operating system for Surface Hub.

To ensure Surface Hub receives the latest updates, sign in with an Admin account and select All apps > Settings > Update and Security > Windows Update, and then install all updates.

Issue Description Remedy
Proxy authentication fails when Device Account is entered as domain\alias (on Active Directory configurations). When the Device Account is configured in OOBE/Settings/MDM using the domain\alias format and the device is using the Device Account for proxy authentication, the Device Account is not properly passed to the Proxy. As a result of this configuration, the proxy does not detect the Device Account as a valid user to authenticate and rejects the request. When this occurs the device cannot connect to internal or external networks. No remedy at this time. Surface Hubs configured to use the device account for proxy authentication should not install the 2020 update.
Proxy authentication fails for certain Hub devices. If customers configure Surface Hub using the Device Account for proxy authentication, proxy authentication may not work. When this occurs the device cannot connect to internal or external networks. No remedy at this time. Surface Hubs configured to use the device account for proxy authentication should not install the 2020 update.
Calendar sync fails when device account UPN and SMTP address do not match. Hubs are trying to use SMTP address to authenticate instead of UPN. In this scenario, Exchange stops syncing meetings to the device. As a result, the device does not receive new meetings. Customers can re-configure their device accounts to have UPN and SMTP be equal. Otherwise, devices should not install the 2020 update.
Calendar sync with on-premises mailboxes fails if customer does not support Hybrid Modern Authentication. Hubs are trying to force Hybrid Modern Authentication for on-premises devices when customers have not enabled this in their topologies. In this scenario, Exchange stops syncing meetings to the device. As a result, the device does not receive new meetings. Customers can enable Hybrid Modern Authentication on their on-premises Exchange Server -- but only if their topology allows it. Otherwise, devices should not install the 2020 update.

Learn more: How to configure Exchange Server on-premises to use Hybrid Modern Authentication.
Sign in is impacted when Conditional Access policy settings are applied. When a device is configured using a Compliance policy setting that requires device-level information (for example, “Require Firewall”), a Conditional Access Error 53000 is triggered. When this occurs users cannot sign in to the device. Customers can exclude Compliance policy settings that require device-level information from executing on Surface Hub devices. If this is not possible due to compliance or security restrictions, Hub devices should not install the 2020 update.

Learn more: Use compliance policies to set rules for devices you manage with Intune.
Hub 2S devices are unable to receive driver updates using WSUS. Surface Hub 2S supports Windows Update and Windows Update for Business to distribute drivers; distribution via Windows Server Update Services (WSUS) is not supported. If using WSUS, migrate to Windows Update for Business.

Learn more: What is Windows update for business?
Single sign-on fails for Azure Active Directory joined devices when using a phone to sign in to Surface Hub If an IT Admin has configured the tenant to use passwordless authentication to sign in to Surface Hub and the device is AAD-joined, users cannot sign in using a mobile device such as a phone. Manually sign in to Surface Hub.
Action Center has an unclickable Settings link. This link should not appear in Windows 10 Team and may cause confusion. The functionality is the same as before the 2020 update; the Apps section of the Start menu should be used to launch the Settings app.
Hub 2S Devices reporting all 0s for Serial Number after updating to November 24, 2020 update for Windows 10 Team 2020 for 2S. After upgrading to the November 24 update for the Surface Hub 2S Windows 10 Team 2020 update or installing the Windows 10 Team 2020 recovery image, some devices are reporting all zeros for the Serial Number. This prevents devices from enrolling into MDM providers. Before updating devices with the November 24, 2020 update for Windows 10 Team 2020, ensure the device has installed the September 1, 2020 update for Windows 10 Team Creators Update. Learn more: Surface Hub update history. Note: Devices should have the Surface SMC Firmware update 1.177.139.0 before moving to SMC Firmware update 3.91.139.0. This prevents serial numbers from being set to zero