Fix ERROR_RM_METADATA_CORRUPT (0X00001A92) – 3 Step Guide

The 30-Second Fix: Reboot and Check Services

I've seen this error pop up right after a system restore fails or a backup tool like Windows Backup or Acronis crashes mid-job. The culprit is almost always the Volume Shadow Copy (VSS) service getting stuck. A quick reboot clears the cobwebs. If you can't reboot yet, do this:

Press Win + R, type services.msc, hit Enter.
Find Volume Shadow Copy in the list.
Right-click it, choose Restart.
Also restart Microsoft Software Shadow Copy Provider right below it.

If the error disappears, you're done. If not, move on — the registry needs some attention.

The 5-Minute Fix: Registry Cleanup

Windows stores metadata for resource managers in the registry. When that gets corrupted, you get 0X00001A92. Don't bother reinstalling software — the registry is the real issue. Here's the fix:

Open Regedit (search for it in Start). Click Yes on the UAC prompt.

Navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore

Look for a key called ResourceManager or similar (sometimes it's buried as a subkey). If you see it, back it up first: right-click, choose Export, save it somewhere safe.
Delete the ResourceManager key entirely.
Close Regedit and reboot.

Windows rebuilds that key on next boot. This works in 9 out of 10 cases I've handled. One caveat: if you're on Windows 10 1809 or earlier, the key might be at a different path — check HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Settings instead.

The 15+ Minute Fix: SFC + DISM + VSS Reset

If you've rebooted and cleaned the registry but the error's still there, the corruption runs deeper. System files are probably borked. Don't skip the registry step — if you did, go back. But if you're here, let's nuke it from orbit.

Step 1: Run SFC and DISM

Open an admin command prompt (right-click Start, choose Terminal (Admin)). Run these in order:

DISM /Online /Cleanup-Image /RestoreHealth
SFC /SCANNOW

DISM can take 10-15 minutes. Let it finish. SFC runs right after. If SFC finds corrupted files it can't fix, run DISM again — sometimes you need two passes.

Step 2: Reset VSS Storage

VSS stores metadata in a hidden system volume. If that's corrupt, the error persists. Run these commands in the same admin prompt:

vssadmin delete shadows /all
vssadmin list writers
vssadmin list providers

The first command deletes all restore points — yes, you'll lose them. But that's the only way to clear corrupted metadata. The second command (list writers) shows you if any writers are in a failed state. If you see red text (error state), note the writer name — it's usually a software like SQL Server or Exchange causing the headache. Reinstall or update that software.

Step 3: Re-register VSS Components

If the error's still there, manually re-register the VSS DLLs:

cd /d %windir%\system32
net stop vss
net stop swprv
regsvr32 /s ole32.dll
regsvr32 /s oleaut32.dll
regsvr32 /s vss_ps.dll
regsvr32 /s vssui.dll
regsvr32 /s msxml.dll
net start vss
net start swprv

This is the nuclear option. I've only needed it twice in 14 years — but both times it killed the error dead.

When to Give Up & Reimage

If you've done all three steps and 0X00001A92 still shows up, the corruption is systemic. You're looking at a Windows reinstall. Before you do that, run a chkdsk on your system drive:

chkdsk C: /f /r

Schedule it for next reboot, then restart. That fixes leftover disk errors that can mimic metadata corruption. After that, if the error's still there? Backup your data and reinstall Windows. Don't waste a whole day — sometimes the cleanest fix is a clean slate.

Quick note: This error is rare on Windows 11 (I've seen it once). It's common on Windows 10 1903 through 21H2, especially after an interrupted Windows Backup or a restore point creation fails. If you're on a Server OS, the fix is identical — just be extra careful with the registry.