Windows Updates: Two problems solved, one new one created
The Windows security updates from June create a new problem on Surface Hubs. However, two older ones have now been solved.
(Image: heise online / dmk)
Two steps forward, one step back – is how the current situation with the Windows security updates from Microsoft's June Patchday can be summarized. While the updates have undesirable side effects on certain Surface devices, the Redmond-based company has been able to solve two older problems that were previously introduced by other Windows updates.
Microsoft is now warning about the June security update on the Surface Hub v1. These devices may refuse to boot and display the error message:
Secure Boot ViolationInvalid signature detected. Check Secure Boot Policy in Setup
Surface Hub 2S and 3 should not be affected. On June 11, Microsoft claims to have already taken countermeasures to protect other Surface Hub v1s from this fate. However, Microsoft is not discussing what this will look like. Investigations into the cause are still ongoing. Microsoft names Windows 10 22H2 as the affected operating system.
Old side effects eradicated
Meanwhile, Microsoft has been experiencing problems with firewall profiles since the April Patchday updates for Windows Server 2025 domain controllers. Since then, if the machines restart, the use or switching to the domain firewall profile fails. As the default firewall profile is then used, some apps and services running on the DC or devices in the network may fail or be inaccessible. Previously, Microsoft suggested simply restarting the network adapter as a workaround, as this would restore the expected behavior. In the Windows Release Health Notes, Microsoft now writes that the June security update solves the problem.
Videos by heise
The April security updates for Windows Server 2025, 2022, 2019 and 2016 also had another undesirable side effect. Authentication issues with “Windows Hello for Business” occurred in Active Directory operation. These were apparently due to a change in the verification of certificates for Kerberos public key cryptography on domain controllers, which Microsoft introduced to seal security leaks. Microsoft now also claims to have corrected this with the patches for the server versions from June, the company writes in the Windows Release Health Notes.
(dmk)
