Recover a missing or corrupt SYSTEM registry hive with error 0xc000014c

Windows Recovery states that the operating system could not be loaded because the system registry file is missing or contains errors and names \Windows\System32\Config\SYSTEM, commonly with 0xc000014c.

Searchable Windows error codes and exact messages

The critical exact search is File: \Windows\System32\Config\SYSTEM Error code: 0xc000014c together with The operating system couldn't be loaded because the system registry file is missing or contains errors. If the screen instead names \Boot\BCD, use the BCD writeup; 0xc000014c alone does not distinguish the two files.

Use this procedure when the screen names the SYSTEM hive and the Windows volume is readable from WinRE.

Do not use it when the screen names BCD, the disk is unstable, or the only evidence is BAD_SYSTEM_CONFIG_INFO with an otherwise loadable SYSTEM hive and a known bad BCD setting.

The exact Windows build may remain unknown. The named hive, Windows volume, availability of a restore point, and existence and size of any registry backup must be confirmed.

• Windows Recovery Environment or installation media
• Command Prompt
• Readable Windows volume
• Preferably a System Restore point or system image
• A separate backup location for the current hive and transaction logs

Open Repair your computer > Troubleshoot > Advanced options. Use System Restore before attempting manual hive replacement.

1. Record the full code and confirm the screen names:

   \Windows\System32\Config\SYSTEM
   

2. Open Command Prompt and detect the Windows volume:

   diskpart
   list volume
   select volume <Windows-volume-number>
   detail volume
   assign letter=W
   exit
   

3. Inspect the registry directory, including hidden files:

   dir /a W:\Windows\System32\Config
   

4. Record the size and timestamp of SYSTEM, SYSTEM.LOG1, and SYSTEM.LOG2.

5. Test whether the hive can be parsed:

   reg load HKLM\OfflineSystem W:\Windows\System32\Config\SYSTEM
   

6. If the load succeeds, query the control-set selector and unload the hive:

   reg query HKLM\OfflineSystem\Select
   reg unload HKLM\OfflineSystem
   

7. A successful load means the hive is structurally readable; consider FIX-015, an update rollback, or a demonstrated service/driver configuration problem before replacing it.

8. If reg load fails or SYSTEM is missing/zero length, the named-hive diagnosis is confirmed.

9. Check the file system without repairing it yet:

   chkdsk W:
   

10. If storage errors or I/O failures appear, stop and protect the data before attempting registry replacement.

11. Inspect the optional RegBack directory:

dir /a W:\Windows\System32\Config\RegBack

12. On modern Windows 10/11 installations, RegBack files are commonly zero bytes because automatic registry backup was disabled by design beginning with Windows 10 version 1803. A zero-byte file is not a backup.

Proceed in this order.

Branch A — Use System Restore

1. Return to Advanced options > System Restore.
2. Select the affected Windows installation.
3. Choose a restore point created before the hive failure.
4. Review affected programs and complete the restore.
5. Restart and test twice.

System Restore is preferred because it restores a coordinated system state rather than replacing one hive without its related configuration.

Branch B — Remove a directly preceding Windows update

Use this branch when the SYSTEM hive loads successfully but the error began during or immediately after an update.

1. Return to Advanced options > Uninstall Updates.
2. Select Uninstall latest quality update, or the feature-update option when that was the trigger and the option is available.
3. Complete the rollback and restart.

Do not use update removal as a substitute for a missing or structurally unreadable hive.

Branch C — Restore a verified nonzero RegBack SYSTEM hive

Use this only when System Restore is unavailable, the active SYSTEM hive cannot load, and RegBack\SYSTEM is nonzero, plausibly sized, and dated before the failure.

1. Create a backup directory:

   md W:\BootRepairBackup
   

2. Preserve the current hive and transaction logs when they exist:

   copy W:\Windows\System32\Config\SYSTEM W:\BootRepairBackup\SYSTEM.before-0xc000014c
   copy W:\Windows\System32\Config\SYSTEM.LOG1 W:\BootRepairBackup\SYSTEM.LOG1.before-0xc000014c
   copy W:\Windows\System32\Config\SYSTEM.LOG2 W:\BootRepairBackup\SYSTEM.LOG2.before-0xc000014c
   

3. Recheck the candidate backup:

   dir W:\Windows\System32\Config\RegBack\SYSTEM
   

4. Stop if it shows zero bytes, is newer than the failure, or is implausibly small compared with the current hive.

5. Rename the current transaction logs so they cannot be replayed against the restored hive:

   ren W:\Windows\System32\Config\SYSTEM.LOG1 SYSTEM.LOG1.before-restore
   ren W:\Windows\System32\Config\SYSTEM.LOG2 SYSTEM.LOG2.before-restore
   

6. Copy the verified backup into place:

   copy /y W:\Windows\System32\Config\RegBack\SYSTEM W:\Windows\System32\Config\SYSTEM
   

7. Validate that the restored hive can load:

   reg load HKLM\OfflineSystem W:\Windows\System32\Config\SYSTEM
   reg query HKLM\OfflineSystem\Select
   reg unload HKLM\OfflineSystem
   

8. If validation succeeds, restart and test.

9. If no valid RegBack hive and no restore point exists, stop manual hive repair. Preserve data and use a known system image, Reset this PC, or reinstall according to the user's data-retention requirements.

• System Restore repairs startup: Preserve the restore-point date and identify the reverted change.
• The active hive loads successfully: It may be logically incompatible rather than structurally corrupt; do not overwrite it with RegBack automatically.
• A verified RegBack hive loads and Windows starts: Expect older service, driver, and device configuration; inspect changes before normal use.
• RegBack files are zero bytes: This is expected on many Windows 10/11 systems and provides no recovery data.
• The replacement hive does not load: Restore the preserved files and stop.
• Storage errors accompany hive corruption: Treat the registry damage as a possible consequence of storage failure.

• Do not copy zero-byte RegBack files.
• Do not replace all five registry hives merely because SYSTEM is named.
• Do not download registry hives from another computer.
• Do not delete .LOG1 or .LOG2 without preserving them.
• Do not use the BCD-repair procedure for a screen that specifically names the SYSTEM hive.
• Do not continue registry writes on an unstable disk.

If a RegBack replacement makes the result worse, return to WinRE and copy SYSTEM.before-0xc000014c from W:\BootRepairBackup back to W:\Windows\System32\Config\SYSTEM. Restore the saved transaction logs only with the original hive. This rollback will also restore the original corruption if the saved hive was bad; its purpose is evidence preservation and reversal of an incorrect replacement.

• The restored SYSTEM hive passes reg load and reg unload.
• Windows completes three normal starts.
• Device Manager and Services show expected essential devices and services.
• Event Viewer contains no new registry or disk I/O failures.
• A fresh restore point or full backup is created after the system stabilizes.

Confidence is approximately 85% when System Restore reverses the hive failure. Confidence is approximately 75–80% for manual recovery from a verified RegBack hive because it can restore older driver and service state. Stop when the backup is zero length, hive validation fails, storage is unstable, or no coordinated backup exists.