Microsoft has acknowledged a serious flaw in its recent Windows 11 24H2 updates that is triggering widespread Blue Screen of Death (BSOD) errors. The crash, linked to the stop code SECURE_KERNEL_ERROR (0x18B), is affecting a significant number of users globally.
Escalation Following April 2025 Update
Although initial signs of the issue emerged in March 2025—first noted by Windows Latest—it gained serious traction after the release of the April 2025 Patch Tuesday update. The bug has been traced back to three recent updates:
- KB5053598 (March 11 – Patch Tuesday)
- KB5053656 (March 27 – Optional Update)
- KB5055523 (April 8 – Patch Tuesday)
Users have reported that after installing any of these updates, their systems either crash during reboot or enter an endless restart loop, with some devices becoming completely unbootable.
Root of the Problem: Secure Kernel Failure
The crash points to a malfunction in the Secure Kernel, a core part of Windows responsible for security and virtualization services. Initially, Microsoft did not respond, likely due to the limited number of affected users. However, once the problem escalated in April, the company quietly confirmed it through updates to its official support documentation and began a deeper investigation.
Other Reported Issues
- Windows Hello authentication failures, preventing sign-in via PIN or facial recognition
- App compatibility issues, particularly on ARM devices—e.g., Roblox fails to open, and some Citrix applications won’t install
Microsoft’s Temporary Solution: Known Issue Rollback (KIR)
To address the disruption, Microsoft is using its Known Issue Rollback (KIR) mechanism, which disables the problematic portions of the updates through a server-side patch. This is being rolled out automatically via Windows Update to all consumer and unmanaged business devices. According to Microsoft, full rollout may take up to 24 hours.
Users are advised to:
- Keep their devices connected to the internet
- Restart their PCs multiple times to help apply the KIR patch more quickly
In managed IT environments, system administrators must deploy a Group Policy update to reverse the buggy changes manually. This policy can be found under Computer Configuration > Administrative Templates in the Group Policy Editor, with full steps outlined in Microsoft’s documentation.
Long-Term Fix in Progress
While KIR serves as a temporary remedy, Microsoft is working on a permanent fix expected to arrive in an upcoming update. In the meantime, affected users should regularly check for updates and continue rebooting their systems to ensure the rollback is successfully applied.
Summary of Affected Updates and Issues
| Update | Release Date | Main Problems | Mitigation Method |
|---|---|---|---|
| KB5053598 | Mar 11, 2025 | BSOD (SECURE_KERNEL_ERROR) | Auto KIR (server-side) |
| KB5053656 | Mar 27, 2025 | BSOD, Windows Hello issues | KIR / Group Policy |
| KB5055523 | Apr 8, 2025 | BSOD, login errors, app failures | KIR / Group Policy |
Actionable Steps for Users
- Reboot your PC several times and check for updates to apply the fix faster.
- For business devices, IT teams should implement the Group Policy rollback and restart systems.
- Monitor for future patches from Microsoft, particularly in the May 2025 update.
Final Thoughts
Microsoft’s swift implementation of KIR has helped reduce the disruption, but the situation has reignited debates around the stability of rapid-fire Windows updates. As the company works toward a more permanent resolution, users remain cautious about installing future updates without delays or complications.
0 comments:
Post a Comment
If you have any problem regrading this post, leave a comment !