How to Fix Windows Backup Error 0x80070002
Published 2026-10-16 · Marion Remote Fix
Your Windows backup is failing with error code 0x80070002. This error means The system cannot find the file specified — Windows is trying to back up a file or access a location that no longer exists or has been moved. This affects Windows Backup, File History, System Image backup, and Backup and Restore (Windows 7). The error can also appear during System Restore. Here is how to fix it depending on which backup feature you are using.
Identify which backup feature is failing
Windows has multiple backup systems and the fix depends on which one is showing the error:
- Windows Backup (Windows 11): the newer backup system that syncs folders to OneDrive and backs up settings, apps, and credentials to your Microsoft account
- File History (Windows 10/11): continuously backs up files from your libraries, desktop, contacts, and favorites to an external drive or network location
- Backup and Restore (Windows 7): the older system image and file backup tool, still available in Windows 10 and 11 through Control Panel
- System Image backup: creates a full copy of the system drive, accessible through Backup and Restore
- Check where you see the error and follow the relevant sections below
Fix File History error 0x80070002
File History shows this error when it cannot find files it previously tracked — usually because files were moved, renamed, or deleted since the last backup:
- Open File History: Settings → System → Storage → Advanced storage settings → Backup options (Windows 11) or Settings → Update and Security → Backup (Windows 10)
- Click More options → scroll down and click See advanced settings → this opens the classic File History control panel
- Click Advanced settings → Clean up versions → delete All but the latest version. Old backup entries pointing to files that no longer exist cause the error
- If that does not help, reset File History: stop File History first (turn it off in settings), then navigate to
%localappdata%\Microsoft\Windows\FileHistory\Configurationand delete all files in this folder. Turn File History back on and let it start fresh - Check that your backup drive is connected and accessible. Error 0x80070002 can appear if the backup drive was disconnected, the network share is unavailable, or the drive letter changed
Fix Backup and Restore error 0x80070002
The older Backup and Restore tool shows this error when backup sources or the backup destination have changed:
- Open Control Panel → Backup and Restore (Windows 7)
- Click Change settings and review the backup configuration. Check that all selected folders and drives still exist. If you added a folder that has since been deleted or a drive that has been removed, the backup fails when it tries to find them
- Remove any missing or invalid backup sources and re-run the backup
- If you are creating a system image, make sure the destination drive has enough space. A system image needs at least as much free space as the used space on your system drive
- Check the backup destination drive — if it is an external drive, try a different USB port. If it is a network location, verify the share is accessible: open File Explorer → type the network path (like
\\servername\sharename) and confirm you can access it
Fix the error in Windows Update backup
Error 0x80070002 frequently appears during Windows Update, which can indirectly prevent backups from completing because pending updates block the backup process:
- Open Command Prompt as administrator
- Stop update services:
net stop wuauservandnet stop bits - Rename the update cache:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old - Restart services:
net start wuauservandnet start bits - Run Windows Update again: Settings → Windows Update → Check for updates. Let all updates install and restart if needed
- After updates are current, try the backup again. Pending or failed updates often interfere with the backup process
Repair system files
Corrupted system files are a common cause of backup error 0x80070002 because the backup process tries to copy files that are damaged or partially missing:
- Open Command Prompt as administrator
- Run
DISM /Online /Cleanup-Image /RestoreHealth— this repairs the Windows component store. Takes 15-30 minutes. It requires an internet connection to download replacement files - After DISM completes, run
sfc /scannow— this checks all protected system files and replaces any corrupted ones. Takes 10-20 minutes - Restart the computer and try the backup again
- If sfc reports it found corrupted files but could not fix some of them, run DISM again and then sfc again. Sometimes it takes two passes
Check the Task Scheduler
Windows backup uses scheduled tasks to run automatically. A corrupted scheduled task can cause error 0x80070002:
- Open Task Scheduler (search for it in Start)
- Navigate to Task Scheduler Library → Microsoft → Windows → WindowsBackup
- Check the tasks listed here. Right-click each task → Properties → look at the Actions tab. If any action points to a file or program that does not exist, the task fails with 0x80070002
- If the WindowsBackup folder is missing or the tasks inside are corrupted, you can recreate the backup schedule by turning backup off and back on in Settings
- Also check Microsoft → Windows → FileHistory if you use File History — same principle applies
Fix System Restore error 0x80070002
If you see this error when trying to restore from a restore point rather than create a backup:
- The restore point may reference files from a program that has since been uninstalled. Try a different restore point — an older one may not have this conflict
- Try running System Restore from Safe Mode: restart → hold Shift → Troubleshoot → Advanced options → System Restore. Safe Mode runs fewer services and fewer files are locked, which reduces the chance of the file-not-found error
- If no restore points work, the restore point data may be corrupted. You cannot repair individual restore points, but you can delete all restore points and create a new one: System Properties → System Protection → Configure → Delete all restore points → then click Create to make a fresh one
Check OneDrive and folder redirection
If you use OneDrive to sync your Desktop, Documents, or Pictures folders, backup tools can get confused about file locations:
- OneDrive's Known Folder Move redirects these folders to
%userprofile%\OneDrive\Desktopetc. If backup was configured before the redirect, it still looks for files at the old path and gets 0x80070002 - Reconfigure the backup after enabling or disabling OneDrive folder sync to point it at the current file locations
- OneDrive files set to Online-only (cloud icon) do not exist locally as full files — backup tools that try to read them may get file-not-found errors. Change important files to Always keep on this device (right-click → Always keep on this device) before running a backup
Check disk health
A failing hard drive can cause files to become unreadable, triggering file-not-found errors during backup:
- Open Command Prompt as administrator
- Run
chkdsk C: /f /r— this checks the disk for errors and attempts to recover readable information from bad sectors. You will be asked to schedule it for the next restart since the system drive is in use - Restart the computer and let chkdsk run. This can take 30 minutes to several hours depending on drive size
- After chkdsk completes, check the results in Event Viewer: Windows Logs → Application → filter for source Wininit → look for the chkdsk summary. If it found and fixed errors, try the backup again
- If chkdsk finds bad sectors repeatedly, the drive is failing and should be replaced. Back up your data to another drive as soon as possible using a simple file copy rather than the broken backup tool
Use a different backup method
If the built-in Windows backup continues to fail with 0x80070002 and you need a working backup now:
- For file backup, manually copy important folders (Desktop, Documents, Downloads, Pictures) to an external drive. This is the simplest and most reliable method
- For a full system image, third-party tools like Macrium Reflect Free or Veeam Agent Free can create system images when the built-in tool fails. These tools handle more edge cases and provide better error messages
- For ongoing automatic backup, File History is generally more reliable than Backup and Restore for file-level backup. If one tool fails, try the other
Remote backup troubleshooting
If Windows backup keeps failing with error 0x80070002 after trying these fixes, Marion Remote Fix can diagnose the problem remotely — checking backup configuration, repairing system files, fixing scheduled tasks, and identifying the specific missing file through a secure remote session.