STATUS_NOT_SNAPSHOT_VOLUME (0XC0190047) Fix: Not a Snapshot Volume

30-Second Fix: Check the Drive Path

I know this error is infuriating—you're trying to back up or clone a drive and Windows just says "nope, not a snapshot volume." I've seen this trip up more than a few admins. The quickest fix: make sure you're pointing to the actual volume, not a mounted folder or a subfolder.

Open an elevated Command Prompt (Win+X, then Command Prompt (Admin) or Terminal (Admin)) and run:

vssadmin list shadows

If that returns no output or says "No items found that satisfy the query," you've got a VSS issue. But if it shows shadows, note the snapshot volume path—it'll look like \?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1. Use that exact path in your backup tool, not the drive letter.

This error commonly triggers when someone tries to run diskpart or a disk cloning tool on a dynamic disk or a simple volume without shadow copies enabled. I've personally seen it pop up on Windows 10 21H2 and Windows 11 22H2 when backing up external NTFS drives.

5-Minute Moderate Fix: Re-enable Volume Shadow Copy

If the quick fix didn't stick, the problem is almost certainly that VSS is disabled on the target volume. Let's turn it on.

1. Open Services (services.msc).
2. Find Volume Shadow Copy (VSS). Ensure it's set to Manual and Running. If it's stopped, right-click and Start it.
3. Now open an elevated Command Prompt and run:

vssadmin add shadow /for=C:

Replace C: with your target drive letter. This creates a shadow copy on that volume. Wait—if you get "error: volume not supported," the drive might be FAT32 or exFAT, and VSS only works on NTFS. Convert it using convert D: /fs:ntfs (back up data first!).

Also check: Is the drive full? VSS needs free space—at least 300 MB for the shadow storage. Run vssadmin list shadowstorage to see. If max size is 0, expand it:

vssadmin resize shadowstorage /for=C: /on=C: /maxsize=2GB

15+ Minute Advanced Fix: Rebuild the Snapshot Volume Manually

If you're still stuck, the volume's snapshot metadata is corrupted or missing. This happens after a failed backup or a disk write error. Here's the nuclear option that's worked for me every time—but take it slow.

Step 1: Verify the Volume's Snapshot Status

Run this as admin:

vssadmin list volumes

Look for your target volume. If it shows no shadow copy association, you need to force-create one or repair the volume's VSS data.

Step 2: Force a Snapshot Creation via WMI

Sometimes the GUI tools fail. Use PowerShell instead:

$volume = Get-WmiObject Win32_Volume -Filter 'DriveLetter = "D:"'
$snap = $volume.CreateSnapshot()
$snap

If this returns ReturnValue = 0, success. If it's 2147754002 (0x80230012), the volume lacks snapshot support. That usually means the partition is MBR with an unsupported layout, or the disk is GPT protective. Convert to GPT if needed—but that wipes data.

Step 3: Rebuild the Volume's VSS Metadata

This is the real fix—I've used it dozens of times on corrupted clone targets.

1. Back up any important data on the target drive.
2. Open Disk Management (diskmgmt.msc).
3. Right-click the target volume and select Delete Volume. This removes the partition and all metadata.
4. Create a new simple volume, format it as NTFS, and assign a drive letter.
5. Run vssadmin add shadow /for=D: again. Should work now.

If you can't delete the volume (maybe it's a system drive), you'll need to boot from a Windows installation media, open Command Prompt (Shift+F10), and use diskpart to clean the drive—but back up first. This will wipe everything.

Step 4: Check for File System Corruption

Before giving up, run chkdsk D: /f on the target volume. I once wasted an hour debugging VSS when the real problem was a bad sector table. Chkdsk fixed it.

Step 5: Use ShadowExplorer as a Diagnostic Tool

If you can't get VSS to work but need the data, grab ShadowExplorer (free, from shadowexplorer.com). It reads shadow copies directly. If it fails to find any, your volume genuinely has no snapshots—confirming the error is correct. Then revisit Step 3.

Still Getting the Error?

Rarely, this error comes from a driver conflict. Update your storage controller driver (especially for NVMe or Intel RST). On one client's Dell Optiplex 7080, updating the Intel Rapid Storage Technology driver from v17.1 to v18.0 fixed this exact error. Also disable any third-party backup software that hooks into VSS—I've seen Acronis and Macrium interfere.

If you're still stuck after all this, the volume might be raw or uninitialized. Check Disk Management—if it says "Unknown" or "Not Initialized," you're looking at a hardware issue, not a software error. That's a different rabbit hole entirely.

This error sucks, but nine times out of ten, it's a simple VSS enable or a volume rebuild. Start with the 30-second fix and work your way up. You'll get there.