Why Can't Windows Create a Volume Snapshot

Theo Lucia
Theo Lucia updated
5 min(s)
robot TL;DR:

Windows usually fails to create a volume snapshot because the Volume Shadow Copy Service (VSS) is disabled, lacks sufficient working space for shadow storage, or encounters conflicts with failed system writers and concurrent backup utilities.
    ● Fix immediate snapshot failures by changing the startup type of both the Volume Shadow Copy and Microsoft Software Shadow Copy Provider services to Manual or Automatic.
    ● Resolve snapshots that fail mid-process at a certain percentage by freeing up system drive space and expanding limits using the vssadmin list shadowstorage command.
    ● Identify blocking components by running the vssadmin list writers command with administrator rights to pinpoint and restart any specific service showing a failed, timed out, or missing status.

Ask AI for a summary

ChatGPT ChatGPT Perplexity Perplexity Gemini Gemini Claude Claude Grok Grok Free Download Free Download Free Download

Windows usually cannot create a volume snapshot because the Volume Shadow Copy Service (VSS) is blocked, disabled, misconfigured, or missing enough free space. An unable to create volume snapshot error can also appear when backup software conflicts, disk errors exist, or required system writers fail. The fix often starts with checking VSS services, storage space, and file system health.

  1. Step 1

    Check free space on the system drive and the source volume. VSS needs working space for shadow storage. Low free space can cause a backup volume snapshot failed message.

  2. Step 2

    Restart VSS-related services. Open Services and check Volume Shadow Copy and Microsoft Software Shadow Copy Provider. Set startup type to Manual or Automatic if disabled, then restart both services.

  3. Step 3

    Check VSS writers. Run vssadmin list writers in Command Prompt with administrator rights. Any writer showing failed, timed out, or missing status can block snapshot creation. Restart the related service or restart Windows.

  4. Step 4

    Check shadow storage allocation. Run vssadmin list shadowstorage. If allocated space is too small or unavailable, increase the limit on the affected volume.

  5. Step 5

    Scan the file system and system files. Run chkdsk on the affected drive, then run sfc /scannow. File system corruption or damaged Windows components can prevent VSS from working.

  6. Step 6

    Retry the backup after disabling conflicting backup tools, antivirus scan tasks, or disk utilities temporarily. Multiple tools requesting snapshots at the same time can trigger a VSS snapshot error.

Common Issues and Fixes
  • Snapshot fails immediately: likely cause is disabled VSS services; fix is enabling and restarting VSS and the Microsoft provider service.
  • Snapshot reaches a certain percentage then fails: likely cause is low free space or limited shadow storage; fix is freeing space and expanding shadow storage.
  • Specific writer shows failed: likely cause is a problem in the related application or service; fix is restarting the related service or rebooting Windows.
  • Snapshot fails on one drive only: likely cause is file system errors or bad sectors; fix is running CHKDSK and checking drive health.
  • Snapshot fails after system changes: likely cause is broken system files or update issues; fix is running SFC and DISM, then retrying.
Option Best For Limitation
Restart VSS services Service-related errors May not fix writer failures
Increase shadow storage Low-space snapshot failures Requires free disk space
Run CHKDSK and SFC Corruption-related failures Can take time
Disable conflicting tools Backup software conflicts Not useful if VSS is already broken
Reboot Windows Temporary writer or lock issues May not fix persistent damage
Quick Tips
  • External drives and network locations may have different snapshot limits than local system volumes.
  • Encrypted volumes usually need proper unlock status and valid credentials before snapshot creation can work.
  • On SSDs, repeated repair attempts after severe corruption can increase risk if important data is still unreadable.
  • If a drive clicks, disconnects repeatedly, or is not detected, stop repeated DIY repair attempts and consider professional diagnosis.

If snapshot errors happen after accidental deletion, formatting, or partition problems, avoid saving new data to the affected drive.

Protip:

Resolve VSS errors before relying on a backup, and copy critical files separately if disk health warnings appear.

Recommend

If a VSS failure leaves Windows files unprotected or missing, Recoverit Windows System Recovery can scan the readable system drive after backup activity stops.

Free DownloadFree DownloadFree Download