0X000002AD

0x000002AD Registry Hive Recovered: What It Means & Fixes

EP
Erropedia Team
📅 May 26, 2026 📅 Updated Aug 2, 2026 👁 10 views Windows Errors Intermediate
Windows says a registry hive was corrupted but recovered. This usually means disk or power issues. Here's how to stop it from happening again.

The 30-Second Fix: Run SFC and DISM

Windows already recovered the hive — that's what the error 0x000002AD tells you. The registry file was damaged, Windows swapped in a backup copy, and now you're up and running. But the underlying cause (bad disk sectors, abrupt shutdown, or driver bug) might still be there. Start with the built-in system file checker.

  1. Open Command Prompt as Administrator. Hit Win+X, choose Terminal (Admin).
  2. Run: sfc /scannow. Wait for it to finish. It'll replace any corrupted system files from the local cache.
  3. If SFC reports errors it couldn't fix, run: DISM /Online /Cleanup-Image /RestoreHealth. DISM pulls fresh files from Windows Update servers.
  4. Reboot. If the error doesn't come back, you're likely done. The corruption was a one-time glitch from a power failure or a flaky driver update.

Why this works first: SFC catches registry file corruption that's still in memory or in the backup copies. If the hive was already recovered, SFC can seal the deal by fixing any lingering inconsistencies.

The 5-Minute Fix: Check Your Disk for Bad Sectors

Registry corruption often traces back to physical disk errors. A failing SSD or a drive with pending reallocated sectors can corrupt any file it touches, including hive files. The registry is read/written constantly, so it's a prime target.

  1. Open Command Prompt as Admin.
  2. Run: chkdsk c: /f /r. The /f flag fixes file system errors, /r locates bad sectors and recovers readable data.
  3. It'll ask to schedule a check on next reboot. Type Y and press Enter.
  4. Restart your PC. Let the disk check run fully — it might take 30-60 minutes on a larger drive.

A real-world scenario: I saw this error on a Dell OptiPlex 7080 after a Windows 11 update that triggered a forced reboot. chkdsk found 4 bad sectors in the pagefile area. The sectors were remapped, and the error never returned. If chkdsk reports a lot of bad sectors, back up your data and replace the drive. The registry hive is just the canary in the coal mine.

The Advanced Fix (15+ Minutes): Restore a Specific Registry Hive from Backup

If the error keeps returning — say, you see it every boot or after a specific program runs — you need to identify which hive is corrupted and restore it manually. Windows keeps automatic registry backups in the System32\config\RegBack folder (or System32\config\regback on older builds). The exact hive name appears in the error message where %hs is. For example, SOFTWARE or SYSTEM or SECURITY.

  1. Boot into Windows Recovery Environment (WinRE). Hold Shift while clicking Restart, or interrupt boot three times to trigger automatic repair.
  2. Go to Troubleshoot > Advanced Options > Command Prompt.
  3. Run diskpart and list volume to find your Windows drive letter (often D: in WinRE). Exit diskpart with exit.
  4. Back up the current (possibly corrupt) hive: ren D:\Windows\System32\config\SOFTWARE SOFTWARE.bad (replace SOFTWARE with your hive name).
  5. Copy the backup: copy D:\Windows\System32\config\RegBack\SOFTWARE D:\Windows\System32\config\SOFTWARE. If the RegBack folder is empty (common on Windows 10/11 with Compact OS), you'll need to use a restore point or reinstall.
  6. Exit and reboot normally.

Why this gets complicated: Since Windows 10 version 1809, Microsoft stopped making automatic registry backups. The RegBack folder is often empty or contains 0-byte files. If that's your case, the last resort is a System Restore point that includes the registry, or an in-place upgrade using Windows Media Creation Tool. Both preserve your apps and settings but replace the hive files.

When to Just Reinstall

If you've run SFC, DISM, chkdsk, checked RegBack, and you're still seeing 0x000002AD, the hive files themselves are persistently damaged. Windows might keep recovering them, but the errors will pile up. The cleanest fix: back up your data, create a bootable USB with Microsoft's Media Creation Tool, choose "Keep personal files and apps" during reinstall. It replaces all registry hives fresh. Takes about an hour, but it's bulletproof.

One more thing: never ignore this error. A recovered hive is a warning. If you see it more than once in a month, investigate your disk health with CrystalDiskInfo or your SSD vendor's tool. The registry doesn't corrupt itself.

Related Errors in Windows Errors
0X00002075 Fix ERROR_DS_USER_BUFFER_TO_SMALL (0X00002075) Fast 0x80070490 Windows Update Agent Corrupted – Fix It Without Reinstalling 0X80004001 E_NOTIMPL (0X80004001) – Not Implemented Fix 0X00000932 Fix 0X00000932: NERR_MaxLenExceeded String Too Long
0x000002AD registry hive recovered event ID 0x000002AD fix Windows registry corruption corrupted registry hive registry recovery error Windows 10/11 registry error 0x000002AD how to fix registry hive corrupted registry hive recovered Windows 11 EVENT_RegistryHiveRecovered check disk registry corruption chkdsk registry repair

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.