Quick fix: Run System Restore from Safe Mode instead of normal Windows — boot to Safe Mode (Settings → Recovery → Advanced startup → Restart now → Troubleshoot → Advanced options → Startup Settings → F4), then launch rstrui. Eliminates most 0x80070003 errors caused by running services interfering with the restore.

You try to roll back via System Restore and it fails with 0x80070003: System Restore failed to extract the file from the restore point. The error code maps to ERROR_PATH_NOT_FOUND. The restore point exists, the disk has space, but System Restore can’t access something it needs — usually because Windows is holding it open or the restore point itself is partially corrupted.

Symptom: System Restore fails with error 0x80070003 (ERROR_PATH_NOT_FOUND), often midway through.
Affects: Windows 11 (and Windows 10) System Restore operations.
Fix time: ~20 minutes.

What causes this

System Restore reads files from the System Volume Information folder and writes them over the current Windows install. Three failure modes produce 0x80070003: Locked files — running services or open file handles prevent overwrite. Partial restore point — Volume Shadow Copy storage was reclaimed or truncated, making some files missing from the restore point. NTFS junctions / hard links — System Restore can’t follow certain reparse points that other apps created since the restore point was made.

Method 1: Run System Restore from Safe Mode

The single most effective fix. Safe Mode runs minimal services so fewer files are locked.

Open Settings → System → Recovery.
Click Restart now next to Advanced startup.
After reboot, choose Troubleshoot → Advanced options → Startup Settings → Restart.
On the boot menu, press 4 for Safe Mode (or 5 for Safe Mode with Networking).
Sign in. Only essential services run.
Press Win + R, type rstrui, press Enter.
Walk through the System Restore wizard. Pick the same restore point that failed before.
System Restore runs from Safe Mode. The restore typically completes successfully.
Reboot when prompted. Windows returns to normal mode.

This works because antivirus, OneDrive, search indexer, and most third-party services don’t run in Safe Mode — they were the file-lockers causing the original failure.

Method 2: Run System Restore from Recovery Environment (WinRE)

When Safe Mode also fails, or when the restore needed is too deep for Safe Mode to handle.

Boot to Recovery Environment: force-shutdown three times during boot, on the fourth Windows boots to WinRE automatically.
From the recovery menu choose Troubleshoot → Advanced options → System Restore.
Pick your account, enter password if prompted.
Pick the restore point. WinRE runs the restore offline — nothing in Windows is running, no file is locked.
Wait for completion (10-30 minutes typically).
Reboot when prompted.

WinRE is even cleaner than Safe Mode for restore operations. Use this when Safe Mode restore fails.

Method 3: Pick a different (older) restore point

Use when the current restore point itself is corrupt — Methods 1 and 2 both fail with the same point.

Open System Properties (Win + R, sysdm.cpl) → System Protection tab.
Click System Restore → Next.
Tick Show more restore points if available.
Pick an older restore point — one created before the suspected problem.
Click Scan for affected programs first to see what apps will be removed/restored.
Confirm and proceed.
If multiple restore points all fail, the entire System Restore database may be corrupted — disable System Restore, enable again, and create a new restore point as the baseline.

For ongoing System Restore reliability, ensure you have enough allocated shadow storage:
vssadmin resize shadowstorage /For=C: /On=C: /MaxSize=10GB

How to verify the fix worked

System Restore completes without error 0x80070003.
Windows boots normally after the restore.
Open Settings → System → About. The system state should reflect the restore point’s date (installed apps, updates, drivers).
Run vssadmin list shadows from elevated Terminal to confirm restore points are intact.

If none of these work

If System Restore fails from Safe Mode, WinRE, and across multiple restore points with 0x80070003, the underlying shadow storage is damaged. Reset System Restore database: from WinRE Command Prompt, run vssadmin delete shadows /for=C: /all /quiet to wipe shadow storage. After reboot, re-enable System Restore in System Protection, create a new restore point as baseline. (Note: this loses all existing restore points.) Check disk health: a failing drive can cause silent corruption in shadow storage. Run chkdsk C: /f /r from WinRE Command Prompt and let it complete on next boot. In-place upgrade instead of restore: if you need to recover Windows to a working state but System Restore won’t cooperate, an in-place upgrade install (mount Windows 11 ISO, run setup.exe, Keep personal files and apps) typically resolves issues that System Restore was trying to fix. Personal files survive; apps reinstall as needed.

Bottom line: 0x80070003 in System Restore is usually file-lock interference — run from Safe Mode or WinRE where fewer services hold files, and the restore completes.