STATUS_REGISTRY_CORRUPT 0xC000014C: Real Fixes for a Dead Boot

I know this error is infuriating. You hit the power button, get past the BIOS splash, and then a black screen with STATUS_REGISTRY_CORRUPT and 0xC000014C staring back at you. Windows won't load. No login screen, no desktop, nothing.

Here's what's actually happening: one of the registry hive files — usually SOFTWARE, SYSTEM, or DEFAULT — is damaged. Windows can't read it, so it can't boot. The error itself is a kernel stop code wrapped in a boot failure.

The usual trigger? A bad shutdown (power cut, force-hold on the power button), a failed Windows Update, or a dying drive. I've seen it happen most often after someone yanks a USB drive during a Windows Update reboot. Classic.

You'll need a Windows install USB to run most of these fixes. If you don't have one, grab another PC and make one with the Media Creation Tool. Boot from it, and choose Repair your computer → Troubleshoot → Advanced options. Everything below happens in that menu.

Fix #1: Run System Restore (the fastest fix, when you have a restore point)

If System Protection was on, this is a five-minute fix. No command line, no hive juggling.

1. In the recovery menu, go to Troubleshoot → Advanced options → System Restore.
2. Pick a restore point from before the problem started. Windows shows the date and time of each.
3. Confirm and let it run. It'll take 10–30 minutes.

The catch: System Restore is off by default on many OEM installs. If there are no restore points, move on. Don't waste time trying to create one — you can't do that from the recovery environment.

Fix #2: Restore the registry hive from RegBack (the real fix when Restore is empty)

Windows keeps a backup copy of your registry hives in C:\Windows\System32\config\RegBack. If the live hive is corrupt, you can swap in the backup. This is the fix that actually saves people who have no restore point.

Open Command Prompt from the recovery menu, then run these one at a time. Note: your system drive is often C: in the recovery environment, but double-check by listing drives with dir C:\Windows — if it errors, try D: or E:.

cd C:\Windows\System32\config

copy C:\Windows\System32\config\RegBack\SOFTWARE SOFTWARE.bak
copy C:\Windows\System32\config\RegBack\SYSTEM SYSTEM.bak
copy C:\Windows\System32\config\RegBack\DEFAULT DEFAULT.bak

copy C:\Windows\System32\config\RegBack\SOFTWARE SOFTWARE
copy C:\Windows\System32\config\RegBack\SYSTEM SYSTEM
copy C:\Windows\System32\config\RegBack\DEFAULT DEFAULT

Reboot and see if Windows comes up. Two important caveats: on Windows 10 build 1803 and later, Microsoft stopped populating RegBack automatically — the folder may be empty. Run dir RegBack to check before you get your hopes up. And don't touch SAM, SECURITY, or BCD hives the same way — you'll lock yourself out of your own user account.

If RegBack is empty, let Windows boot into Startup Repair instead. It sometimes rebuilds the BCD and fixable hive links on its own. Just let it run to completion — don't interrupt it even if it sits at 0% for 15 minutes.

Fix #3: Check for a failing drive (when fixes keep failing)

If you've restored the hive and it corrupts again within days, you're not dealing with a software problem. Your drive is dying. Registry corruption that keeps coming back is a classic symptom of failing NAND or bad sectors.

From the recovery Command Prompt:

chkdsk C: /f /r

That scans for bad sectors and repairs what it can. Expect it to take an hour or more on a full drive. Also run:

wmic diskdrive get status,model,size

If it says anything other than OK, back up your data immediately. On a laptop, listen for clicking or grinding — that's the drive telling you it's done. SSDs usually just vanish or throw read errors instead of making noise.

If SMART is failing, this isn't a repair job. Clone the drive to a new one with something like Macrium Reflect (free) or Clonezilla, then run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth on the new drive to clean up leftover damage.

Quick reference

One last thing: if you reach Reset this PC → Keep my files and it errors out too, you're looking at a clean install. Pull the drive, hook it to another PC with a USB adapter, and grab your files before you do anything else. The registry might be toast, but your data almost never is.