this post was submitted on 19 Jul 2024
142 points (100.0% liked)

Technology

37699 readers
286 users here now

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.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] MagicShel@programming.dev 9 points 3 months ago (2 children)

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

[–] NeatNit@discuss.tchncs.de 30 points 3 months ago (1 children)

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/

[–] MagicShel@programming.dev 8 points 3 months ago

Yep. That makes more sense. Thanks!

[–] NeatNit@discuss.tchncs.de 8 points 3 months ago

That's some high quality speculation