Microsoft is investigating a known issue that triggers Secure Boot errors and prevents Surface Hub v1 devices from starting up.
These boot problems only impact Surface Hub v1 systems running Windows 10, version 22H2, after installing the KB5060533 June 2025 Windows security update.
Microsoft says that “Surface Hub v1 devices might fail to start with the following error: ‘Secure Boot Violation. Invalid signature detected. Check Secure Boot Policy in Setup.”
It’s also important to note that this known issue did not impact Surface Hub 2S and Surface Hub 3 devices, according to Redmond.
The company says it released a mitigation one day after discovering the issue, to ensure that other systems would not be impacted after installing the faulty update.
“A mitigation was released on July 11, 2025, that prevents additional Surface Hub v1 devices from encountering this issue,” Microsoft added.
“We have confirmed this issue affects some Surface Hub v1 devices and are continuing to investigate. We will provide more information when it is available.”
The KB5060533 Windows update behind this known issue fixes another bug causing some Hyper-V virtual machines with Windows 10, Windows 11, and Windows Server to freeze or restart unexpectedly.
On Tuesday, Redmond released security updates for 66 security flaws, including an actively exploited WebDAV (Web Distributed Authoring and Versioning) zero-day (CVE-2025-33053) and a publicly disclosed Windows SMB privilege escalation vulnerability (CVE-2025-33073).
In all, 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 enable privilege escalation.
This week, Microsoft also released an emergency Windows 11 24H2 update (KB5063060) to address an Easy Anti-Cheat incompatibility issue that caused some systems to restart with blue screen of death (BSOD) errors.
Source link