You're staring at a blue screen or a boot error that says STATUS_REGISTRY_IO_FAILED (0xC000014D), and Windows won't start. That's frustrating, but it's fixable.
Let's get right to it. The real fix is to repair the registry hives from a recovery environment. Here's how.
Step-by-step fix
You'll need a Windows installation USB or DVD. If you don't have one, create it on another PC using the Media Creation Tool (for Windows 10) or Windows 11 Installation Assistant.
- Insert the USB or DVD and boot from it. You might need to change the boot order in your BIOS/UEFI. Look for "Boot Menu" or "Boot Order" — usually F12, F2, Del, or Esc during startup.
- When the Windows Setup screen appears, choose your language and click Next.
- Click Repair your computer in the bottom-left corner.
- Select Troubleshoot > Advanced options > Command Prompt.
You'll see a black Command Prompt window. That's normal.
Now, you need to find which drive letter your Windows installation is on. In the recovery environment, it's often not C:. Run this command:
diskpart
list volume
exit
Look for the volume with the largest size that's labeled "Windows" or has your system files. Note the drive letter — for example, it might be D: or E:. Replace C: in the commands below with that letter.
First, check the disk for errors. This can fix I/O problems that cause the registry error.
chkdsk C: /f /r
This might take a while. Let it finish. If it finds and fixes errors, great. If not, move on.
Next, repair the registry by restoring from a backup. Windows keeps a backup of the registry in C:\Windows\System32\config\RegBack. You'll copy the backup files over the current ones.
Run these commands one at a time, pressing Enter after each:
cd C:\Windows\System32\config
ren DEFAULT DEFAULT.bak
ren SAM SAM.bak
ren SECURITY SECURITY.bak
ren SOFTWARE SOFTWARE.bak
ren SYSTEM SYSTEM.bak
copy C:\Windows\System32\config\RegBack\*.* C:\Windows\System32\config
If you get an error saying "The system cannot find the file specified" for the copy command, it means the RegBack folder is empty. That's common on Windows 10 version 1803 and later. In that case, skip to the System Restore method below.
If the copy worked, close Command Prompt, and restart your PC. Windows should boot normally.
If it still fails, go back to the recovery environment and try System Restore.
- From the recovery environment, choose Troubleshoot > Advanced options > System Restore.
- Select a restore point from before the error started. If you don't see any, you can't use this method.
- Follow the prompts. The restore will take some time. Your PC will restart when it's done.
Why this works
The error 0xC000014D means the registry tried to read or write data and failed. This usually happens because the registry hive files (like SYSTEM, SOFTWARE, SAM) are corrupted, or there's a physical disk problem. By running chkdsk, you fix disk-level errors. By restoring the registry from a backup, you replace corrupted hives with healthy ones. System Restore rolls back the entire system state, including the registry, to a point where it worked.
Less common variations
Sometimes the error is caused by something else. Here are a few other things to check:
- Failing hard drive or SSD: If
chkdskfinds lots of bad sectors, your drive might be dying. Back up your data and replace the drive. - RAM issues: Faulty memory can cause registry corruption. Run Windows Memory Diagnostic (search for it in the Start menu) or MemTest86.
- Third-party drivers: A bad driver can trigger this error. Try booting into Safe Mode (from Advanced options > Startup Settings) and uninstall recent drivers.
- Windows Update gone wrong: If the error appeared after an update, uninstall the latest update from Advanced options > Uninstall Updates.
Prevention
Once you're back up, do these things to avoid a repeat:
- Keep automatic backups on. Use File History or a third-party tool.
- Don't use registry cleaners. They cause more harm than good.
- Run
chkdskoccasionally to catch disk problems early. - Make sure your PC has proper cooling and a good power supply. Sudden shutdowns can corrupt the registry.
That's it. You should be back in Windows now. If not, the disk might be too far gone, and you'll need professional data recovery.