Windows 11 April Update Triggers BSOD, Breaks Windows Hello

[Kenrou]

Ever since people installed Microsoft's April cumulative update for Windows 11 24H2 (KB5055523), many have been greeted by a blue screen showing error code 0x18B and the message SECURE_KERNEL_ERROR. What started as a few scattered reports after March's KB5053656 and KB5053598 patches quickly became a widespread frustration once the April release went live. Some PCs reboot every minute or two, while others refuse to start up at all. Microsoft has acknowledged the problem in an updated support notice and is rolling out a Known Issue Rollback (KIR) to strip out the offending code. Home users should see the fix applied automatically within 24 hours, though you can speed things along by signing back in after a crash, opening Settings > Update & Security, and checking for updates up to five times. The rollback won't appear in your update history, but it will install quietly in the background.

Windows 11 April Update Triggers BSOD, Breaks Windows Hello

Ever since people installed Microsoft's April cumulative update for Windows 11 24H2 (KB5055523), many have been greeted by a blue screen showing error code 0x18B and the message SECURE_KERNEL_ERROR. What started as a few scattered reports after March's KB5053656 and KB5053598 patches quickly...

www.techpowerup.com

 

[Woomack]

I wonder how they test all those updates when every cumulative update in the last few months has caused serious issues. We don't even hear about all the problems happening, as many are more business-related, so typical home users can't see them.

 

[Kenrou]

I wonder how they test all those updates when every cumulative update in the last few months has caused serious issues. We don't even hear about all the problems happening, as many are more business-related, so typical home users can't see them.

You're assuming they test it seriously, IMO if they did proper QC most of these would've been caught in time and patched even on crunch. I know full well that the miriad of hardware will always cause problems, but each one of these that came out have been windows breaking bugs, they're becoming as prolific as the Nvidia drivers and AMD before them...

 

[Janus67]

I wonder how they test all those updates when every cumulative update in the last few months has caused serious issues. We don't even hear about all the problems happening, as many are more business-related, so typical home users can't see them.

MS got rid of a significant portion of their QA/QC folks and are using the average user as the test-bed. It's why in our enterprise environment we don't roll updates (outside of emergency critical) for ~2.5 weeks after patch Tuesday.

 

[mackerel]

I saw elsewhere Jim Keller and John Carmack talking about "fail fast" operations. I wonder if that is the operating method for many/most non-critical things these days. Idea is basically it takes a lot of time and resource to get something near "perfect" before releasing it. It costs a lot less in resources and time to get something out there, and fix whatever is broken as needed. Would explain why a lot of games are broken on launch.

 

[Audioaficionado]

I think I'll wait a few months after major updates come out to install them. I do the same for Linux.