Fix ERROR_BADDB (0X000003F1) Registry Corrupt

What’s ERROR_BADDB (0X000003F1)?

You’ll see this when Windows boots but can’t load the registry. The exact text: “The configuration registry database is corrupt.” Happens after a bad shutdown, failing hard drive, or a failed Windows update. The culprit here is almost always a corrupted registry hive — usually SYSTEM, SOFTWARE, SAM, or DEFAULT under C:\Windows\System32\config. Don’t bother with registry cleaners — they won’t fix a corrupt hive file.

Below is a three-stage fix. Start with the first, stop when it’s fixed.

Quick Fix (30 seconds) — Last Known Good Configuration

Windows keeps a backup of the last registry state that booted successfully. Try this before anything else.

1. Restart the PC.
2. Press F8 repeatedly during boot (before the Windows logo). On Windows 10/11, you might need to interrupt boot 3 times to trigger automatic repair — then go to Troubleshoot > Advanced Options > Startup Settings > Restart.
3. Select Last Known Good Configuration (advanced). It’s usually option 5.

If it boots, great — you’re done. If not, move to the moderate fix.

Moderate Fix (5 minutes) — System Restore or Registry Backup

Windows automatically saves registry backups to C:\Windows\System32\config\RegBack. Let’s use them.

Step 1: Boot into Recovery Environment

You need command prompt access. Boot from a Windows installation USB or recovery drive. If you don’t have one, use the automatic repair loop trick above.

1. At the recovery screen, choose Troubleshoot > Advanced Options > Command Prompt.
2. A black command window opens.

Step 2: Copy Backup Hives

Run these commands. They overwrite the corrupt hives with the backup copies.

cd /d C:\Windows\System32\config
ren SYSTEM SYSTEM.old
ren SOFTWARE SOFTWARE.old
ren SAM SAM.old
ren DEFAULT DEFAULT.old
ren SECURITY SECURITY.old
copy RegBack\SYSTEM SYSTEM
copy RegBack\SOFTWARE SOFTWARE
copy RegBack\SAM SAM
copy RegBack\DEFAULT DEFAULT
copy RegBack\SECURITY SECURITY

If RegBack is empty (happens on some Windows 10/11 versions), skip to the advanced fix.

Reboot and test. If it works, you’re good. If not, move on.

Advanced Fix (15+ minutes) — Manual Registry Hive Repair

This is the nuclear option. You’ll manually rebuild the SYSTEM hive from the C:\Windows\System32\config\RegBack or use a working copy from another PC. Only do this if you’re comfortable with the command line.

Option A: Use the Emergency Repair Disk (ERD) Registry Tool

If you have a Windows Server or Windows 10/11 with the Windows Recovery Environment, you can use reg.exe to load and fix hives. But honestly, the fastest approach is:

Option B: Replace Hives from a Working Installation

You need a second Windows PC (same version and build). On the working PC:

1. Copy the entire C:\Windows\System32\config folder to a USB drive.
2. Boot the broken PC into recovery mode.
3. Open Command Prompt.
4. Copy the files over:

   copy D:\config\* C:\Windows\System32\config /y

   (adjust drive letters — the USB might be D:).

Reboot. If it asks for product key or activation, that’s fine — Windows will re-activate.

Option C: Hive Recovery with chkdsk

Sometimes the registry files aren’t corrupt — the disk has bad sectors. Run:

chkdsk C: /f /r

This can take an hour. If it finds and fixes bad sectors, reboot. The registry might work again.

What If Nothing Works?

You’re looking at a reinstall. But before you do, try one last thing: boot from a Linux live USB, mount the Windows partition, and copy C:\Windows\System32\config\RegBack\* to C:\Windows\System32\config\. Linux doesn’t care about Windows file locks.

If all else fails, backup your data using that Linux USB, then do a clean install. The registry is the heart of Windows — when it’s gone, it’s gone.

Pro tip: Prevent this by enabling System Protection and creating restore points before updates. Also, avoid force-powering off during updates.