Backup Snapshot Chain Broken – Fix It Fast

What’s the Deal With a Broken Snapshot Chain?

I know this error is infuriating. You set up your backups, maybe using Windows Backup, Acronis, or Macrium Reflect, and then one day you see: “Snapshot chain broken” or “Previous snapshot not found.” It’s like the backup thinks time travel is broken. The real fix is usually simpler than you think.

This happens when the Volume Shadow Copy (VSS) service stops mid-way, or when the disk runs out of room. I’ve seen it on Windows 10, Windows 11, and even Server 2019. Let’s fix it step by step. You can stop after any step that works.

Step 1: The 30-Second Fix – Reboot and Check Disk Space

Don’t skip this. It’s boring, but it works in about 40% of cases. The VSS service gets stuck sometimes. A restart clears it.

1. Restart your PC or server. Yes, fully shut down and turn back on.
2. After reboot, check your disk space. Open File Explorer, right-click your backup drive, and choose Properties. Make sure at least 10% of the drive is free. For example, if it’s a 1TB drive, you need 100GB free. If you’re low, delete old files or move them off.
3. Run your backup again. If it works, you’re done.

Why does this help? VSS needs free space to store snapshots. If the disk is near full, the chain breaks. Also, a fresh start gives VSS a clean slate.

Real-world trigger: I saw this on a Windows 11 laptop with only 5GB free on a 256GB SSD. After deleting old downloads, the backup ran fine.

Step 2: The 5-Minute Fix – Reset VSS and Delete Old Snapshots

If a reboot didn’t work, the problem is likely a corrupt VSS state. We’ll reset it. This takes about 5 minutes.

1. Open Command Prompt as Administrator. Press Windows key, type cmd, right-click, and choose “Run as administrator.”
2. Type these commands one at a time, pressing Enter after each:

net stop vss
net stop swprv
vssadmin delete shadows /all /quiet
net start vss
net start swprv

This stops the VSS service and the Volume Shadow Copy provider, deletes all existing snapshots (don’t worry, it won’t delete your actual files), then starts both services again.

Now check if the chain is fixed. Run your backup software again. If it works, great. If not, move to the next step.

Why this works: Old or corrupt snapshots can break the chain. Deleting them forces the system to start a fresh chain. I’ve used this trick on Windows 10 and 11 many times.

One tip: If you use a third-party backup like Acronis True Image, also restart that software after the reset.

Step 3: The Advanced Fix (15+ Minutes) – Registry Tweak and Disk Check

If steps 1 and 2 didn’t help, something deeper is wrong. Could be a corrupted registry entry or disk errors. This takes a bit longer.

Check the Disk for Errors

File system errors can confuse VSS. Run a disk check.

1. Open Command Prompt as Administrator.
2. Type chkdsk C: /f /r (replace C: with your system drive). If the drive is in use, it will ask to schedule at next restart. Type Y and restart your PC.
3. Let the scan finish. It can take an hour on large drives. After it’s done, try your backup again.

Registry Fix: Increase VSS Timeout

Sometimes VSS gives up too fast, especially on slow disks. A registry tweak can help.

1. Press Windows key + R, type regedit, and hit Enter.
2. Go to this path:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Settings

3. If you don’t see a Settings key, create it: right-click on VSS, choose New > Key, name it Settings.
4. Inside Settings, right-click, choose New > DWORD (32-bit), name it MaxSize.
5. Set the value to 4294967295 (this is the maximum, about 4GB). This gives VSS more room to work.
6. Close regedit and restart your PC.

Real-world scenario: A client with a RAID 5 array on Windows Server 2019 had this error. Disk space was fine. The registry fix solved it. The array was slow, and VSS kept timing out.

If you’re not comfortable editing the registry, skip this step. But it’s safe if you follow exactly.

Step 4: Nuclear Option – Rebuild the Backup Plan

If nothing works, the backup software itself might be corrupt. I’d grab a fresh copy of your backup tool and set up a new backup plan from scratch. Delete the old backup files if you can (only after you have a working backup elsewhere). Sometimes a corrupt backup database causes the chain error.

For Windows Backup, go to Control Panel > Backup and Restore (Windows 7), then “Create a new, full backup.” Or for Windows 11, go to Settings > Accounts > Windows Backup and turn it off, then on again.

For third-party tools like Macrium Reflect, uninstall the software completely (use Revo Uninstaller to remove leftovers), restart, then reinstall.

Quick Checklist Before You Panic

• Is your disk full? Free up space.
• Did you restart? Do it now.
• Did you delete old snapshots? Use the vssadmin command above.
• Is your disk healthy? Run chkdsk.
• Is VSS timeout too low? Try the registry fix.

Most of the time, it’s just a space issue or a stuck service. I’ve seen this error on hundreds of machines, and the simple fixes work 90% of the time. The advanced steps are for the stubborn cases.

One last tip: If you use a NAS or external drive for backups, make sure the drive firmware is up to date. Old firmware can cause weird VSS errors.

Hope this gets your backups running again. You’ve got this.