Vssadmin Command: Guide to Volume Shadow Copy Service

The vssadmin command is a powerful Windows administrative tool used to manage the Volume Shadow Copy Service (VSS). It allows administrators to display current volume shadow copy backups, installed shadow copy writers, and providers. Furthermore, it provides the essential ability to resize the storage space allocated for shadow copies and manually delete them.

Whether you're troubleshooting a failed Windows Server Backup, freeing up critical disk space consumed by unseen system restore points, or verifying that database writers are in a stable state before a snapshot, mastering vssadmin gives you direct control over the Windows backup infrastructure. IT professionals and storage administrators rely on this command for maintaining a healthy and resilient disaster recovery environment.

This comprehensive guide covers vssadmin syntax, all major operations (list, resize, delete), practical examples for common scenarios, troubleshooting tips, and frequently asked questions. By the end, you'll confidently manage Volume Shadow Copies from the command line.

What Is the Vssadmin Command?

The vssadmin (Volume Shadow Copy Service administrative command-line tool) is a built-in Windows utility available in Command Prompt and PowerShell that interacts directly with the VSS infrastructure. VSS is the framework Windows uses to create consistent point-in-time snapshots (shadow copies) of data, even if files are currently in use or locked by applications (like SQL Server or Exchange).

When third-party backup software or the native Windows Server Backup runs, it invokes VSS writers to freeze I/O, creates a snapshot using a VSS provider, and uses that snapshot to back up the data securely. vssadmin allows you to inspect this entire ecosystem, ensuring that writers haven't failed and that there is sufficient storage space allocated for these hidden snapshots.

Because manipulating snapshots and storage limits affects system recoverability, vssadmin requires administrative privileges to execute.

Syntax

The basic syntax for the vssadmin command involves the main command followed by a primary action (such as list, resize, create, or delete) and specific objects like shadows, writers, or shadowstorage.

vssadmin <Command> [<Options>]

Commands Table

Command	Purpose
`list providers`	Lists registered volume shadow copy providers (usually Microsoft Software Shadow Copy provider vs Hardware providers).
`list shadows`	Lists all existing volume shadow copies and their creation times.
`list shadowstorage`	Lists the volume shadow copy storage space associations and current usage.
`list volumes`	Lists volumes that are eligible for shadow copies.
`list writers`	Lists subscribed volume shadow copy writers and their current state/errors.
`resize shadowstorage`	Resizes the maximum amount of storage space allocated for shadow copies.
`create shadow`	Creates a new volume shadow copy (Server editions only).
`delete shadows`	Deletes existing volume shadow copies to free up disk space.

Parameters and Options Explored

The list Option

The list command is an investigative tool. It is primarily used when backups fail. Knowing if a specific writer (like the WMI Writer or Registry Writer) is stuck in a "Failed" state is the first step in troubleshooting any VSS-aware backup software.

The resize shadowstorage Option

This is critical when a drive runs out of space. VSS requires adequate room to track block-level changes. If the allocated storage fills up, older shadow copies are purged. Use /For=, /On=, and /MaxSize= to define limits.

The delete shadows Option

Running out of disk space rapidly? The delete shadows command allows you to aggressively purge older snapshots. You can target specific snapshot IDs or use /all to wipe out everything on a volume. Make sure you don't need them for system restore!

The create shadow Option

On Windows Server, you can manually trigger a snapshot using /For=. This is useful for writing custom backup scripts that need a consistent point-in-time view of a volume before copying files off to a network share.

Examples

In this section, we will look at various practical, copy-pasteable examples of using the vssadmin command. Note that you must open your Command Prompt or PowerShell as Administrator to successfully run these commands.

1. View All Existing Shadow Copies

To see how many snapshots currently exist on your system and when they were taken.

vssadmin list shadows

Output:

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Contents of shadow copy set ID: {abc123de-4567-890f-g123-456789abcdef}
   Contained 1 shadow copies at creation time: 3/30/2026 10:00:00 AM
      Shadow Copy ID: {fedcba98-7654-3210-fedc-ba9876543210}
      Original Volume: (C:)\\?\Volume{12345678-1234-1234-1234-123456789012}\
      Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
      Originating Machine: SERVER01
      Service Machine: SERVER01
      Provider: 'Microsoft Software Shadow Copy provider 1.0'
      Type: ClientAccessibleWriters
      Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered

Explanation: This command pulls the current list of hidden snapshots. You can see the Volume they belong to, when they were created, and their unique IDs. These are often used by the "Previous Versions" feature in Windows Explorer.

2. Check the Status of VSS Writers

When a backup fails, checking the status of the VSS writers is always the first troubleshooting step.

vssadmin list writers

Output:

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {2b291a13-7d72-4d2d-96e0-1c4b8b6c86e0}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71cb01f99a13}
   Writer Instance Id: {47900b95-d856-42d7-b8db-dbff0dcb18c3}
   State: [1] Stable
   Last error: No error
...

Explanation: This iterates through all registered writers (like SQL, Registry, WMI, Hyper-V). You are looking for State: [1] Stable and Last error: No error. If a writer is stuck in a failed state (e.g., [8] Failed), backups interacting with those components will fail.

3. Check Shadow Storage Usage

Determine how much physical disk space is being consumed by shadow copies and what the maximum limit is.

vssadmin list shadowstorage

Output:

Shadow Copy Storage association
   For volume: (C:)\\?\Volume{12345678-abc-1234-abc-123456789012}\
   Shadow Copy Storage volume: (C:)\\?\Volume{12345678-abc-1234-abc-123456789012}\
   Used Shadow Copy Storage space: 15.5 GB (3%)
   Allocated Shadow Copy Storage space: 16.0 GB (3%)
   Maximum Shadow Copy Storage space: 47.6 GB (10%)

Explanation: This tells you the volume the snapshots are for, where they physically reside, how much space they are currently using, and the hard ceiling limit dictated by the system.

4. Resize Shadow Storage Allocated Space

If your backups are failing because older shadow copies are being aggressively purged, or if shadow copies are eating up too much of your C: drive, you must resize the storage limit.

vssadmin resize shadowstorage /for=c: /on=c: /maxsize=20GB

Output:

Successfully resized the shadow copy storage association

Explanation: This sets the absolute maximum space that VSS can use on the C: drive (to hold snapshots for the C: drive) to exactly 20 GB. You can also specify percentages, such as /maxsize=15%, or use UNBOUNDED to let it consume all available free space (not recommended).

5. Delete All Shadow Copies on a Volume

If your C: drive is completely full and you urgently need to free up 15-20 GB of space, wiping out all restore points and shadow copies is a quick fix.

vssadmin delete shadows /for=c: /all /quiet

Output:

Successfully deleted 4 shadow copies.

Explanation: The /all parameter targets every snapshot associated with the C: drive. The /quiet parameter suppresses the standard confirmation prompt, making this ideal for automated cleanup scripts. Note: This deletes your ability to use "Previous Versions" or System Restore until a new snapshot is taken.

6. Delete the Oldest Shadow Copy

If you just want to free up a little bit of space without destroying your most recent backup mechanism, purge only the oldest snapshot.

vssadmin delete shadows /for=c: /oldest

Explanation: This removes only the single oldest shadow copy on the specified volume. If you run it multiple times, it will sequentially walk forward in time deleting the oldest available.

7. View VSS Providers

Typically, Windows relies on the default Microsoft software provider, but SANs and enterprise storage arrays often inject hardware-level providers.

vssadmin list providers

Explanation: This outputs all installed providers. If you are using a SAN and the hardware provider is missing or throwing errors, offloaded hardware snapshots will silently fail and revert to slower software snapshots.

8. Create a Manual Shadow Copy (Windows Server)

If you want to quickly baseline a drive before performing a highly destructive script or major server upgrade, force a snapshot manually.

vssadmin create shadow /for=d:

Explanation: This creates a new, accessible shadow copy for the D: drive. You can then use the list shadows command to find its unique paths and mount it or script against it. (Note: The create shadow command is generally not available on client operating systems like Windows 10/11 without third-party tools).

Common Use Cases

Here are the most common scenarios where IT professionals use the vssadmin command.

Backup Troubleshooting: Executing vssadmin list writers is the undisputed first step when Veeam, Datto, Windows Server Backup, or Backup Exec starts failing with cryptic VSS errors.
Emergency Disk Cleanup: Using vssadmin delete shadows /all to instantly reclaim tens of gigabytes of space when a C: drive hits 0 bytes free, preventing a server crash.
Storage Quota Enforcement: Preventing System Restore from monopolizing a virtual machine's disk by strictly defining vssadmin resize shadowstorage /maxsize=10%.
Snapshot Verification: Using list shadows to confirm that automated backup software successfully created a snapshot during its nightly window.
Hardware Provider Checks: Ensuring that expensive SAN hardware snapshots are actually being utilized by checking list providers.
Pre-Patching Baselines: On servers, manually creating a shadow copy before installing cumulative updates to ensure a rapid rollback path exists.
Resolving VSS Writer Errors: While vssadmin doesn't purely "fix" a failed writer (that usually requires restarting specific services like the Cryptographic Service or a reboot), it definitively identifies exactly which service is causing the backup to fail.

Tips and Best Practices

To get the most out of vssadmin while maintaining a reliable backup environment, follow these proven best practices:

Never Use UNBOUNDED: When resizing shadow storage, never use /maxsize=UNBOUNDED on a production server. A runaway process writing to the disk will cause VSS to consume all free space, crashing the server. Stick to 10-20%.
Don't Forget the /On Parameter: When resizing, understand that /for=C: /on=D: means you can store the snapshot data for the C drive onto a completely different physical disk (D:). This dramatically improves performance and saves space on the primary OS drive.
Restarting Failed Writers: If vssadmin list writers shows a "[8] Failed" state, you cannot fix it through vssadmin. You must find the related Windows Service (e.g., "SQL Server VSS Writer") and restart it via services.msc, or ultimately reboot the server.
Understand the 64-Snapshot Limit: Older versions of Windows and certain VSS configurations limit you to 64 shadow copies per volume. If you schedule backups hourly, the oldest will aggressively purge after a few days.
Beware the Delete Command: Once you execute vssadmin delete shadows, there is absolutely no undelete function. Those recovery points are gone forever.
Combine with Diskshadow: On Windows Server, vssadmin is somewhat deprecated for advanced creation tasks. The diskshadow tool is the more modern, scriptable replacement for complex VSS workflows.
Run as Administrator: vssadmin commands interact directly with the kernel-level Volume Manager; they will fail immediately with an access denied error if not executed in an elevated command prompt.

Troubleshooting Common Issues

Even experienced administrators face hurdles when dealing with the intricacies of the Volume Shadow Copy Service.

"No items found that satisfy the query"

Problem: When running vssadmin list shadows, you get an empty response. Solution: This simply means there are no active snapshots on the system. If you expected your backup software to be running and holding a snapshot open, verify the software ran successfully. Prevention tip: Ensure System Protection is actually enabled for your drives via the System Properties GUI if you expect automatic daily restore points.

"Error: A Volume Shadow Copy Service component encountered an unexpected error."

Problem: Any vssadmin command throws generic COM+ or unexpected errors. Solution: The VSS service itself is likely hung or corrupted. Open services.msc and forcibly restart the "Volume Shadow Copy" service and the "Microsoft Software Shadow Copy Provider" service. Prevention tip: Ensure your servers are thoroughly patched, as VSS bugs are frequently addressed in Microsoft cumulative updates.

Writers Stuck in "Waiting for Completion" or "Failed"

Problem: Running list writers shows multiple writers not in the [1] Stable state. Solution: Often caused by a third-party backup application failing to send the "Backup Complete" signal to the VSS framework. You must restart the specific services tied to those writers or reboot the machine. Prevention tip: Ensure your backup software agents are up to date and that you do not have multiple different backup products attempting to snapshot the same server simultaneously.

"The shadow copy provider had an error."

Problem: Attempting to create or view snapshots fails citing provider errors. Solution: If using a hardware SAN provider, update the integration tools or drivers. If using the default Microsoft provider, check the Event Viewer (Application log) for VSS source errors to trace the specific fault.

Related Commands

Here are some commands closely related to vssadmin that you should also master for storage and backup administration:

diskshadow – Advanced VSS Tool

Available on Windows Server, diskshadow is an interactive scriptable command-line tool that exposes the complete functionality of VSS APIs. It provides more granular control over creating and managing complex snapshot groupings than vssadmin.

wmic shadowcopy – WMI Alternative

You can manage shadow copies via WMI objects. wmic shadowcopy delete achieves the same result as vssadmin delete shadows, often acting as a reliable workaround if the vssadmin executable throws unexpected syntax parsing errors.

diskpart – Disk Partition Tool

While vssadmin manages the hidden snapshot overlay, diskpart is the definitive tool for managing the underlying physical and logical volumes, extending partitions, and assigning drive letters.

fsutil – File System Utility

Often used in tandem with VSS troubleshooting to query free space, handle hard links, or manage USN journals before allocating massive shadow storage volumes.

Frequently Asked Questions

What does the vssadmin command do?

The vssadmin command allows administrators to view, resize, create, and delete Volume Shadow Copies, as well as interrogate the internal status of VSS Writers and Providers to ensure backups function correctly.

Is vssadmin safe to use?

Yes, but commands like delete shadows /all are highly destructive to your rollback capability. Never run deletion or resizing commands unless you specifically understand the impact on your system restore points or third-party backup chains.

Why do my shadow copies keep disappearing?

If list shadows shows your snapshots vanish unpredictably, the shadow storage limit is likely too small. Whenever the volume generates high I/O (like a large file copy), VSS exceeds its storage allocation and automatically deletes the oldest shadow copies to compensate. Use resize shadowstorage to increase the limit.

How do I fix a VSS Writer in a failed state?

The vssadmin command only shows you the failed state. To fix it, you usually need to restart the specific Windows Service associated with that writer (e.g., restart the WMI service if the WMI Writer failed), or reboot the server entirely.

What is the difference between vssadmin and diskshadow?

vssadmin is a legacy tool included in all Windows versions primarily focused on basic administration and troubleshooting. diskshadow is a more robust, scriptable framework on Server editions designed for executing complex backup methodologies and exposing hidden volumes.

Can I copy files out of a shadow copy using vssadmin?

No. vssadmin list shadows will show you the Shadow Copy Volume path (e.g., \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1), but you must use a tool like mklink to map that path to a folder on your C: drive, or use robocopy to extract the files.

Do I need to be an administrator to run vssadmin?

Yes. Modifying or viewing the deeply integrated Volume Shadow Copy infrastructure requires elevated administrative privileges. Standard users will receive access denied errors.

Should I delete shadows to free up space?

Only as a last resort. Deleting shadows removes System Restore points and the "Previous Versions" file recovery tab data. However, if a server is entirely out of disk space and crashing, deleting shadows is often the fastest, safest way to immediately recover 20-30 GB without touching user data or application binaries.

Why does "create shadow" not work on Windows 10/11?

Microsoft intentionally limited vssadmin create shadow to Windows Server operating systems. On client OS versions, shadow copies are managed strictly through the GUI "System Protection" tab or via WMI calls.

Quick Reference Card

Here is a quick reference table of vital vssadmin commands that busy administrators frequently use.

Command	Purpose	Example
`vssadmin list writers`	Check backup stability	Run when Veeam or Windows Backup fails
`vssadmin list shadows`	View all active snapshots	Find paths to extract locked files
`vssadmin list shadowstorage`	Check snapshot physical space usage	Investigate missing space on a C: drive
`vssadmin delete shadows /for=c: /all /quiet`	Instantly delete all C: drive snapshots	Emergency fix for a 100% full partition
`vssadmin resize shadowstorage /for=c: /on=c: /maxsize=20%`	Cap VSS usage at 20% of disk space	Prevent snapshots from eating up servers

Summary

The vssadmin command is a mandatory tool for any Windows administrator managing storage, disaster recovery, or server backups. It grants direct visibility into the Volume Shadow Copy Service, the fragile backbone that allows modern Windows systems to be backed up while running live.

We covered the core syntax and the essential sub-commands such as list writers for troubleshooting, list shadowstorage for capacity planning, and the emergency resize and delete options for managing critical disk space constraints. Through practical examples, we looked at how to surgically identify why an enterprise backup is failing and how to correct runaway storage allocations.

Whether you're baselining a new Exchange server, hunting down why a database replica failed last night, or simply trying to free up desperately needed gigabytes on an aging workstation without deleting user data, a strong functional knowledge of vssadmin is essential.

Ready to test your vssadmin skills? Try using the interactive simulator on our platform to build muscle memory without risking snapping volumes on a production web server. You can also explore our Commands Reference for deeper dives into related administrative utilities, or check out our guide on the diskpart command to round out your storage administration expertise.