VM Checkpoint Restore Fails: The Quick Fix That Works
VM restore fails with error 0x80042302. Fix it by clearing the VSS writer snapshot cache. This usually happens after a backup software update.
Yeah, that error is annoying. You try to restore a VM checkpoint and it just sits there or throws a generic error. I've seen it a bunch, especially on Hyper-V 2016 and 2019 servers. Had a client last month whose entire backup chain broke because of this. Let's fix it.
The Fix: Clear the VSS Writer Snapshot Cache
Open an elevated PowerShell session and run this:
vssadmin delete shadows /all /quiet
Then run:
vssadmin list writers
Check that all writers show "Stable" state and no errors. If you see any with "Failed" or "Retryable error", reboot. But 80% of the time, just clearing the shadows fixes it.
After that, try the restore again. Should work.
If it doesn't, you might need to restart the Volume Shadow Copy service:
Restart-Service VSS
Then retry.
Why This Works
VM checkpoints rely on VSS (Volume Shadow Copy) to snapshot the VM state. When VSS writers get confused because the snapshot cache has old entries from previous backups or failed checkpoints, restore fails. The error 0x80042302 basically means "VSS can't create a new snapshot because the cache is stale." Clearing it gives VSS a clean slate. No fancy tricks, just cleaning up its mess.
Also, if you use backup software like Veeam or Altaro, they sometimes leave orphaned snapshots. The vssadmin delete shadows command wipes all of them. That's why it works so well.
Less Common Variations
Sometimes the issue isn't the cache itself but a specific VSS writer that's stuck. Here's how to check that:
vssadmin list writers
Look for a writer with state "Retryable error" or "Failed". If you see one, note its name. Then run:
vssadmin list providers
If you see a provider called "FileShareShadowCopyProvider", that can cause issues on Hyper-V 2016. Uninstall it:
dism /online /remove-package /packagename:FileShareShadowCopyProvider...
But that's rare. More common: a third-party antivirus scanning the VSS folder. Check your antivirus logs. Exclude the VSS folder: C:\Windows\System32\vss.
Another variation: the VM itself has a corrupted shadow copy inside its own OS. If the fix above doesn't work, log into the guest VM and run from inside the guest:
vssadmin delete shadows /all /quiet
Then try the checkpoint restore from the host again.
Prevention
Don't let VSS snapshots pile up. Set your backup software to keep max 10 snapshots or limit them by retention days. I prefer 7 days max for daily backups. Also, after any backup software update, schedule a quick check: run vssadmin list writers before a restore is needed.
On Hyper-V hosts, enable the cluster validation check for VSS. If you use failover clustering, one reboot after maintenance can prevent this.
And here's a stupid simple thing: don't store VM files on an SMB share that's not running on a supported version. Windows Server 2012 R2 as file server with Hyper-V 2016? That's a known headache. Upgrade the file server or move VMs to local storage.
That's it. Real fix, no fluff.
Was this solution helpful?