Article Details

Free Blue Screens of Death for Windows 11 24H2 users. Microsoft rewards those who patch early with bricks hurled through its operating system. Keeping with its rich history of updates that break Windows in unexpected ways, Microsoft has warned that two recent patches for Windows 11 24H2 are triggering blue screen crashes. The software in question, April cumulative update KB5055523 and March preview update KB5053656, are causing the freeze-ups on devices running Windows 11 24H2, Microsoft said, and appear after either update is installed and the system is rebooted.  "You might encounter a blue screen exception with error code 0x18B indicating a SECURE_KERNEL_ERROR," Microsoft's documentation for both patches reads.  The Azure titan hasn't explained much about the issue, and hasn't responded to our questions about the matter. No permanent fix has been issued yet, with Redmond only suggesting a workaround mitigation that it's working to roll out now.  Microsoft is addressing the issue using a Known Issue Rollback (KIR), a mechanism introduced in 2021 that lets the Excel giant quietly undo borked non-security updates without user intervention. If you're running Windows 11 24H2 on a personal or unmanaged machine, the rollback should apply automatically via Windows Update - though it might take up to 24 hours to kick in. A reboot could help your system grab the fix faster, according to Microsoft. The repair job is somewhat more involved for IT departments managing affected machines.  IT teams dealing with machines hit by this particular BSOD will need to download a Group Policy .msi file from Microsoft's update support pages and follow the documented steps to install it. Once added, the policy will appear under Computer Configuration > Administrative Templates in the Group Policy Editor. The same KIR package applies to both problematic updates. After installation, affected machines must be restarted to apply the rollback, naturally.  Microsoft has developed something of a reputation for smashing Windows all by itself. In recent months, Redmond has managed to push code that made printers spit gibberish, broke USB audio devices, locked users out of their accounts, and threw false error messages even when installs were completed successfully.  To be fair to Microsoft, it clearly has its hands full, pushing Copilot on everyone, so a few bugs are bound to sneak through. Or be ignored, as it turns out: Redmond hasn't even managed to solve a synchronization issue with the OneDrive apps for Windows and macOS that has been happening for more than 10 months.