Microsoft Issues Emergency Fix After Surface Hub v1 Fails to Boot

Install the update ASAP!

Reading time icon 2 min. read


Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more

Windows 10 December Patch Tuesday

Microsoft’s June Patch Tuesday updates caused a major headache for Surface Hub v1 users. After installing updates like KB5060533 for Windows 10, Surface Hub v1 devices were hit with a Secure Boot validation issue that stopped them from starting.

The bug leaves Surface Hub v1 stuck at boot

The issue triggered a “Secure Boot Violation: Invalid signature detected” message, effectively bricking affected units. Surface Hub 2S and 3 weren’t impacted, but Microsoft quickly flagged the problem in its support documentation. A warning was posted: “DO NOT install this update. Instead, install update KB5063159.”

Microsoft paused the rollout of the faulty update for Surface Hub v1, using a safeguard hold similar to one it applies during major Windows version upgrades.

Also read: Microsoft’s June 2025 Patch Tuesday causes DHCP Server issues—Fix incoming

Microsoft pushes out-of-band update to fix it

To fix the issue, Microsoft released a new out-of-band patch yesterday—KB5063159. It contains all the fixes from the original update without the Secure Boot problem.

This update prevents Surface Hub v1 devices from encountering a start failure issue,” Microsoft confirmed. The buggy KB5060533 rollout was officially paused on June 11 to stop the issue from spreading to more devices.

Also read: Windows 11 June 2025 Patch Tuesday update brings system restore changes, fixes, and a font hiccup

The fix installs automatically for affected Surface Hub v1 users. For those who prefer manual installation, it’s also available through the Microsoft Update Catalog.

More about the topics: fix, Microsoft Surface, Update, windows 10

User forum

0 messages