0X80070070 Disk Full Error: Fix It in 2 Minutes

You know there's space on that drive, but Windows keeps throwing the 0X80070070 error. Annoying as hell. Fixed this one dozens of times — it's almost never about actual files you can see.

The Quick Fix: Free Up Shadow Copy Space

The culprit is almost always Volume Shadow Copy (VSS) storage. Windows holds onto old restore points and backup snapshots even when you think it's not. These don't show in normal disk usage. Here's the fastest way to clear them:

1. Open Command Prompt as Administrator (right-click Start, pick Command Prompt (Admin) or Terminal (Admin)).
2. Type: vssadmin list shadowstorage and hit Enter. You'll see how much space shadow copies are using — often 10-30 GB or more.
3. To delete all old shadow copies, run: vssadmin delete shadows /all /quiet. This wipes every restore point and backup snapshot. No undo.
4. Then set a max limit for future shadow copies. Run: vssadmin resize shadowstorage /for=C: /on=C: /maxsize=5GB (replace C: with your drive letter, and 5GB with whatever cap you want — I use 5%).
5. Finally, run chkdsk C: /f if you want, but not strictly necessary. Reboot and try your operation again.

That's it. 9 times out of 10 this clears the error immediately.

Why This Works

When Windows needs to write to a disk, it checks actual free space minus any reserved space for system functions. Shadow copies reserve a chunk of the disk (default is 10% of the drive size) — but old snapshots can fill that reserved space even if the visible free space looks fine. The error code 0X80070070 fires when the system tries to write but hits that reservation. By deleting stale snapshots and capping the reservation, you give the OS room to breathe. This is exactly how Windows Update installs fail, or when you can't write a file bigger than 4 GB despite having 50 GB free.

Less Common Variations

Shadow copies aren't the only offender. Here's what else I've seen trigger this error:

1. Page File Too Big

If you have a small SSD (128 GB or less) and a page file set to "System managed size," Windows can allocate a huge chunk — 16 GB or more. That reserved space counts toward the "full" calculation. Check with wmic pagefile list /format:list. If it's over 8 GB on a small drive, set a fixed size: 4-8 GB depending on your RAM.

2. Windows Update Staging Folder

The C:\Windows\SoftwareDistribution folder can bloat to 20+ GB after updates fail. Stop the Windows Update service (net stop wuauserv), delete everything inside that folder, then restart the service (net start wuauserv). Don't delete the folder itself.

3. Recycle Bin Oversized

By default, the Recycle Bin takes 10% of each drive. If you have a 2 TB drive, that's 200 GB reserved — invisible to normal cleanup tools. Right-click Recycle Bin > Properties, set the max size to something sane like 5% or 10 GB.

4. Hidden System Restore Points

Even after deleting shadow copies, a corrupted restore point can hang on. Run diskcleanup, click "Clean up system files," then check "System Restore and Shadow Copies" in the list. That'll nuke the rest.

Prevention

You don't want to keep hitting this. Three things:

• Cap shadow storage right after you fix it — use the vssadmin resize command above. I set it to 5% on client machines.
• Run Disk Cleanup monthly — the built-in tool (cleanmgr) with "Clean up system files" handles most junk. Schedule it if you're lazy.
• Monitor free space — anything below 10% on a system drive will trigger this eventually, especially with updates. Use a simple script or tool like WizTree to see where space goes. I check drives monthly.

One last thing: if you're running a virtual machine or a USB drive, this error can pop when the host/drive is physically full or if it's formatted as FAT32 (max file size 4 GB). For FAT32, reformat to NTFS. That's a different beast, but I've seen it confuse people into thinking it's the Windows error.