Fix ERROR_CANT_CREATE_MORE_STREAM_MINIVERSIONS (0X00001A9C)

Cause 1: Too Many Shadow Copies on the Volume

This is the one I see most often. The error ERROR_CANT_CREATE_MORE_STREAM_MINIVERSIONS pops up when Windows Volume Shadow Copy Service (VSS) has created too many miniversions of a file. Miniversions are tiny snapshots of file changes, used by System Restore and backup tools. Each NTFS volume has a hard limit — 64,000 miniversions per file. Yeah, sounds like a lot, but when you've got aggressive backup software or frequent restore points, you'll hit it fast.

I had a client last month whose accounting software kept throwing this error during nightly backups. Turned out their server had over 400 shadow copies stacked up from two years of daily snapshots. Deleted the old ones and the error vanished.

Fix: Delete Old Shadow Copies with vssadmin

Open Command Prompt as Administrator. Then run:

vssadmin list shadows /for=C:

Replace C: with your affected drive. You'll see a list of shadow copies. To delete the oldest ones:

vssadmin delete shadows /for=C: /oldest

Repeat until you've got less than 100 shadow copies. If you want to nuke them all (risky — you lose all restore points):

vssadmin delete shadows /for=C: /all

Then re-enable System Restore normally. After cleanup, the error should stop. If it doesn't, move to cause 2.

Cause 2: VSS Snapshot Limit Set Too High

Even after deleting old snapshots, VSS might recreate them too aggressively. The default max shadow copies per volume on desktop Windows is 64. On Server, it's 512. If you (or some backup software) cranked this higher, you're asking for trouble.

Check the current limit with:

vssadmin list shadowstorage /for=C:

Look at the "Used Shadow Copy Storage Space" and "Maximum Shadow Copy Storage Space". If the max is huge, you'll keep hitting the miniversion ceiling.

Fix: Lower the Max Shadow Copy Space

Use vssadmin to resize the storage. Set a reasonable maximum — for most systems, 10% of the volume size or 10 GB, whichever is smaller:

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

Change the path and size to fit your drive. After this, the system won't create new snapshots once it hits that cap. This prevents the miniversion limit from being reached again.

Warning: If you're using third-party backup software that relies on VSS, check its settings too. Some tools override the system limit.

Cause 3: File-Level Miniversion Limit from Frequent Saves

This one's less common but real. If you have a single file that gets saved hundreds of times per hour (think database files, log files, or a busy Excel workbook shared over a network), each save creates a miniversion. After 64,000 saves, the error kicks in.

I helped a manufacturing company whose inventory database file (.mdb) hit this exact limit. Their barcode scanner updated the file every 3 seconds during shifts. That's 1,200 saves per hour. After 53 hours, boom — error.

Fix: Exclude the File or Folder from VSS

You can't directly exclude a single file from VSS in Windows GUI, but you can use registry or script. The cleanest way: move the file to a volume with VSS disabled, or disable VSS on the entire volume if it's not critical.

To disable VSS on a drive temporarily:

Disable-MMAgent -MemoryCompression   # this doesn't do it — wrong command
vssadmin delete shadows /for=D: /all

Then open Services.msc, find "Volume Shadow Copy", set it to Disabled. Reboot. That kills all snapshots on all drives — heavy-handed but works if you're desperate.

A better permanent fix for a specific file: use fsutil to set the file's miniversion limit low (though this only reduces the limit, not bypasses it). Actually, you can't bypass the file's limit. The real fix is to configure backup software to take snapshots less often, or to move the high-churn file to a separate volume with its own VSS schedule.

For databases, switch to Volume Shadow Copy-friendly backup mode: most modern DBs have a VSS writer. Use that instead of file-level copying.

Quick-Reference Summary Table

If none of these fix it, you've got something exotic. Check Event Viewer under Application and System logs for VSS errors. Also verify you're not hitting NTFS metadata corruption — run chkdsk /f /r on the drive. But 9 times out of 10, it's just shadow copy clutter.