181
To Fix CrowdStrike Blue Screen of Death Simply Reboot 15 Straight Times, Microsoft Says
(www.404media.co)
this post was submitted on 19 Jul 2024
181 points (95.9% liked)
Not The Onion
12200 readers
846 users here now
Welcome
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!
The Rules
Posts must be:
- Links to news stories from...
- ...credible sources, with...
- ...their original headlines, that...
- ...would make people who see the headline think, “That has got to be a story from The Onion, America’s Finest News Source.”
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!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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