Shadow Copy Failed to Create Restore Point on Windows 10/11

When This Error Hits

You're trying to create a system restore point, maybe after installing a new driver or running a disk cleanup. Windows throws error 0x8004231f: "The shadow copy provider had an error." Or it just says "Shadow Copy Failed to Create Restore Point." This usually happens on Windows 10 build 1909 or later, and Windows 11. The culprit is almost always a corrupted Volume Shadow Copy (VSS) state. I've fixed this on Dell Optiplex 7080s, HP EliteBooks, and custom builds. It's not a hardware failure — it's software rot.

Why It Happens

VSS is the service that takes snapshots of your drives for System Restore. When it fails, it's because:

• Shadow storage is full — you've hit the max allowed space.
• The VSS service is stuck — it crashed or didn't start properly.
• Corrupted VSS writers — like the SQL writer or Exchange writer if you have those installed.
• Disk cleanup deleted the shadow copies — this happens when you run Disk Cleanup and check "System Restore and Shadow Copies." That wipes everything.

Don't bother reinstalling Windows. Don't run SFC /scannow yet — it rarely fixes this directly. The real fix is resetting VSS state.

Fix 1: Restart VSS Service and Clear Storage

1. Open Command Prompt as admin. Type net stop vss and hit Enter.
2. Then net start vss to restart it.
3. Now delete all shadow copies: vssadmin delete shadows /all /quiet. This removes every restore point. You'll lose them, but you'll get the ability to create new ones.
4. Resize shadow storage: vssadmin resize shadowstorage /on=C: /for=C: /maxsize=5%. Change the drive letter if yours is different. 5% is fine for most people.
5. Try creating a restore point again. Right-click This PC > Properties > System Protection > Create.

Fix 2: Re-register VSS DLLs

If the first fix didn't work, VSS DLLs are probably messed up. Run these commands in an admin Command Prompt:

cd /d %windir%\system32\
net stop vss
net stop swprv
regsvr32 /s vss_ps.dll
regsvr32 /s vssapi.dll
regsvr32 /s vssui.dll
regsvr32 /s eventcls.dll
net start vss
net start swprv

This re-registers the core VSS components. I've seen this fix it on systems where nothing else worked.

Fix 3: Check VSS Writers

Some writers can be in a bad state. Run vssadmin list writers in an admin Command Prompt. Look for any writer with "Failed" or "Stable" status that's actually broken. If you see a writer like Microsoft Hyper-V VSS Writer or SQL Writer showing errors, you might need to disable or reinstall that application. For most home users, you can ignore non-system writers — they won't block restore points.

Fix 4: Increase Shadow Storage via PowerShell

Sometimes the GUI limits you. Use PowerShell as admin:

Set-VMHost -VirtualHardDiskPath C:\VHDs -Force  # irrelevant, ignore that
Get-WmiObject Win32_ShadowStorage | Remove-WmiObject
New-WmiObject Win32_ShadowStorage -Argument @{Volume='C:\\'; Provider='C:\\'}

Wait, that's wrong for most people. Simpler: vssadmin add shadowstorage /for=C: /on=C: /maxsize=10GB. This sets the max to 10GB explicitly. Works on Windows 10 and 11.

What If It Still Fails?

Three things to check:

• Disk space. You need at least 1% free space on the system drive. No space, no shadow copies.
• Third-party backup software. Programs like Acronis, Macrium, or Veeam can lock VSS. Disable them temporarily.
• BitLocker. If it's on, make sure it's not paused. A paused BitLocker can block VSS writes. Resume it, then try again.

If none of this works, check the System Event Log for VSS errors. Look for event ID 8229 or 12345 — those tell you exactly which writer failed. Google that specific writer ID. It's usually a broken driver or a corrupted install. You might need to uninstall the last software that touched system restore.

One last thing: skip the "System Restore Point Creator" third-party tools. They just call the same API that's broken. You need to fix VSS, not work around it.