0XC000015C

Fix STATUS_NOT_REGISTRY_FILE (0XC000015C) Fast

Windows Errors Intermediate 👁 7 views 📅 May 27, 2026

This error means Windows can't load a registry hive file. It's almost always a corrupted SAM, SOFTWARE, or SYSTEM file. I'll show you the fix.

You're staring at that error screen, and yeah, it sucks. Windows just refused to boot, and the message is about as helpful as a screen door on a submarine. Let's cut through the noise—here's how to fix STATUS_NOT_REGISTRY_FILE (0XC000015C).

The Fix: Restore Corrupted Registry Hives from Backup

In 90% of cases, this error means one of your registry hive files (usually C:\Windows\System32\config\SAM, SOFTWARE, or SYSTEM) is corrupt. Windows checks that file during boot, and if it can't read it properly, you get 0XC000015C.

  1. Boot from a Windows installation USB or recovery drive. If you don't have one, create it on another PC using the Media Creation Tool.
  2. At the setup screen, click Repair your computer (lower-left corner).
  3. Select Troubleshoot > Command Prompt.
  4. Type notepad and press Enter. This gives you a file explorer you can navigate with.
  5. Go to C:\Windows\System32\config. Look for the RegBack folder. If it's there (Windows 7/8/10 sometimes keeps it), you're golden. Copy the files from RegBack to the parent config folder. Say Yes to overwrite.
  6. If RegBack is empty or missing (common on Windows 10/11), you'll need a different approach. Type these commands one by one, replacing D: with your system drive letter (usually C:):
cd D:\Windows\System32\config
ren SAM SAM.old
ren SYSTEM SYSTEM.old
ren SOFTWARE SOFTWARE.old
copy D:\Windows\System32\config\RegBack\SAM .
copy D:\Windows\System32\config\RegBack\SYSTEM .
copy D:\Windows\System32\config\RegBack\SOFTWARE .

Had a client last month whose entire print queue died because of a corrupt SOFTWARE hive. Same fix, worked like a charm. The key is using the backup from RegBack—Windows automatically saves these every 10 days or so.

If there's no RegBack folder (or it's empty), your next bet is chkdsk and sfc. Still in Command Prompt, run:

chkdsk C: /f
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

This checks for file system corruption and repairs system files. It's not a silver bullet but catches about 10% of cases.

Why This Works

Windows stores your user accounts, security settings, and hardware config in those hive files. When they get corrupted—usually from a sudden power loss, a failing hard drive, or a failed Windows update—the boot loader can't read them. Restoring from RegBack gives you a snapshot of the last healthy state. It's not perfect (you lose changes made since the backup), but it gets you booting again.

If the restore works but you still have problems later, the corruption might be deeper. Run a full hard drive check: chkdsk C: /r. That takes hours but finds bad sectors.

Less Common Variations

Sometimes the error shows up during Windows Update or after a failed driver install. In those cases:

  • Boot into Safe Mode by repeatedly pressing F8 during boot (if still available). Once there, uninstall the last update or driver via Control Panel.
  • Use System Restore from the recovery environment. It rolls back the registry without manual file copies. Type rstrui.exe in Command Prompt to launch it.
  • Check your disk for physical damage. If chkdsk finds bad sectors, replace the drive ASAP. I've seen this error on failing SSDs that otherwise pass SMART checks—don't trust those alone.

If you're running Windows Server (2008 R2 or 2012 R2), I've seen 0XC000015C happen because of antivirus locking the registry hive during backup. Disable third-party AV temporarily and reboot to test.

Prevention

You don't want to deal with this again. Here's how to avoid it:

  • Enable automatic registry backups. Windows does this by default on some versions, but not all. Run this command to force a backup schedule: reg add "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Configuration Manager" /v EnablePeriodicBackup /t REG_DWORD /d 1 /f. Then restart. From that point, C:\Windows\System32\config\RegBack will get updated daily.
  • Use a UPS. Power loss during a registry write is the #1 cause. A $40 UPS saves you hours of headache.
  • Run chkdsk monthly. Automate it with Task Scheduler: schtasks /create /tn "Check Disk" /tr "chkdsk C: /f" /sc monthly /st 03:00.
  • Don't skip Windows updates, but also don't install them the day they release. Wait a week—let others find the bugs first. Failed updates corrupt registry hives more often than you'd think.

That's it. No fluff, no magic. Fix the hive, get back to work.

Was this solution helpful?