Windows 11 users met with Blue Screen of Death after installing the latest April update
Table of Contents
With support for Windows 10 officially ending on October 14, 2025, many users have started moving over to Windows 11. After this date, Microsoft will no longer provide any important updates for Windows 10, including those that fix security problems.
Because of this, upgrading to Windows 11 has become the only option for people who want to stay protected. But if you recently switched to Windows 11 and installed the latest April update, you might be seeing the dreaded Blue Screen of Death (BSOD). And you’re not the only one, as Microsoft has confirmed that this is a known issue.
Blue Screen of Death error after Windows 11 April update
Unlike Windows 10, which has been around for nearly a decade and has gone through hundreds of patches and fixes, Windows 11 is still relatively new to people. Since its launch, users have reported many issues, including the start menu not working, sound problems, and poor performance in games. This month, Microsoft released a new update called KB5055523, and it seems to be causing Blue Screen of Death errors for some users. The problem started right after users installed the latest patch.
According to Microsoft's official support page, after installing this update and restarting your computer, you might run into a blue screen crash with an error code 0x18B, which points to something called a SECURE_KERNEL_ERROR. What makes things worse is that this update is marked as a mandatory security patch, which means it installs automatically and can't be skipped. So even if you don't want it, your computer might already have it installed.
For now, Microsoft has offered a temporary fix, but it’s not instant. The company is using a system called Known Issue Rollback (KIR) to deal with the issue. This fix will slowly roll out to all affected users, but Microsoft says restarting your PC might help speed up the process.
For businesses with managed computers, IT teams can fix the issue by using a special Group Policy setting, which is listed in the company's official instructions. In any case, at the moment, all you can do is sit back and wait for the fix to apply automatically. Microsoft might also release a patch to address this, but the company hasn’t confirmed anything yet.
About the Author