Microsoft's recent out-of-band update aims to rectify a critical issue introduced by June's Patch Tuesday updates, which left several Surface Hub v1 devices unbootable. The problematic update, identified as KB5060533 for Windows 10 versions 21H2 and 22H2, caused affected devices to display the error message: "Secure Boot Violation: Invalid signature detected. Check Secure Boot Policy in Setup."
Upon recognizing the severity of the issue, Microsoft promptly paused the deployment of KB5060533 for Surface Hub v1 devices on June 11 to prevent further incidents. A week later, the company released a corrective patch to address the problem. Notably, this issue did not impact Surface Hub 2S and Surface Hub 3 models.
The absence of a reliable workaround exacerbated the situation. Microsoft acknowledged the challenge, stating, "We are working on a resolution to recover the limited number of Surface Hub v1 devices that were impacted by this issue and are unable to start. We will provide more information when it is available." Some users attempted to use the disk re-imaging tool, but success was inconsistent. Reports also indicated that Microsoft's Surface team was exploring the use of manufacturing tools to recover affected devices.
This incident underscores the critical importance of thorough testing protocols, especially for updates affecting enterprise hardware. The Surface Hub v1, introduced in 2015, has been a staple in many corporate environments. However, with the Windows 10 Team edition OS reaching its end of support on October 14, 2025, Microsoft has advised organizations to plan for device upgrades or alternative conferencing solutions. Transitioning to newer models like the Surface Hub 3 is recommended to maintain optimal performance, security, and support.
For organizations continuing to use Surface Hub v1 devices, Microsoft suggests utilizing Replacement PC Mode by connecting an external PC. However, this approach does not extend the device's hardware support lifespan. To avoid disruptions, completing the transition before the end of support date is advisable. For guidance on available upgrade options and planning assistance, organizations should contact their Surface device reseller or Microsoft support representative.
This incident serves as a reminder of the complexities involved in maintaining legacy hardware and the necessity of proactive planning for hardware lifecycle management.
Source: theregister.com Microsoft patches the patch that can brick Surface Hub v1 screens
