Microsoft fixes Surface Hub boot issues with emergency update

Microsoft fixes Surface Hub boot issues with emergency update

Microsoft has released an emergency update to fix a known issue causing startup failures for some Surface Hub v1 devices running Windows 10.

As the company explained when it acknowledged this issue last week, users see Secure Boot Violation errors on affected devices, prompting them to check the Secure Boot Policy in setup.

These boot problems only impact Surface Hub v1 systems running Windows 10, version 22H2, after installing the June 2025 Windows security update (KB5060533). Microsoft also noted that these boot problems do not affect Surface Hub 2S and Surface Hub 3 devices.

While the company released a mitigation one day after discovering it to ensure that other systems would not be impacted after installing the buggy update, it also rolled out an emergency out-of-band update (KB5063159) to address this issue on Monday.

“This update prevents Surface Hub v1 devices from encountering a start failure issue. The start failure issue was observed when some Surface Hub v1 devices installed the update KB5060533,” Microsoft said.

“On June 11, 2025, we paused the update KB5060533 offering for Surface Hub v1 to prevent new devices from experiencing the failure. If you installed earlier updates, only the new updates contained in this package will be downloaded and installed on your device.”

​​The KB5060533 Windows update behind this issue fixes another bug that triggers unexpected restarts or freezes on some Hyper-V virtual machines with Windows 10, Windows 11, and Windows Server.

Last week, Microsoft issued another emergency update (KB5063060) to address an Easy Anti-Cheat incompatibility issue, causing some Windows 11 24H2 systems to reboot with blue screen of death errors.

Redmond also released security updates for 66 security flaws last Tuesday, including a publicly disclosed Windows SMB privilege escalation vulnerability (CVE-2025-33073) and an actively exploited WebDAV (Web Distributed Authoring and Versioning) zero-day (CVE-2025-33053).

The June 2025 Patch Tuesday Windows updates addressed ten critical vulnerabilities, eight allowing attackers to gain remote code execution on unpatched devices, while the other two can let them escalate privileges.

Patching used to mean complex scripts, long hours, and endless fire drills. Not anymore.

In this new guide, Tines breaks down how modern IT orgs are leveling up with automation. Patch faster, reduce overhead, and focus on strategic work — no complex scripts required.

0 Shares:
Leave a Reply

Your email address will not be published. Required fields are marked *

You May Also Like