Volume Shadow Copy (VSS) does not support direct file or folder exclusions through its native command-line tools like
vssadmin or
wmic. To prevent specific large files or directories from being included in shadow copies, you must disable shadow copy protection for the entire volume containing those files. This approach stops all changes on that volume from being tracked by VSS, effectively excluding them from backups while requiring careful management of data integrity and recovery options for the affected drive.
Understanding VSS Limitations
It is a common misconception that administrators can fine-tune Volume Shadow Copy settings to include or exclude individual files, similar to how backup software allows exclusion lists. The Windows Volume Shadow Copy Service operates at the volume level, not the file system entry level. When you enable shadow copies on a drive, every change to every file on that volume is logged to maintain point-in-time consistency. There is no built-in switch in
vssadmin or Group Policy to ignore specific paths like
C:\Temp or
D:\Logs.
Attempting to use commands such as
vssadmin add shadowstorage /ExcludedFiles=... will fail because this syntax does not exist. The
vssadmin tool only manages shadow storage quotas, maximum sizes, and existing shadow copies. It cannot filter content. Therefore, the only native method to "exclude" data from VSS is to remove the volume from the shadow copy provider entirely.
Disabling Shadow Copies on Specific Volumes
To stop VSS from tracking a specific drive, you must delete the existing shadow copies and then disable the service for that volume. This process is straightforward but has significant implications for data recovery on that specific disk.
First, open an elevated Command Prompt or PowerShell window. Run the following command to view current shadow copy configurations:
vssadmin list shadows
This output shows which volumes have shadow copies enabled and their storage usage. If you want to exclude
D:, for example, you must first delete any existing shadows on that volume using:
vssadmin delete shadows /for=D: /quiet
Once the shadows are deleted, disable shadow copying for the volume with:
vssadmin disable shadows /for=D:
Verify the change by running
vssadmin list shadows again. The
D: drive should no longer appear in the list, confirming that VSS is no longer tracking it. This action immediately frees up the space allocated for shadow storage on that volume and stops future snapshots from being created.
Impact on Data Recovery and Backups
Disabling shadow copies on a volume means you lose the ability to restore previous versions of files via the "Previous Versions" tab in Windows Explorer. If a user accidentally deletes a file or overwrites important data on that drive, standard local recovery methods will not be available. You must rely entirely on your primary backup solution (such as Windows Server Backup or third-party tools) to recover lost data.
For many servers, this trade-off is acceptable for high-churn directories like
\Windows\Temp,
\ProgramData\Package Cache, or database transaction logs. These files change constantly, causing VSS to consume excessive disk space rapidly without providing meaningful value for most recovery scenarios. By excluding these volumes, you reduce backup times and preserve storage capacity for critical system files and user data.
However, avoid disabling shadow copies on system volumes (
C:) unless absolutely necessary. System stability and application compatibility often depend on consistent shadow copy operations. For more complex issues where VSS fails or stalls, refer to our guide on
How to unstick the Windows Volume Shadow Copy Service? to troubleshoot underlying service errors before resorting to disabling the feature.
Alternative Approaches for Large Files
If your goal is to save space rather than strictly exclude files from VSS, consider adjusting the shadow storage quota instead. While this does not exclude files, it limits how much space VSS can consume. Use the following command to set a hard limit:
vssadmin resize shadowstorage /for=D: /maxsize=5GB
This prevents VSS from growing indefinitely. Additionally, ensure that your backup software is configured to handle large files efficiently. Some backup agents allow you to exclude specific file extensions or directories during the backup phase, which is distinct from VSS behavior. This separation ensures that your long-term archives do not contain redundant temporary data, even if VSS continues to track the volume for local recovery purposes.
For environments requiring granular control over volume creation and prefixes, understanding the underlying storage architecture is crucial. Learn more about managing volume identifiers in
How to Create Windows Volumes with Prefix \\Device\\HarddiskDmVolumes*.
Frequently Asked Questions
Can I exclude a single folder from VSS on the same volume?
No, VSS operates at the volume level and cannot selectively exclude folders within an active shadow copy. All files on the volume are tracked equally. You must disable shadow copies for the entire volume to achieve exclusion.
What happens to my existing shadow copies when I disable VSS?
Existing shadow copies are immediately deleted when you run the
vssadmin disable shadows command. Any data that was previously recoverable via the Previous Versions tab will become permanently inaccessible unless restored from a separate backup.
Is it safe to disable VSS on the C: drive?
It is generally not recommended to disable VSS on the system drive (
C:). Many applications, including SQL Server and Exchange, rely on VSS for consistent backups and may fail or perform poorly if shadow copies are unavailable.
How do I check if VSS is disabled on a volume?
Run
vssadmin list shadows in an elevated command prompt. If the volume does not appear in the output, shadow copies are disabled. You can also check the volume properties in Computer Management under Storage > Shadow Copies.
Does disabling VSS affect BitLocker encryption?
No, disabling VSS does not impact BitLocker encryption status or decryption keys. However, if you need to recover data from a BitLocker encrypted volume after losing access, refer to
Recovering Data from a BitLocker Encrypted Volume with Decryption Key for guidance on using recovery keys.