Microsoft is investigating a known issue that triggers safe boot errors and prevents the surface hub V1 devices from starting devices.
These boot problems affect the surface hub V1 system only, which is going to run Windows 10, version 22H2, after installing KB5060533 June 2025 Windows Security Update.
Microsoft says that “Surface Hub V1 devices may fail to start with the following error: ‘Safe boot violations. Inscribed signatures detected. Check the safe boot policy in the setup.”
It is also important to note that this known issue did not affect the surface hub 2S and surface hub 3 devices according to Redmond.
The company says that it released a mitigation a day after the discovery of the issue, to ensure that other systems would not be affected after installing faulty updates.
“On July 11, 2025, a mitigation was issued, which prevents the additional surface hub V1 devices from facing the issue,” Microsoft added,
“We have confirmed that this problem affects some surface hub V1 devices and is continuing investigation. We will provide more information when available.”
The KB5060533 Windows update behind this known problem fixes another bug, causing some hyper-V virtual machines with Windows 10, Windows 11 and Windows server unexpectedly freeze or restarted.
On Tuesday, Redmund released security updates for 66 security flaws, including an actively exploited webpost (web distributed authoring and versioning) zero (Cve-2025-33053) And a public disclosure Windows SMB Privilege escalation vulnerability (Cve-2025-33073,
Overall, on June 2025 patch on Tuesday, Windows update addressed ten important weaknesses, eight allowed the attackers to obtain distance code execution on unexpected equipment, while the other two are capable of increasing two privileges.
This week, Microsoft also released an emergency Windows 11 24H2 update (KB5063060) to address the issue of an easy anti-chit inconvenience, inspired to restart with some systems Blue Screen of Death (BSOD) errors.