Tell HN: I made a shareable one-page site on how to fix the CrowdStrike issue | Hacker News Reader

Tell HN: I made a shareable one-page site on how to fix the CrowdStrike issue

10 pointsjerrygoyal16 comments

Hey everyone,

I just created a shareable one-page site that provides a step-by-step guide to fix the CrowdStrike issue. You can check it out here: https://howtofixcrowdstrikeissue.com

The website is open-source, and you can find the code on GitHub (https://github.com/GorvGoyl/howtofixcrowdstrikeissue.com). It's built using Next.js, Tailwind, and deployed on Vercel.

I hope this helps people who are currently affected by the global CrowdStrike issue. Feel free to contribute or suggest improvements!

View on HN

It is one static page. Even that feedback link is just a link to Github issues. Why did you choose to make this a full app instead of a single HTML file on a server?

It was easier for me to build and manage as I already have my other projects on Vercel built with Next.js.

Everything is in the `index.tsx` page that anyone can edit and raise PR, I'll update the instructions on Github.

That's hilarious. If only there was some way to publish static information on the internet without writing an app.

I once wrote a web page using Microsoft Word, and a few years later used Google Docs to edit it. I'm not going to blame anyone. Sometimes you use the tools that are at hand and call it a day.

In the Bitlocker section, you may want to include this workaround[1] from u/HammerSlo:

1. Cycle through BSODs until you get the recovery screen.

2. Navigate to Troubleshoot>Advanced Options>Startup Settings

3. Press "Restart"

4. Skip the first Bitlocker recovery key prompt by pressing Esc

5. Skip the second Bitlocker recovery key prompt by selecting Skip This Drive in the bottom right

6. Navigate to Troubleshoot>Advanced Options> Command Prompt

7. Type "bcdedit /set {default} safeboot minimal" then press enter.

8. Go back to the WinRE main menu and select Continue.

9. It may cycle 2-3 times.

10. If you booted into safe mode, log in per normal.

11. Open Windows Explorer, navigate to C:\Windows\System32\drivers\Crowdstrike

12. Delete the offending file (STARTS with C-00000291*. sys file extension)

13. Open command prompt (as administrator)

14. Type "bcdedit /deletevalue {default} safeboot", then press enter. 5. Restart as normal, confirm normal behavior.

as well as this child comment and reply:

> I don't have the Startup Settings

>> Are you using Dells? if so this worked for me from another post i found: If you are on Dell and not seeing anything but the x: in command prompt and limited Safe Mode options, go to the UEFI (BIOS) settings and change your storage settings from RAID to AHCI. It will boot loop and you will be put back into the correct version of system recovery.

[1] https://old.reddit.com/r/sysadmin/comments/1e6vx6n/comment/l...

added.

Nice! Just nitpicking:

2.1> After restarting, select option 4 (Safe Mode) or option 5 (Safe Mode with Networking) by pressing the corresponding number on your keyboard.

Why not just recommend 5? Is 4 useful in this case?

3.1> Open Command Prompt:

Is it possible to use the gui version? I'm a mouse person.

3.3> If C: Drive is Not the Windows Drive:

One trick to go to the system32 folder is to use

  cd %SYSTEMROOT%

or to see it

  echo %SYSTEMROOT%

I like that you suggest to just go to the usual folder. 99.99% of Windows computers just use the standard folder.

4.2> Delete the File: Type del C-00000291*.sys

Is there some hidden requirement to not brick your computer, for example that there is at least another C-whatever.sys file in the some folder? (I have no idea about this problem. Just been paranoiac.)

May want to include a link to CrowdstrikeUsbFix (“Fix for Crowdstrike issue with USB Bootdevice”) as well: https://github.com/Broadcast932/CrowdstrikeUsbFix

added.