181
To Fix CrowdStrike Blue Screen of Death Simply Reboot 15 Straight Times, Microsoft Says
(www.404media.co)
We're not The Onion! Not affiliated with them in any way! Not operated by them in any way! All the news here is real!
Posts must be:
Comments must abide by the server rules for Lemmy.world and generally abstain from trollish, bigoted, or otherwise disruptive behavior that makes this community less fun for everyone.
And that’s basically it!
Is anyone able to read the full article? Is this a boot loop OS detection feature?
Sounds like a race condition in a kernel driver. Try it enough times and maybe you can get clear of it once without triggering.
I saw in another thread: sometimes upon booting, the updater has just enough time to grab the fixed update before BSOD so keep trying.
I saw some SysAdmin threads as it was happening say to boot into safe mode, navigate to the affected file, and delete it.
Yeah. That's the easiest, unless the drive is encrypted.
I imagine the folks going for the 15 reboots approach are doing so because it's easier than waiting in line for their IT help desk to deliver them their boot encryption key.
Especially when the encryption keys are all stored on a Windows server that's bootlooped
I haven't been affected by this personally, just curious at this point what the variables are hah
Archive.ph version
bless up thank you