A quick answer: If your Restore point doesn’t work in Windows 10, it’s usually because System Protection is disabled, the Volume Shadow Copy Service (VSS) or related services are broken, disk space is insufficient, or system files are corrupted. This article explains the 10 most common causes and gives clear, step‑by‑step fixes so you can get System Restore working again.
You’ll learn how to enable System Protection, fix VSS, allocate disk space, repair system files, handle antivirus or update interference, check disk health, read VSS errors, and prevent future issues.
Key Takeaway
The most effective single fix is to ensure System Protection is enabled for the system drive and that Volume Shadow Copy Service (VSS) and Microsoft Software Shadow Copy Provider are running; after that, repair system files (SFC/DISM) and check disk health to restore reliable restore-point creation and restore functionality.
Quick Fix Guide
Quick Fix Guide
| Reason for the Problem | Quick Solution |
|---|---|
| System Protection is turned off | Turn on System Protection for the system drive in Control Panel > System > System protection. |
| Not enough disk space for restore points | Increase Max Usage in System Protection > Configure or use vssadmin to resize shadow storage. |
| Volume Shadow Copy Service (VSS) stopped or failing | Start Volume Shadow Copy and Microsoft Software Shadow Copy Provider services via services.msc or net start. |
| Corrupt system files | Run SFC and DISM: sfc /scannow then DISM /Online /Cleanup-Image /RestoreHealth. |
| Disk errors or bad sectors | Run chkdsk C: /f /r and restart to scan/repair the drive. |
| Antivirus or third‑party software blocking VSS | Temporarily disable or add exclusions for your AV and retry creating a restore point. |
| Restore points were deleted by Disk Cleanup/Storage Sense | Disable automatic cleanup or change Storage Sense settings and reconfigure System Protection. |
| VSS writers have errors | Check vssadmin list writers, restart services or reboot to restore writer state. |
| Group Policy or registry disabling Restore | Check Group Policy and registry keys that may disable System Restore and re-enable them. |
| Recent Windows Update or incompatible drivers | Boot to WinRE and run System Restore from Advanced Options, uninstall problematic updates/drivers if needed. |
Detailed Fixes for “Restore point doesn’t work in Windows 10”
Below are the 10 common causes with clear explanations and step‑by‑step remediation.
1. System Protection is turned off
Why it causes the problem:
System Restore requires System Protection to be enabled on a volume (commonly C:). If it’s off, Windows will not create restore points and you cannot restore.
How to fix it:
- Open Control Panel → System and Security → System (or press Windows + Pause).
- Click System protection on the left (opens the System Properties dialog on the System Protection tab).
- Under Protection Settings, select (C:) (System) and click Configure.
- Choose Turn on system protection, set Max Usage to an appropriate percentage (5–10% recommended for most systems), then click OK.
- Back in the System Protection tab, click Create to make a manual restore point and verify it completes.
Notes: You must be an administrator for these steps. If the option is greyed out, see the Group Policy/registy steps below.
2. Not enough disk space allocated for restore points
Why it causes the problem:
If the shadow storage is too small, Windows may delete older restore points or fail to create new ones.
How to fix it:
- Open System Properties → System Protection → select C: → Configure.
- Move the Max Usage slider to allocate more space (start with 5–10%).
- Alternatively, use an elevated Command Prompt:
- View current shadow storage:
vssadmin list shadowstorage - Resize shadow storage:
vssadmin resize shadowstorage /For=C: /On=C: /MaxSize=10GB(adjust size as needed).
- View current shadow storage:
- Create a manual restore point to test.
Tip: If you have multiple partitions, ensure System Protection is enabled for the system volume (where Windows is installed).
3. Volume Shadow Copy Service (VSS) stopped or failing
Why it causes the problem:
System Restore relies on VSS and the Software Shadow Copy Provider; if these services are stopped or have errors, restore points can’t be created.
How to fix it:
- Press Windows + R, type services.msc, and press Enter.
- Find Volume Shadow Copy and Microsoft Software Shadow Copy Provider.
- Set Startup type to Manual (or Automatic (Delayed Start) for troubleshooting).
- Right‑click and choose Start.
- From an elevated Command Prompt, check status:
sc query vsssc query swprv
- To start via command line (admin):
net start vssandnet start swprv. - Try creating a restore point.
If service fails to start, check Event Viewer for VSS errors (Application/System logs) and follow the indicated error code steps.
4. Corrupt system files
Why it causes the problem:
Broken Windows system files can disable System Restore components or VSS writers.
How to fix it:
- Open Command Prompt (Admin): right-click Start → Windows PowerShell (Admin) or Command Prompt (Admin).
- Run:
sfc /scannowand allow it to complete. - If SFC reports corruption it can’t fix, run:
DISM /Online /Cleanup-Image /RestoreHealth
- After DISM completes, run
sfc /scannowagain. - Restart and test System Restore.
Notes: DISM requires internet access to retrieve repair files from Windows Update.
5. Disk errors or bad sectors
Why it causes the problem:
If the system disk has file system errors, VSS can’t create consistent snapshots and restore points fail.
How to fix it:
- Open an elevated Command Prompt.
- Schedule a disk check:
chkdsk C: /f /r - You’ll be asked to schedule on next restart—type Y and reboot.
- Allow chkdsk to complete (may take time). After Windows boots, try creating a restore point.
Tip: Backup important files before running extensive disk repairs.
6. Antivirus or third‑party software interference
Why it causes the problem:
Some security or backup tools interfere with VSS or lock files needed to build a restore point.
How to fix it:
- Temporarily disable real-time protection in your antivirus (consult vendor docs).
- Try to create a restore point. If it succeeds, add exclusions in the AV for C:\Windows\System32\vssvc.exe, the System folder, or your backup software processes.
- If unsure which program causes the issue, perform a Clean Boot:
- Press Windows + R, type msconfig → Services tab → check Hide all Microsoft services → click Disable all → Startup tab → Open Task Manager and disable startup items → Restart.
- Re-enable services one at a time to find the culprit.
Warning: Don’t leave protection off; re-enable AV after testing.
7. Restore points deleted by Disk Cleanup or Storage Sense
Why it causes the problem:
Disk Cleanup’s “Clean up system files” can remove restore points; Storage Sense may purge older points automatically.
How to fix it:
- Open Settings → System → Storage → Storage Sense → click Configure Storage Sense or run it now.
- Turn off automatic deletion of temporary files and old system restore points, or adjust timing.
- In Disk Cleanup, avoid using the More Options > System Restore and Shadow Copies > Clean up… unless you want to remove restore points.
Tip: Keep at least one manual restore point after major changes.
8. VSS writers have errors (corrupt writer state)
Why it causes the problem:
VSS writers (components that provide consistent data to VSS) can report error states and prevent snapshot creation.
How to fix it:
- Open an elevated Command Prompt and run:
vssadmin list writers - Look for any writer with an Error status (e.g., Waiting for Completion, Failed).
- Restart related services or the system:
net stop vssthennet start vss- Restart the specific service related to the writer (check writer name).
- If the writer is part of an app (SQL Server, Exchange, etc.), restart that application service or server.
- Re-run
vssadmin list writersto confirm Stable state.
If a writer remains in error after service restarts and reboot, search for the writer name + error in Microsoft documentation for targeted fixes.
9. Group Policy or registry is disabling System Restore
Why it causes the problem:
Enterprise or local policies or registry settings can disable System Restore functionality.
How to fix it:
- Open Group Policy Editor (Pro/Enterprise): gpedit.msc → Computer Configuration → Administrative Templates → System → System Restore.
- Ensure Turn off System Restore and Turn off Configuration are Not Configured or Disabled.
- Registry check (advanced; back up registry first):
- Open regedit, navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\SystemRestore
- Ensure DisableSR and DisableConfig are either absent or set to 0.
- Open regedit, navigate to:
- Reboot and enable System Protection as shown earlier.
Warning: Editing Group Policy/Registry affects system behavior—proceed carefully.
10. Recent Windows Update or incompatible drivers prevent restore
Why it causes the problem:
Sometimes updates or drivers modify system components so that a restore fails or restore points are incompatible.
How to fix it:
- Boot into Windows Recovery Environment (WinRE):
- Hold Shift while clicking Restart → Troubleshoot → Advanced options → System Restore.
- Attempt to restore from WinRE (this uses a different environment and can succeed when Windows cannot).
- If restore still fails, in WinRE use Uninstall Updates → remove the latest Quality or Feature update and reboot.
- In Windows, roll back or update drivers via Device Manager (right‑click device → Properties → Driver tab → Roll Back Driver or Update Driver).
Note: System Restore may not roll back major Windows version upgrades; use full backups if available.
Prevention and Additional Tools
Why add this section:
Fixes are good — prevention avoids headaches. These tools help diagnose or prevent future restore issues.
Best practices:
- Keep System Protection enabled and allocate adequate disk space.
- Create manual restore points before installing drivers, apps, or updates.
- Schedule periodic checks: run sfc /scannow, DISM, and chkdsk monthly.
- Use Windows Backup (File History) or a third‑party disk-imaging tool alongside System Restore for full recovery.
- Monitor VSS with
vssadminand check Event Viewer (Applications/System logs with sources VSS and SR) when problems occur.
Useful commands recap (run as admin):
vssadmin list writersvssadmin list shadowstoragesfc /scannowDISM /Online /Cleanup-Image /RestoreHealthchkdsk C: /f /r
FAQ
How can I recover deleted restore points?
If restore points were deleted by Disk Cleanup or Storage Sense, they cannot usually be recovered. Check backups or disk images; otherwise create new restore points and adjust settings to prevent future automatic deletions.
Will System Restore remove my personal files?
No — System Restore affects system files, registry, installed programs and drivers; it does not modify personal documents, pictures, or emails. Still, always backup important files before major operations.
How often does Windows create restore points?
Windows creates restore points automatically before major system events (updates, driver installs, some app installs). You can also create them manually at any time.
Can BitLocker or disk encryption block System Restore?
BitLocker should not block System Restore on the OS drive, but if the drive is in a locked or pre-boot state (e.g., trying to restore from WinRE), ensure you can unlock the drive. BitLocker does not prevent restore points on an unlocked Windows session.
What if vssadmin list writers shows a failing writer repeatedly?
Identify the writer’s associated application (e.g., SQL, Exchange, Storage). Restart its service, update the application, or consult the vendor’s support for VSS writer recovery. If the writer is a Windows component, run SFC/DISM and check Event Viewer for detailed errors.
Conclusion
System Restore problems usually come down to disabled System Protection, VSS/service issues, insufficient shadow storage, or corrupted system files — all of which can be diagnosed and fixed with the steps above. If your Restore point doesn’t work in Windows 10, start by enabling System Protection, ensuring VSS and related services are running, and running SFC/DISM and chkdsk to repair system and disk issues.
