You are viewing a single thread.
View all comments View context
6 points

I am so confused. What’s supposed to happen on the 15th reboot?

permalink
report
parent
reply
40 points

The IT guy quits and it’s no longer their problem to fix

permalink
report
parent
reply
8 points

Probably triggers some auto-rollback mechanism I’d guess, to help escape boot loops? I’m just speculating.

permalink
report
parent
reply
28 points

Welp, Ars Technica has another theory:

Microsoft’s Azure status page outlines several fixes. The first and easiest is simply to try to reboot affected machines over and over, which gives affected machines multiple chances to try to grab CrowdStrike’s non-broken update before the bad driver can cause the BSOD. Microsoft says that some of its customers have had to reboot their systems as many as 15 times to pull down the update.

https://arstechnica.com/information-technology/2024/07/crowdstrike-fixes-start-at-reboot-up-to-15-times-and-get-more-complex-from-there/

permalink
report
parent
reply
7 points

Yep. That makes more sense. Thanks!

permalink
report
parent
reply
7 points

That’s some high quality speculation

permalink
report
parent
reply

Technology

!technology@beehaw.org

Create post

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community’s icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

Community stats

  • 2.8K

    Monthly active users

  • 2.9K

    Posts

  • 53K

    Comments