How to fix Error 437 on Windows 11

by

Troubleshooting Guide: Error 437 – Volume Shadow Copy Snapshot Operation Terminated

Why This Error Happens

Error 437 occurs when the Volume Shadow Copy Service (VSS) attempts to create a consistent snapshot of a volume, but a file within the snapshot set is modified or locked in a way that violates the copy-on-write mechanism VSS relies on. This is typically caused by aggressive disk I/O from antivirus software, database applications, or backup agents writing to files during the snapshot window. It can also result from a corrupted VSS provider, insufficient shadow storage space, or conflicts between multiple VSS writers running simultaneously.

Step-by-Step Resolution Guide

  1. Check VSS Writer Status
    Open Command Prompt as Administrator and run:
   vssadmin list writers

Look for any writer in a “Failed” or “Retryable Error” state. Note the specific writer causing issues.

  1. Restart the Volume Shadow Copy Service and Dependencies
   net stop vss
   net stop swprv
   net start vss
   net start swprv

This clears any stuck VSS sessions that may be holding a lock on the snapshot process.

  1. Increase Shadow Storage Allocation
    Insufficient shadow storage space is a common trigger. Increase the allocation via:
   vssadmin resize shadowstorage /for=C: /on=C: /maxsize=20%

Adjust the drive letter and percentage based on your available disk space.

  1. Exclude Backup/Snapshot Target Folders from Antivirus Real-Time Scanning
    Go to Windows Security > Virus & threat protection > Manage settings > Add or remove exclusions, and add the folder(s) being backed up or snapshotted. Real-time scanning often modifies file metadata mid-snapshot, triggering Error 437.

  2. Re-register VSS DLLs
    If the writers remain unstable after a restart, re-register the core VSS components:

   cd /d %windir%\system32
   net stop vss
   regsvr32 /s ole32.dll
   regsvr32 /s vss_ps.dll
   vssvc /register
   net start vss

Alternative or Verification Steps

  • Verify the fix: Re-run vssadmin list writers and confirm all writers show a “Stable” state with “No error.” Then retry the original snapshot/backup operation.
  • Alternative: If the issue persists, temporarily pause any active file-syncing or database write operations (e.g., SQL Server, OneDrive) on the target volume during the snapshot window, then retry the backup while monitoring Event Viewer under Applications and Services Logs > Microsoft > Windows > VSS for additional diagnostic details.