Fix Windows Backup Error 0x80070002 in 3 Steps

What's Actually Happening Here

Error 0x80070002 is a 'file not found' error. When Windows Backup runs, it checks for a list of files it backed up before. If one of those files got deleted — by disk cleanup, a failed update, or someone messing with the backup folder — Backup can't continue. It stops and throws this error.

I've seen this most often after Windows Update fails midway, or after running Disk Cleanup with 'Delivery Optimization Files' checked. The system tries to do a differential backup (saving only changes), but can't find the original backup catalog file.

Here's the fix path. Start with the simplest, takes 30 seconds. If it doesn't work, move to the next. You can stop when backup runs clean.

The 30-Second Fix: Delete the Backup Catalog

This is the reason step 1 works: Windows Backup stores a catalog of what it backed up. If that catalog references a file that's no longer there, the backup fails. Deleting the catalog forces Backup to rebuild it from scratch during the next run.

1. Open File Explorer.
2. Go to your backup drive (where you store backups, not C:).
3. Look for a folder named WindowsImageBackup. If you don't see it, enable hidden items: View > Show > Hidden items.
4. Open that folder, then open the folder with your computer's name (like DESKTOP-ABC123).
5. Delete the Backup folder inside. Don't delete the whole computer-name folder — just the Backup subfolder.

Now run Windows Backup again. It'll re-create the catalog and do a full backup (first time will be full, not incremental). That's fine.

If backup succeeds now, you're done. If error persists, move to step 2.

The 5-Minute Fix: Turn Off Shadow Copies, Retry

What's actually happening here is that the backup process uses Volume Shadow Copy Service (VSS) to snapshot files. If a shadow copy is corrupt or the disk is tight on space, VSS fails, and Backup errors out with 0x80070002.

1. Open Command Prompt as admin. Hit Start, type cmd, right-click Command Prompt, choose 'Run as administrator'.
2. Type this and hit Enter:
   

   vssadmin delete shadows /all

   
   This deletes all shadow copies on the system. Yes, you lose restore points. But you can re-create them after fixing backup.
3. Now run Windows Backup again.

If backup succeeds, the problem was a corrupt shadow copy. After backup completes, re-enable system protection if you want restore points: go to System Properties > System Protection > Configure > Turn on system protection.

If the error still shows up, move to step 3.

The 15+ Minute Fix: Reset Windows Backup Completely

This is the nuclear option. It deletes all existing backups and starts fresh. Do this only if steps 1 and 2 failed. The reason step 3 works is that sometimes the backup metadata itself is broken beyond repair — not just the catalog or shadow copies.

1. Open Control Panel > System and Security > Backup and Restore (Windows 7) — yes, that's the same tool in Windows 10 and 11.
2. Click 'Manage space' on the right side.
3. Click 'View backups' — you'll see a list of all backup folders.
4. Click 'Delete' for each backup listed. Confirm deletion.
5. Close the window.
6. Now click 'Set up backup' and configure a fresh backup to a different drive if possible. If you must use the same drive, that's fine — the old data is gone.

After this, run a manual backup. It'll do a full backup, which can take hours depending on your data. But it should complete without error 0x80070002.

If it still fails, you likely have deeper issues: bad drive, failing RAM, or a corrupt system file. Run sfc /scannow from admin Command Prompt, then DISM /Online /Cleanup-Image /RestoreHealth. If those find and fix errors, try backup again.

Why Not to Use the 'Backup and Restore' Wizard's Repair Option

You might see a 'Repair' button in the Backup and Restore tool. Skip it. In my experience it tries to fix metadata but rarely works for this specific error. It's a waste of time. Just delete the catalog or start fresh.

One Last Thing: Check Disk Space

Error 0x80070002 can also mean the backup drive is almost full. Windows needs room to write temporary files. Try to keep at least 10% of the backup drive free. If you're under that, delete old backups or use a bigger drive.

That's it. Start with step 1, most people stop there. If not, work through the rest. This error is annoying but fixable.