System Restore not working in Windows 11 — restore points missing, the restore failing mid-process, or System Restore not finding any points to restore to — is fixable in most cases, though the fixes vary significantly depending on which specific failure you’re encountering. For a broader walkthrough, our Complete Guide to Fixing Windows, Browser, and Software Errors is a good next read.
The most useful first question: is System Restore enabled at all? It’s turned off by default on many Windows 11 installations, and on machines where only the C: drive has limited space, Windows sometimes disables it automatically to free disk. Settings → System → About → scroll to “Device specifications” → “Advanced system settings” → System Protection tab. If your C: drive shows “Off” next to it: System Restore has never been creating points on this machine.
Enable System Restore and configure space
System Properties → System Protection tab → select your C: drive → Configure → “Turn on system protection” → set disk space usage to at least 5-10 GB (the slider controls how much space restore points can use) → Apply. After enabling: click “Create” to make a restore point immediately — confirm it works before relying on it.
With insufficient allocated space: Windows overwrites the oldest restore points as new ones are created, and on very small allocations, only keeps the most recent one. For meaningful protection: allocate at least 5% of the drive or 10 GB, whichever is smaller.
System Restore showing “no restore points”
If System Restore is enabled but shows no points: either none have been created yet, or they were deleted by a disk cleanup. Windows creates automatic restore points before major changes (Windows Updates, driver installs, application installs) but only if System Restore is enabled and space is available at the time of the change.
Disk Cleanup’s “System Restore and Shadow Copies” option deletes all restore points when checked. This is sometimes included in automated cleanup tools or third-party maintenance software without the user realising. After any disk cleanup session: check whether restore points still exist in System Properties.
System Restore failing mid-process
A restore that starts but fails with an error (typically error 0x80070091 or “System Restore did not complete successfully”) is caused by one of:
- Antivirus blocking file restoration: temporarily disable real-time protection before running System Restore, then re-enable after
- File system errors: run
chkdsk C: /f /rin Administrator Command Prompt (requires restart) before retrying restore - VSS (Volume Shadow Copy Service) issue: the service that manages restore points has a problem — see the VSS fix below
Restore from Safe Mode
If System Restore fails in normal Windows: running it from Safe Mode removes the interference of most third-party software and antivirus. Win+R → msconfig → Boot tab → check “Safe boot” → Minimal → Restart. In Safe Mode: open System Restore normally (search “Create a restore point” → System Restore). After restoring: msconfig → Boot → uncheck Safe boot to return to normal mode.
Volume Shadow Copy Service repair
System Restore uses VSS to create and access restore points. When VSS is broken: no restore points can be created or accessed. Administrator Command Prompt:
net stop vss
net stop swprv
cd %systemroot%system32
regsvr32 vss_ps.dll
vssvc.exe /regserver
regsvr32 /i swprv.dll
net start vss
After running: create a test restore point to confirm VSS is working. If VSS registration fails: DISM /RestoreHealth (below) is the next step.
DISM and SFC for corrupted system files
System Restore infrastructure can be corrupted by failed updates or disk errors. Run in order:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
Both in Administrator Command Prompt. Restart after both complete. Corruption in the backup/restore component files causes System Restore failures that the VSS repair above won’t address — DISM and SFC fix the underlying file system issues first.
System Restore and available disk space
If the drive has less free space than System Restore needs to complete a restore: it fails mid-process. Restore temporarily unpacks files and requires working space beyond what the final restored state uses. Ensure at least 2-5 GB free space on C: before attempting a restore to avoid mid-restore failures.
Our guide on Windows startup issues covers the Advanced Recovery Options that provide alternative system recovery when System Restore isn’t available. For disk health issues that affect System Restore’s VSS infrastructure, our disk health guide covers CHKDSK and disk space management. Microsoft’s System Restore documentation covers the full list of what System Restore does and doesn’t protect (personal files are not affected; only system files, registry, and program files are restored), which is important for setting correct expectations.
Third-party restore point deletion
Defragmentation software, cleanup utilities, and even some security products can delete restore points as part of their optimization routines. CCleaner’s “Windows” cleaning option includes VSS snapshots; defragmenters sometimes treat shadow copies as disk space to reclaim. If restore points disappear after running maintenance software: check those applications’ settings and exclude VSS/System Restore data from their cleaning scope.
Windows Update and restore points
Windows Update creates a restore point before installing major updates — but only if System Restore is enabled and there’s enough space. On machines where System Restore was disabled or space was insufficient: Windows Update doesn’t create a pre-update restore point, leaving no way to roll back a problematic update through System Restore. The Windows Update rollback feature (Settings → Windows Update → Update history → Uninstall updates) is separate from System Restore and works independently, but it’s more limited in scope.
Restoring to a specific restore point when multiple exist
System Properties → System Protection → System Restore → “Show more restore points” checkbox — this reveals all available points, not just the most recent ones. Restore points are listed by date and by the event that triggered them (Windows Update, driver install, manual). Choosing the right restore point matters: restoring to a point just before a problem started is effective; restoring to an old point loses all changes made since then, including beneficial updates and installed software.
Before restoring: click “Scan for affected programs” for any restore point — this shows which programs will be removed and which will be restored. Reviewing this prevents surprises where a restore reinstalls problematic software or removes applications installed after the restore point was created.
System Restore and encrypted drives
BitLocker-encrypted drives have a specific interaction with System Restore: restore points exist and work normally on BitLocker-encrypted drives, but the encryption state at the time of the restore point is what’s restored. If BitLocker was configured after a restore point was created: restoring to that point restores the pre-BitLocker state, requiring BitLocker to be reconfigured. This is rarely an issue but worth knowing before running a restore on an encrypted drive.
Event Viewer for System Restore failures
Event Viewer → Windows Logs → Application → filter for Source “System Restore” or “VSS.” Errors from these sources show the specific technical reason a restore failed or a restore point wasn’t created. Error messages like “System Restore failed to extract the file” point to disk errors; “The shadow copy storage area is full” indicates VSS space allocation issues; “The shadow copy provider had an unexpected error” suggests VSS component corruption.
The Event ID for System Restore failures: 8193 (VSS errors), and events from “System Restore” source show the specific restore attempt details and why it failed. This log review takes 2 minutes and often provides a specific technical error message that immediately identifies the fix needed rather than requiring trial-and-error.
System Restore points and Windows Backup
System Restore is not a backup system — it protects system configuration but doesn’t preserve personal files. A failed restore attempt that can’t be completed doesn’t harm personal files (they’re unchanged by System Restore). For actual data protection: Windows Backup (Settings → System → Backup or the legacy “Backup and Restore (Windows 7)” in Control Panel) provides file backup. For complete system image backups: “Create a system image” in the legacy backup system creates a full drive image that can restore everything including personal files.
Windows 11 reset as an alternative
When System Restore is unavailable or all restore points predate the problem: Settings → System → Recovery → Reset this PC provides two options: “Keep my files” (reinstalls Windows but preserves personal documents) or “Remove everything” (complete clean slate). “Keep my files” is effectively a more thorough alternative to System Restore when the restore infrastructure has failed.
| Problem | Cause | Fix |
| No restore points exist | System Restore disabled or space zero | Enable in System Properties; allocate space; create a point |
| Restore fails mid-process | Antivirus, disk errors, or VSS | Disable AV; run CHKDSK; repair VSS with commands above |
| Points disappear after cleanup | Maintenance software deleted them | Exclude VSS from cleanup tools; check CCleaner settings |
| “No restore points” after Windows Update | Space was insufficient at update time | Increase allocated space; update will create future points |
| VSS errors in Event Viewer | VSS component corruption | Re-register VSS DLLs; run DISM /RestoreHealth |
System Restore is most valuable when it’s been running continuously in the background before a problem occurs — the restore point created just before a driver update or Windows Update is the one you need when something goes wrong. Setting it up and forgetting about it (with adequate space allocated) is the correct approach. The troubleshooting in this guide applies when it’s failed to either create points or successfully restore from them, but the best System Restore experience comes from having it properly configured from the start.
Creating manual restore points — when and why
Automatic restore points are created before driver installs and Windows Updates. They’re not automatically created before you install third-party software, change complex registry settings, or before experimenting with system configuration changes. Creating a manual restore point before these activities is a 30-second habit: System Properties → System Protection → Create → name the point descriptively (e.g., “Before installing NVIDIA driver 550.xx”). This provides an instant rollback option when a manual change causes problems.
System Restore in WinRE (Windows Recovery Environment)
When Windows won’t boot: System Restore can be run from WinRE without needing Windows to start. When the machine fails to boot twice consecutively: WinRE opens automatically. Alternatively: hold Shift while clicking Restart → Troubleshoot → Advanced options → System Restore. Running from WinRE bypasses all third-party software, antivirus, and the Windows startup process — if System Restore fails in normal Windows but the issue is third-party interference, WinRE almost always succeeds.
WinRE System Restore also works when Windows is in a broken state that prevents the recovery options from launching normally — boot from a Windows 11 installation USB → Repair your computer → Troubleshoot → Advanced options → System Restore.
For IT administrators managing many Windows 11 machines: enabling System Restore and configuring an appropriate allocation through Group Policy ensures every managed machine has restore capability before any issues arise. Computer Configuration → Administrative Templates → System → System Restore → “Turn off System Restore” → Disabled (this enables it — the confusingly-named policy works by setting whether it’s turned off). Combined with a scheduled task that creates a restore point weekly: every managed machine maintains recent restore capability without requiring user action or IT intervention per machine.
Verifying restore points with command line
Administrator Command Prompt:
vssadmin list shadows /for=c:
This lists all Volume Shadow Copies for the C: drive, which includes System Restore points. Each entry shows the creation time and shadow copy volume. If this command returns results: restore points exist and VSS can access them. If it returns nothing despite System Restore showing it’s enabled: VSS is not creating shadows correctly — the VSS repair commands above are the next step. The vssadmin output confirms at the storage layer whether restore points actually exist, which is more reliable than the System Restore GUI which occasionally shows inaccurate point counts due to indexing delays.
A realistic note on System Restore expectations: it’s effective for undoing driver changes, rolling back Windows Updates, and reverting system configuration changes. It’s not effective for recovering deleted files, undoing ransomware encryption (modern ransomware specifically targets and deletes VSS shadow copies), or recovering from hardware failure. For these scenarios, proper backups are the only protection. System Restore is best understood as a “configuration undo” feature rather than a comprehensive disaster recovery solution — understanding this sets appropriate expectations and motivates maintaining actual backups alongside relying on restore points.
For users who want continuous protection beyond what weekly or update-triggered restore points provide: Windows File History (Settings → System → Storage → Advanced Storage settings → Backup options) creates regular backups of personal files to an external drive. Combined with System Restore for system configuration protection: this combination covers both the “I accidentally deleted a document” and the “a driver update broke my system” scenarios that System Restore alone can’t fully address. See also Windows 11 Notifications Not Working for a related case.
