Global IT disruption caused by a defective CrowdStrike Falcon Sensor update

  • SpinRite v6.1 Release #3
    Guest:
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
    /Steve.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

I don’t think the registry key fixes it.

From what I gather, it’s a kernel-level module (driver) that causes the bugcheck.

If disabling the service works to start Windows, great! :) But don’t forget to roll back the update and re-enable the service.
@EdwinG that registry path is where Windows specifics its drivers, really drivers are just a services, I am not up on the details, but I bet in most cases just disabling the Driver would fix things. These are the things loading when you see the Windows circles on boot up. I do not have much experience writing Windows Drivers yet, but my guess is it is not that hard. The funny thing is that typically drivers are test and signed by MS before they will load in to a default modern Windows.

A quick google and I think is tells about that registry path

 
From my understanding (see https://www.crowdstrike.com/blog/technical-details-on-todays-outage/), this was what we used to call "definitions updates" for antivirus software.
This is the kind of base update that one would expect the AV software to receive multiple times per day.
Granted. But my point does not depend on whether the update was to code or data or a ruleset or whatever. The update had the potential to screw things up big time and yet it was blindly trusted. No excuse for that. Reasons, yes. Excuses, no. And, the release did not seem very staggered.
 
  • Like
Reactions: EdwinG
A co-worker of mine took Fri/Mon off and was headed out of town. They drove 3 hours to LAX late Thursday and got to spend much of the night in the airport, & then slept in the car before driving back home. He's here at work today so as not to burn that other vacation day. Oh well.... he's got a story to tell out of it. :)
 
  • Like
Reactions: EdwinG
Crowdstrike and complicit Microsoft show the digital world very clearly and purposefully how MITM's work. Is it a relief that Mac and Liinux didn't get their update pushed out?
:cool::cool::cool:
 
Last edited:
Our county IT admin was kind enough to give 3 guys the day off on Friday because everything was going smoothly on Thursday.
He went in about 2am Friday after the alerts went off and finished the servers about 5, then his other guys not on a day off came in and took care of PCs in the court, govt center, jail and fairground. 600 PCs were finally done about 3pm.