Editor's note: This blog post was first published February 24 , 2021 and updated with new information March 5 and March 10.
As announced February 24, the team began delivering the Windows 10 Team 2020 Update to first-generation Surface Hub 55” and 84” devices. We will continue to provide the Windows 10 Team 2020 Update to all first-generation Surface Hub devices as a staged rollout. Using a staged rollout allows our engineers to investigate issues as they arise and ensure the highest quality update experience.
In response to recent customer feedback, we throttled the March 2 rollout to investigate an issue listed in the known issues list. We also released a fix (KB5000749) as a prerequisite to receive the Windows 10 Team 2020 Update. This update repairs a condition that might result in an unbootable state when you upgrade Surface Hub devices to Windows 10 Team 2020 Update.
All Surface Hub v1 devices through Windows Update for Business.
We will continue to provide updates as the rollout continues. If you would like to start your Surface Hub v1 feature update before it is offered via Windows Update, we encourage you to use the Surface Hub Recovery Tool. Instructions are provided below.
Note: If the Windows 10 Team 2020 Update does not appear in the list of available Windows Updates, you can temporarily turn on full telemetry (aka Windows diagnostics). After enabling full telemetry and restarting the device, it may take 24 hours or more before the update appears. To check, open the Settings app from the Start menu, login with an administrator account, and select Updates & Security > Check for updates.
Updating via Surface Hub Recovery Tool
As an alternative to Windows Update, all first-generation Surface Hub devices can be updated from Windows 10 Team, version 1703 (RS2) to the new Windows 10 Team 2020 Update with the Surface Hub Recovery Tool (SHRT) available for download (select SurfaceHub_Recovery_v184.108.40.206.msi). When you run the SHRT tool, you will be prompted to select the 2020 Update image - aka 20H2 - as shown in the following screenshot: