Archive
Archive for July, 2024
Crowdstrike Bug Resolution Instructions
July 19, 2024
Leave a comment
(this blog originally posted at Reveald.com)
How To Resolve The Issue
These instructions were first published by Superuser.com from advice given by Brody N. – Director of Overwatch at CrowdStrike Inc. The Reveald team is actively researching other options and other workflows and will update this blog periodically.
- Boot to Safe Mode or the Command Prompt from the WinRE blue screen:
- Safe Mode:
See advanced repair options → Troubleshoot → Advanced options → Startup Settings → Restart → Options menu: F4 / 4 - WinRE: Command Prompt
See advanced repair options → Troubleshoot → Advanced options → Command Prompt- If a machine is stuck on a BSOD and not auto-booted to WinRE:
- Reboot machine by holding down power button for ~10s
- Once Windows’ bootloader begins loading Windows, repeat 2x
- Windows will auto-boot to WinRE upon two failed attempts by the Windows bootloader to load Windows
- Windows will auto-boot to WinRE upon two failed attempts by the Windows bootloader to load Windows
- If a machine is stuck on a BSOD and not auto-booted to WinRE:
- Safe Mode:
- Delete file matching
C-00000291*.syswithin:%WinDir%\System32\drivers\CrowdStrike- Safe Mode:
- Open an Admin terminal:
+R → Open:powershell→ Ctrl+Shift+OK - Delete file:
Remove-Item -Path "$env:WinDir\System32\drivers\CrowdStrike\C-00000291*.sys" -Force - Reboot:
Shutdown /f /r /t 0
- Open an Admin terminal:
- WinRE Command Prompt:
(C:is usually not the OS partition mount point in WinRE)
- Obtain mount point of the OS partition:
::# Launch DiskPart:
DiskPart
::# List all volumes [partitions]:
Lis Vol
::# Close DiskPart:
Exit - Delete file:
Del /f /q "<OSdriveLetter>:\Windows\System32\drivers\CrowdStrike\C-00000291*.sys" - Reboot:
Close Command Prompt → Continue to Windows <#>
- Obtain mount point of the OS partition:
- Safe Mode:
- Normally boot to Windows
Categories: Uncategorized
crowdstrike, linux, technology, windows

Comments