System Restore Points Not Creating? Here's What's Actually Wrong

1. Disk Space: The #1 Reason Restore Points Go Missing

I had a client last month—small dental office, five machines, all with the same problem. Restore points would show up for a week, then vanish. They'd been running Windows Updates like crazy, and each update triggers a restore point. But here's the kicker: Windows only keeps restore points until the disk space allocated hits its limit. Once that limit is reached, the oldest points get deleted silently.

Go check if you're running into this right now. Open System Protection settings by pressing Win + R, typing sysdm.cpl, and hitting Enter. Click the System Protection tab. Select your system drive (usually C:) and click Configure.

Look at the Disk Space Usage slider. The default max usage is 3-5% of your drive. On a 250GB SSD, that's about 7.5-12GB—enough for maybe 3-4 restore points. Every time the system tries to create a new point, it finds zero room and deletes the old one instead. You're not missing restore points; they're being rotated out before you ever see them.

Bump that slider to 10% of your drive. For a 500GB drive, that's 50GB—plenty of room for a couple weeks worth of restore points. Click OK. Then manually create a restore point by clicking Create in the same window, naming it something like "Manual test". If it succeeds, you're good. If it fails, read on.

One thing: if your drive is nearly full (less than 1GB free), Windows flat-out refuses to create any restore points. Might be time to clean up with Disk Cleanup or move some files. I tell clients to keep at least 5% free.

2. The Scheduled Task That Decides to Nap

Windows doesn't create restore points on a timer. It does it through a scheduled task called SR (System Restore). That task lives in Task Scheduler, and it's supposed to run daily. But Microsoft, in their infinite wisdom, made the task trigger dependent on user logon. If nobody logs in? No restore points. Also, the task can get disabled after a Windows update or a third-party cleaner runs amok.

Open Task Scheduler by hitting Win + R, typing taskschd.msc, and pressing Enter. Navigate to this path in the left pane:

Task Scheduler Library > Microsoft > Windows > SystemRestore

You should see a task named SR. Double-click it. On the General tab, make sure it's Enabled and set to Run whether user is logged on or not.

Now go to the Triggers tab. If there's no trigger, click New and set it to Daily, start time of your choice (I use 3 AM), and check Enabled. If there's already a trigger, check if it's enabled and set to repeat every 1 day.

Click OK and close Task Scheduler. Restart the machine, then wait a few minutes. Check System Protection to see if a restore point appeared. If it did, you're done. If not, the task might be stuck—try running it manually: right-click the task and select Run. If it errors out, note the error code and check the event log (Win + X > Event Viewer > Windows Logs > System) for anything with source VolSnap or VSS.

3. Volume Shadow Copy Service: The Hidden Gatekeeper

The actual engine behind restore points is the Volume Shadow Copy Service (VSS). If VSS is broken, nothing works. I've seen this happen after a bad Windows patch (KB5003537, I'm looking at you) or if some backup software (looking at you, old Norton Ghost) mucks with the VSS writers.

Open an elevated Command Prompt (right-click Start > Windows Terminal (Admin)). Run this command to check VSS writers:

vssadmin list writers

You should see a list of writers, each with a state of [1] Stable. If you see [5] Failed or [2] Waiting for completion, you've got a problem. Note the writer name.

Now check the VSS volume status:

vssadmin list shadows

If this returns "No items found that satisfy the query", VSS isn't creating any shadow copies—meaning no restore points at all. Next, check if the service is running:

sc query vss

Look for STATE—it should be 4 RUNNING. If it's stopped, start it:

net start vss

If VSS fails to start, check the Event Viewer under Applications and Services Logs > Microsoft > Windows > VolumeShadowCopy. Common errors include corrupt VSS writers (fix: uninstall recent updates or use vssadmin delete shadows /all then reboot) or missing system files (fix: run sfc /scannow and dism /online /cleanup-image /restorehealth).

One last thing: third-party antivirus tools like McAfee or Malwarebytes sometimes block VSS from creating snapshots. Temporarily disable the AV for a few minutes, create a manual restore point, and see if it works. If it does, add an exception for VSS in your AV settings.

Quick-Reference Summary Table