Why Shadow Copies Vanish After You Resize the Allocation in Windows 11

Quick fix: Resizing Volume Shadow Copy allocation discards all existing snapshots if the new size is smaller than the current snapshot data. Set the new allocation higher than current usage before changing. View current size with vssadmin list shadowstorage; resize with vssadmin resize shadowstorage.

You wanted to expand Volume Shadow Copy storage so you could keep more system restore points and File History snapshots. You used Disk Management or Control Panel to increase the allocation, but all your existing shadow copies are gone. Or you shrunk the allocation to save space, and again, snapshots vanished. The resize operation deletes existing data if it crosses thresholds.

How Shadow Storage allocation works

Each volume can have shadow storage assigned to itself or to another volume. When you resize the allocation, VSS checks: if the new size is smaller than the current shadow storage usage, it can’t fit existing snapshots — it deletes them. If the new size is larger, snapshots are preserved.

Method 1: Check current usage before resizing

1. Open elevated Command Prompt.
2. Run vssadmin list shadowstorage.
3. Note the Used Shadow Copy Storage space for the volume.
4. The new allocation must be larger than that value.

Method 2: Resize via vssadmin

1. Run vssadmin resize shadowstorage /On=C: /For=C: /MaxSize=20GB (adjust 20GB to your target).
2. This sets max allocation for C: shadow storage. If 20 GB < current usage, snapshots are deleted.
3. Verify with vssadmin list shadowstorage.

Method 3: Save existing snapshots before resize

1. If you have a system restore point or file history snapshot you care about, complete the restore or backup operation first.
2. Then resize. The new snapshots can be created in the resized allocation.

How to verify the fix worked

• vssadmin list shadowstorage shows the new Maximum Shadow Copy Storage space.
• Existing snapshots remain (if you sized up).
• New restore points create within the allocated space.

If none of these work

If snapshots keep deleting unexpectedly, the volume itself may have insufficient free space — VSS needs working space beyond the allocation. Free up at least 10% of the volume. For chronic snapshot loss, check Event Viewer for VSS errors that may indicate a deeper issue with the volume.

Bottom line: Resize allocation only upward, or after backing up existing snapshots. Downsizing discards data that doesn’t fit. vssadmin lets you check sizes precisely before committing.