Soldato
- Joined
- 6 Jan 2013
- Posts
- 22,187
- Location
- Rollergirl
Anyone scoring the day off for this one?
Who are we blaming, Putin..?
![Smile :) :)](/styles/default/xenforo/vbSmilies/Normal/smile.gif)
Who are we blaming, Putin..?
I'm on holiday at the moment but I'm guessing work is affected - trying to connect to some stuff remotely is just giving an server error: unknown message or nothing happening just eventual timeout.
EDIT: Most stuff seems to be working just a small number of services out. Mostly seems to be the external parts of HR and payroll systems having problems.
Where is that file located?The fix:
How to fix the CloudStrike Windows BSOD issue
Fortunately, CloudStrike has since announced at 2:30 a.m. ET that it has identified the update causing the issue and rolled it back. The company also offered a workaround for anyone having problems:
- "Boot Windows into Safe Mode or the Windows Recovery Environment
- "Navigate to the C:\Windows\System32\drivers\CrowdStrike directory
- "Locate the file matching 'C-0000029*.sys', and delete it.
- "Boot the host normally."
CrowdStrike Falcon is mainly used by businesses but some allow their employees to use it.
Yes. Simply renaming the Crowdstrike folder (or deleting the file as posted) and then rebooting the server, fixes it. We have had about 20 of 200 servers affected.
I think the reason Microsoft was mentioned specifically, is becuase it isn't affecting Linux servers with Crowdstrike agents installed, only MS servers.
Thanks, no directory there so can't just be solely Crowd Strike.
- 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.
You should be straight onto the OS drive, if not try a few drive letters till you find the directory.
Depending on the build of the machine, if its been upgraded etc, you can try the following
c:\windows\system32\drivers\crowdstrike
d:\windows\system32\drivers\crowdstrike
even had one machine where it was on x:, no idea how that was built:-
x:\windows\system32\drivers\crowdstrike
Then once in there you can delete the file causing the issue :-
dir C-00000291*.sys
del C-00000291*.sys
Is the drive visible in diskpart? (dunno if you can then use mountvol).
Is the recovery/system partition not on the same disc?
Unlocking Bitlocker from CMD Type either "manage-bde-unlockX: -Password" or "manage-bde-unlockX: -RecoveryPassword."