Fix Registry Corruption: \Windows\System32\config\SYSTEM Missing or Corrupt

The fast answer. A screen reading File: \Windows\System32\config\system with “the system registry file is missing or contains errors” means Windows couldn't load its SYSTEM registry hive — the file holds the driver and service configuration Windows needs to start. Microsoft documents this with status 0xc000014c; some PCs show 0xc0000098 instead. It is not a boot-configuration (BCD) problem, so bootrec won't fix it. Boot into Windows Recovery (WinRE) and use System Restore — restore points include the registry, and it's Microsoft's recommended recovery for a corrupt hive. If there's no restore point, check the disk and restore the hive from RegBack only if the backup files aren't empty:

dir C:\Windows\System32\config\RegBack

If SYSTEM there shows 0 bytes, there is no backup to restore — skip to Step 6.

Why this happens

Unclean shutdown — power loss, a forced power-off, or a crash while Windows was writing the registry leaves the hive damaged or not closed correctly. This is the most common cause.
Disk errors — bad sectors or file-system corruption on the Windows volume landed on the hive file.
Interrupted update or driver install — changes to services and drivers are written to the SYSTEM hive; an interruption mid-write can corrupt it.
Manual registry edits or third-party “registry cleaners” that damaged or deleted keys Windows needs at boot.
Failing drive or RAM — if the hive keeps getting corrupted after repairs, suspect hardware.

Step-by-step fix

Step 1 — Get into Windows Recovery (WinRE)

Force three failed boots (power on, then hold the power button as the Windows logo appears, three times) to open Automatic Repair. If the PC stops at the error screen instead, boot from a Windows 10/11 install USB and choose Next → Repair your computer. Then go to Troubleshoot → Advanced options.

Step 2 — Run Startup Repair

Choose Startup Repair and let it finish. It's non-destructive and occasionally clears the problem. If it reports it couldn't repair the PC, continue.

Step 3 — Restore from a System Restore point

In Advanced options, choose System Restore, pick the Windows installation, and select a restore point dated before the error started. Restore points include registry information. Personal files are kept; apps, drivers, updates, and settings changed after that point are undone. If WinRE says there are no restore points, System Protection was off — continue.

Step 4 — Check the Windows volume for disk errors

Open Advanced options → Command Prompt. Drive letters in WinRE often differ from normal Windows — run dir C:\Windows (then D:, E:…) to find the Windows volume. Then check it, replacing C: with that letter:

chkdsk C: /f /r

Reboot and test. If chkdsk reports bad sectors, treat the drive as failing — copy your data off before going further.

Step 5 — Restore the hives from RegBack (only if the backup isn't empty)

Starting with Windows 10 version 1803, Windows no longer backs up the registry to the RegBack folder by default — the files are still there but are 0 KB. Check first:

cd /d C:\Windows\System32
dir config\RegBack

If SYSTEM, SOFTWARE, SAM, SECURITY, and DEFAULT show real sizes (not 0), back up the current hives, then copy the backups over them, answering A (All) when asked to overwrite:

mkdir configBak
copy config configBak
cd config\RegBack
copy * ..\*

Reboot. If any of those files is 0 bytes, do not copy — an empty hive will leave Windows unbootable. The configBak folder lets you undo the copy if it makes things worse.

Step 6 — Last resort: Reset this PC, keeping your files

With no restore point and no usable RegBack copy, the hive can't be rebuilt by hand. Copy irreplaceable data off first, then choose Troubleshoot → Reset this PC → Keep my files. Personal files are kept; apps and settings are removed, so plan to reinstall software.

Data safety: A corrupted registry hive often means the disk took a bad write — sometimes because it's failing. If the files on this machine matter and you have no backup, image the drive to a known-good external disk first. chkdsk /r reads every sector and can push a dying drive over the edge, and copying hives without backing up the originals removes your way back. Never run repairs on the only copy of irreplaceable data, and get your files off before any reset.

GRAM tip: These repairs run in Windows Recovery, which lives on the broken PC or any Windows install USB. Once the machine boots again, plug in GRAM — a free portable repair toolkit that runs from a USB inside Windows — to check the drive's SMART health, read the event logs for the unclean shutdown or disk errors that damaged the hive, and let its AI agent confirm the root cause so the corruption doesn't come back.

Download GRAM free See AI pricing →

FAQ

Can I fix this without a second working computer?

Usually, yes. WinRE lives on the broken PC itself — three failed boots open Automatic Repair, where Startup Repair, System Restore, and Command Prompt are available. If WinRE won't load, boot any Windows install USB and choose Repair your computer. The repair itself needs no second computer. (GRAM runs inside Windows rather than from boot media — use it once the machine boots to verify disk health and confirm the root cause.)

Why is my RegBack folder full of 0 KB files?

By design. Starting with Windows 10 version 1803, Microsoft stopped the automatic registry backup to RegBack to save disk space; the files remain but are empty. Microsoft recommends System Restore for recovering a corrupt hive. You can re-enable the old backup for the future by setting the DWORD EnablePeriodicBackup to 1 under HKLM\System\CurrentControlSet\Control\Session Manager\Configuration Manager and restarting.

Will bootrec /rebuildbcd fix this?

No. bootrec repairs the boot configuration store (BCD), which tells Windows where to start. This error is about the SYSTEM registry hive in \Windows\System32\config, which bootrec doesn't touch. If your screen names \Boot\BCD instead, see the 0xc000014c BCD guide.

Will these repairs delete my files?

Startup Repair, System Restore, and the RegBack copy don't touch personal files. chkdsk /f /r can move damaged fragments into FOUND.000 folders but doesn't wipe the drive. Reset this PC with Keep my files keeps personal files but removes apps and settings. Copy important data off first anyway.