CrowdStrike states: "The issue has been identified, isolated and a fix has been deployed." It would seem that the official fix is as follows:
Workaround Steps:
Boot Windows into Safe Mode or the Windows Recovery Environment
Navigate to the C:\Windows\System32\drivers\CrowdStrike directory
Locate the file matching “C-00000291*.sys”, and delete it.
Boot the host normally.
As someone who is not a sysadmin, how the hell is locally logging in to millions of servers and devices stuck in a bootloop a "fix"? I understand that Windows Safe Mode is unavailable in encrypted devices, what do then?
I saw a picture posted of Delta airport personnel going to every single airport check-in terminal and kiosk (like where you weigh your bag) and doing this manual fix.
CrowdStrike states: "The issue has been identified, isolated and a fix has been deployed." It would seem that the official fix is as follows:
As someone who is not a sysadmin, how the hell is locally logging in to millions of servers and devices stuck in a bootloop a "fix"? I understand that Windows Safe Mode is unavailable in encrypted devices, what do then?
I saw a picture posted of Delta airport personnel going to every single airport check-in terminal and kiosk (like where you weigh your bag) and doing this manual fix.
What a clusterfuck!