Critical Process Died on Startup Loop – Quick Fix Guide

What's Happening?

You turn on the PC, see the Windows logo, then it crashes to a blue screen with Critical Process Died. It loops like this forever. This is almost always a corrupted system file, a bad driver, or a recent Windows update gone wrong. I've seen this on Windows 10 builds 1909 through 22H2 and Windows 11.

Quick Fix (30 Seconds): Force Startup Repair

No, this isn't a magic reset. But startup repair catches the obvious stuff fast.

Hard power off your PC by holding the power button for 10 seconds. Do this three times total — let it boot, then force it off.
On the fourth boot, Windows will say "Preparing Automatic Repair." Let it run.
Click Advanced Options > Troubleshoot > Advanced Options > Startup Repair.

If this works, you're done. If not, move on.

Moderate Fix (5 Minutes): System Restore

System Restore is your best bet — it backs out whatever broke the system.

Boot to the same Advanced Options menu (force three restarts to get there).
Click Troubleshoot > Advanced Options > System Restore.
Pick a restore point from before the error started showing up. If you don't have any, skip this — someone turned off System Protection.

Warning: System Restore won't touch your personal files, but it might remove apps and drivers you installed after the restore point. That's fine — you can reinstall them later.

I've personally saved at least 20 machines with this method. It's the most reliable fix for this error.

Advanced Fix (15+ Minutes): DISM and SFC from Command Prompt

No restore points? Okay, let's fix the system files manually. This takes longer but works when the above fails.

Boot to Advanced Options again. This time click Troubleshoot > Advanced Options > Command Prompt.
Run this command first (it checks for corruption in the system image):
```
dism /online /cleanup-image /restorehealth /source:WIM:X:\Sources\Install.wim:1 /limitaccess
```
Replace X: with your DVD or USB drive letter (often D:). If you don't have installation media, skip the /source part — it'll use Windows Update instead.
Let it finish. Could take 10-15 minutes. Don't touch the PC.
Then run:
```
sfc /scannow
```
This checks and fixes core system files. Takes another 5 minutes.
Type exit and restart.

If sfc /scannow reports corrupted files but can't fix them, you need a fresh copy of the file. That's when you either reinstall Windows or try the next step.

Last Resort: Reset This PC (30 Minutes)

If none of the above works, your system files are too damaged. Boot to Advanced Options, choose Troubleshoot > Reset This PC. Pick Keep my files — it reinstalls Windows but keeps your documents and photos. You'll need to reinstall apps though.

Prevention Tips

Turn on System Restore now — it's off by default on many PCs. Go to Control Panel > System > System Protection > Configure.
Don't run disk cleanup tools that delete WinSxS files. That's where the backup system files live.
If a Windows update caused this, pause updates for 30 days after you recover.

That's it. Try the quick fix first — it saves time. If not, System Restore usually wins. Only fall back to DISM/SFC if you're comfortable with command line.