At 04:09 (UTC) Windows virtual machines on Azure began rebooting and crashing, and at 06:48 Google Compute Engine also reported the issue. At 07:15, Google identified it was the CrowdStrike update at fault. CrowdStrike CEO George Kurtz confirmed that a faulty driver update released by CrowdStrike caused the outage and confirmed that it was not a cyberattack.[l[3! Technical details An update to a configuration file (here called a channel file) issued at 04:09 UTC on 19 July 2024 conflicted with the Windows sensor client, causing affected machines to enter a blue screen of death with the stop code PAGE_FAULT_IN_NONPAGED_AREA . This left machines stuck in a boot loop or in recovery mode.Hosts running Windows 7 or Windows Server 2008 R2 are not affected. Remedy Affected machines could be restored by booting into safe mode or the Windows Recovery Environment and deleting the %windirs \System32\drivers\CrowdStrike\C-00000291x.sys files.As this process must be done locally on each individual machine, it may take days for affected businesses to restore all systems. CrowdStrike reverted the content update at 05:27 UTC, and devices booted after the reversal are not impacted. At 09:45 UTC, CEO George Kurtz confirmed that the fix was deployed.
https://files.mastodon.social/media_attachments/files/112/814/544/854/577/770/original/499f68cc484042e0.png