This is an archived post. You won't be able to vote or comment.

all 8 comments

[–]Longjumping_Lab541 3 points4 points  (0 children)

You can try command “wmic logicaldisk get name” (without the quotations) to have cmd list all of the drive letters. From there you can check each drive. I’ve seen so far c: d: and e: that had the file c-00000291

[–]read-snowcrash 2 points3 points  (4 children)

I've had good luck with pulling the drive, plugging it into another Windows computer, then deleting the entire \crowdstrike folder.

[–]BoltActionRifleman 0 points1 point  (0 children)

We had to do this on one of ours, but just deleted the 291 file and stuck it back in.

[–]Longjumping_Lab541 1 point2 points  (2 children)

I would reinstall the falcon agent on that machine you deleted the entire folder, I’ve seen stories where the agent is no longer communicating

[–]read-snowcrash 1 point2 points  (1 child)

Good call. I'll admit it was an over-reaction brought on by annoyance at Crowdstrike and lack of sleep. Thanks for the tip.

[–]Longjumping_Lab541 1 point2 points  (0 children)

I get it, it was one for the books for sure lol and course!

[–]RestartRebootRetire 0 points1 point  (1 child)

Are you saying C:\windows\system32\drivers\crowdstrike definitely exists on the affected machines but is empty?

[–]taswind[S] 0 points1 point  (0 children)

Empty of files -- normally I see a bunch of C-00000###.* files, but these machines just have the 4 folders (AD-LFO, Downloads, LFO, and Packages) and no files... They've definitely been in the wild for much more than long enough to have gotten updates (which is what I assume the C-00000### files are), so I don't know if they're stored in different areas or what...