Rocket Backups
Windows 10 & 11 Buy license · $69.95
Troubleshooting

Volume Shadow Copy Error During Backup? How to Fix VSS Problems

Fix Volume Shadow Copy errors that stop Windows backups: check the VSS service and writers, free shadow storage space and repair disk problems.

Updated 5 minute read The Rocket Backups team

A Volume Shadow Copy (VSS) error during a backup means Windows could not take the snapshot the backup program needs to copy open files. The usual fixes, in order: make sure the Volume Shadow Copy service is not disabled, check for failed VSS writers with vssadmin list writers, give shadow storage enough space, free up disk space, repair file system errors with chkdsk, and remove conflicting backup or snapshot software. Restarting the PC clears most temporary VSS failures.

Below is what VSS does, how to read the error, and each fix step by step.

What Volume Shadow Copy does during a backup

When a backup starts, the backup program asks VSS for a snapshot of the drive. VSS briefly tells running applications, through components called writers, to pause and flush their data to disk. It then freezes a point-in-time view of the volume, and the backup copies files from that frozen view while you keep working. The result is a consistent copy, even of files that are open, such as an Outlook PST, a database or the Windows registry.

System images, File History in some situations, wbadmin and most third-party backup tools rely on VSS. When it fails, you see messages such as:

  • "The backup failed. A Volume Shadow Copy Service operation failed."
  • "Volume Shadow Copy Service error: Unexpected error calling routine..."
  • "There was a failure in preparing the backup image of one of the volumes in the backup set."
  • Error codes such as 0x81000202 or 0x80042302 from Backup and Restore (Windows 7).

Find the real error in Event Viewer

  1. Press Win + X and choose Event Viewer.
  2. Go to Windows Logs → Application.
  3. Click Filter Current Log and tick the sources VSS, VolSnap (in the System log) and your backup program.
  4. Look at errors from the time of the failed backup. The description often names the writer or the volume that caused the problem.

Knowing whether the problem is a writer, a space issue or a disk error tells you which fix below to start with.

Fix 1: check the Volume Shadow Copy service

  1. Press Win + R, type services.msc and press Enter.
  2. Find Volume Shadow Copy. Its startup type should be Manual, which is the default. It starts when a backup asks for it.
  3. If it is Disabled, double-click it and set it to Manual.
  4. Check Microsoft Software Shadow Copy Provider is also set to Manual, not Disabled.

"Tweaking" guides sometimes recommend disabling VSS to save resources. If you followed one, this is likely your problem.

Fix 2: check the VSS writers

  1. Open Command Prompt as administrator.
  2. Run vssadmin list writers.
  3. Each writer should show State: [1] Stable and Last error: No error.
  4. Note any writer with a state such as Failed or an error such as Retryable error or Timed out.

Each writer belongs to a service. Restarting that service, or simply restarting the PC, resets it:

WriterRelated service
System WriterCryptographic Services
WMI WriterWindows Management Instrumentation
Registry Writer, Shadow Copy Optimization WriterVolume Shadow Copy
COM+ REGDB WriterCOM+ System Application
SqlServerWriterSQL Server VSS Writer

If a third-party application's writer keeps failing, check for an update to that application.

Fix 3: make room for shadow storage

Snapshots need working space on the drive being backed up. If the drive is nearly full, or the space set aside for shadow copies is too small, VSS fails.

  1. In an administrator Command Prompt, run vssadmin list shadowstorage to see the used, allocated and maximum shadow storage for each drive.
  2. To raise the limit for C:, run vssadmin resize shadowstorage /for=C: /on=C: /maxsize=10%.
  3. Free space on the drive. As a rule of thumb, keep at least 10 to 15 percent of a drive free; Disk Cleanup (cleanmgr) and Settings → System → Storage help.

Small hidden partitions, such as the System Reserved or recovery partition, can also run out of room for a snapshot. If the error mentions a volume without a drive letter, that is likely the cause. Fixing it usually means resizing the partition in Disk Management or with a partition tool; back up first.

Fix 4: repair disk and file system errors

File system corruption and failing sectors stop VSS from creating a clean snapshot.

  1. Run chkdsk C: /scan in an administrator Command Prompt for an online check.
  2. If it reports problems, run chkdsk C: /f and allow it to run at the next restart.
  3. Run sfc /scannow to repair damaged Windows system files, then DISM /Online /Cleanup-Image /RestoreHealth if SFC cannot fix everything.
  4. Check the drive's health with the manufacturer's tool. Repeated disk errors in the System log are a warning sign; back up what you can now.

Fix 5: remove conflicts

  • Two backup programs at once. Only one snapshot can be prepared at a time. If two jobs start together, one fails. Stagger their schedules.
  • Leftover snapshot providers. Uninstalled backup tools can leave their own VSS provider behind. Run vssadmin list providers; normally you see only the Microsoft Software Shadow Copy provider plus any from software you still use.
  • Antivirus scans. A full scan running during the backup can cause writer timeouts. Schedule them at different times.
  • Old orphaned shadow copies. vssadmin list shadows shows existing snapshots. Deleting them with vssadmin delete shadows /for=C: /oldest frees space, but it also removes restore points and Previous Versions, so only do it if you understand the trade-off.

Fix 6: drives VSS cannot snapshot

VSS works with NTFS and ReFS volumes. Drives formatted FAT32 or exFAT, such as some USB sticks and memory cards, cannot be snapshotted, so a backup that includes them as a source may fail or skip open files. Network drives cannot be snapshotted from your PC either. Back them up as plain files, or back them up on the device that owns them.

After the fix: test and keep watching

Run the backup by hand, then check the result. If it completes, run vssadmin list writers once more to confirm every writer is back to Stable. VSS problems tend to come back when a drive fills up again, so a backup tool that reports failures matters.

Rocket Backups uses snapshots to back up files that are open and in use, verifies each backup after it runs, and emails you if a job fails, so a VSS problem shows up the next morning rather than months later. Rocket Backups also shows protection status in its tray icon. For other ways a backup can silently stop, see why a scheduled backup is not running and how to verify a backup works. If the cause turns out to be a full disk, fixing a full backup drive covers the destination side too.

Frequently asked questions

What does Volume Shadow Copy do in a backup?

VSS takes a point-in-time snapshot of a drive so backup software can copy files that are open and in use, giving a consistent copy.

How do I check VSS writers?

Open Command Prompt as administrator and run vssadmin list writers. Any writer that shows a state other than Stable or an error other than No error needs attention.

Should the Volume Shadow Copy service be set to Manual?

Yes. Its default startup type is Manual, which lets it start when backup software requests a snapshot. Do not disable it.

Get three guides like this every month, plus software update notices.Subscribe →