Windows Update Error 0x80070070: What ERROR_DISK_FULL Means and How to Free Space Fast

Error 0x80070070 is the most straightforward Windows Update error you can encounter — and the most actionable. The message Windows shows makes it clear:

“Updates are available, but we currently require additional space for downloading. Let’s clear some space by removing any unnecessary files and apps, and we’ll try again.”

Or during feature upgrades:

“Windows cannot copy files required for installation. 0x80070070”

“Installation failure during the SAFE_OS phase caused by insufficient disk space.”

Error code 0x80070070 indicates that there is not enough disk space available, most commonly when installing Windows updates or during setup/upgrade.

Unlike errors such as 0x80073712 or 0x800f081f that require technical repair tools, 0x80070070 is almost always fixed by freeing up space on your C: drive. This guide explains exactly how much space you need, every method to reclaim it, and the less obvious causes like Disk Quotas that can trigger the error even when your drive appears to have adequate free space.

What Does 0x80070070 Mean?

0x80070070 is ERROR_DISK_FULL — a standard Windows system error indicating the target drive has no room for the operation being attempted.

The error occurs because not enough disk space exists on your physical computer or VM to store Windows updates for installation.

Windows Update requires disk space at every stage of the update process. It needs space in the SoftwareDistribution folder to download the update package. It needs additional space to extract and stage the update files. It needs more space still during the actual installation phase when new files are written alongside existing ones before the swap is made. If any of these stages runs out of room, 0x80070070 appears and the update halts.

This is a clean, non-destructive failure. No files are corrupted and Windows remains in its current working state. The update simply could not proceed.

How Much Space Does Windows Need?

Microsoft recommends at least 20GB of free space on the C: drive for standard cumulative update installation. Feature updates — like upgrading to a new Windows 11 version — require more.

Specific space requirements:

Monthly cumulative security updates — 3GB to 8GB of free space minimum, depending on update size. July 2026’s KB5101650 for Windows 11 was over 4GB.

Windows 11 feature updates — the KB5054156 Windows 11 25H2 enablement package requires the system to have adequate free space beyond the download itself for staging and swap files.

Microsoft’s stated minimum for running Windows 11 is 64GB of total storage — and on low-storage devices with 32GB or 64GB eMMC drives, 0x80070070 is common as the drive fills up over time.

To check your current free space: open File Explorer, right-click Local Disk C:, select Properties. The free space figure shown is what you are working with.

0x80070070 vs Similar Error Codes

Error Code	Technical Name	Core Issue
0x80070070	ERROR_DISK_FULL	Not enough C: drive space
0x800f0922	—	EFI System Partition full
0xc0430001	Code Integrity failure	EFI boot components cannot write
0x8024200d	WU_E_UH_NEEDANOTHERDOWNLOAD	Download payload corrupted
0x80244022	WU_E_PT_HTTP_STATUS_SERVICE_UNAVAIL	Server unavailable

The distinction between 0x80070070 and 0x800f0922 is important. Both involve disk space — but they affect different partitions.

0x80070070 affects the main C: drive — Windows cannot download or stage the update package because the primary system drive is full.

0x800f0922 affects the hidden EFI System Partition — a separate small partition that holds boot files. The EFI partition can be full even when C: has gigabytes of free space. The fixes are completely different.

If you have plenty of free space on C: but still see a disk-related error, check whether 0x800f0922 is the actual error — the EFI partition fix is in a separate guide.

Every Root Cause — Including the Less Obvious Ones

Cause 1 — Simply Not Enough Free Space on C:

The most common cause. The C: drive genuinely does not have enough room. This is most frequent on:

Low-storage laptops and tablets — devices with 32GB or 64GB eMMC drives where the OS and apps already consume most of the storage.

PCs that have accumulated years of files, downloads, and installed software.

Devices where a previous Windows version (Windows.old folder) is still present after an upgrade.

Cause 2 — Disk Quota Restrictions

This is the less obvious cause that trips up many users and enterprise administrators.

If enabled, disk quotas can restrict available space, leading to 0x80070070.

Disk Quotas are a Windows feature that limits how much disk space individual users can consume. When a Quota is set — particularly on a managed enterprise device — the effective available space is capped at the quota limit, not the actual physical free space on the drive.

This means a drive with 50GB of physical free space can still trigger 0x80070070 if the user’s quota has been reached. The update process sees only the quota-limited available space, hits the wall, and fails.

Cause 3 — Accumulated Delivery Optimization Files

Windows uses Delivery Optimization to download updates and share them with other devices on the network. These cached files accumulate in a dedicated folder and can consume gigabytes of space without being visible in typical file browsing.

Cause 4 — Windows.old Folder From Previous Upgrades

After a major Windows version upgrade, the previous Windows installation is saved to C:\Windows.old as a rollback option. This folder can be 15GB to 25GB in size. It is automatically deleted after 10 days, but if you upgraded recently and the 10-day window has not passed, it is still consuming significant space.

Cause 5 — Recycle Bin Not Emptied

Files in the Recycle Bin continue to occupy disk space even after deletion. A Recycle Bin that has never been emptied can hold gigabytes of data that counts against available space.

Cause 6 — Virtual Machine Disk Not Extended

On Azure VMs and other virtualized environments, 0x80070070 has a specific additional cause: the VM disk has not been extended when the storage requirement increased.

If you’re working on an Azure virtual machine, you can use Azure PowerShell cmdlets to collect Windows Update log information.

VM administrators need to extend the OS disk in the virtualization platform and then allow Windows to recognize the enlarged disk before Windows Update can proceed.

Diagnostic Step — Check SoftwareDistribution Download Logs

If you want to confirm 0x80070070 is definitely a disk space issue before clearing files, check where the download was attempting to go.

Open Event Viewer. Navigate to Applications and Services Logs, Microsoft, Windows, WindowsUpdateClient, Operational. Look for failed events. The log will show entries like:

Windows failed to download from [URL] to local path = 
C:\Windows\SoftwareDistribution\Download\[hash] 
with error 0x80070070

This confirms the download was trying to write to the SoftwareDistribution folder and ran out of space. Now you know which drive and folder to target.

Every Fix — In Order

Fix 1 — Run Disk Cleanup (System Files)

The built-in Disk Cleanup tool is the fastest and safest way to reclaim significant space on most Windows PCs.

Open Start, search for Disk Cleanup and run it. Select your C: drive. When the initial scan completes, click Clean up system files — this is the critical button. It re-runs the scan with elevated permissions to find additional categories including previous Windows installations.

Select these categories for deletion:

Windows Update Cleanup — previous update installation files, often 500MB to several GB.

Delivery Optimization Files — cached update files shared via Delivery Optimization, often 1GB to 10GB.

Previous Windows installations — the Windows.old folder, 15GB to 25GB if present.

Temporary files — generated by apps and the system, typically 500MB to 2GB.

Recycle Bin — files pending permanent deletion.

Downloaded Program Files — obsolete web component files.

Important: Do not delete Temporary Files before Windows Update if Windows warns against it specifically — in some update scenarios, Windows needs these temporary files during the update process itself.

Click OK, confirm deletion, and restart before retrying Windows Update.

Fix 2 — Use Storage Sense

Storage Sense is Windows 11 and Windows 10’s built-in automatic space management tool.

Go to Settings, System, Storage. Enable Storage Sense by clicking the toggle. Then click Configure Storage Sense or run it now and click Run Storage Sense now.

Storage Sense removes temporary files, empties the Recycle Bin automatically, and — when configured — removes the Windows.old folder after the specified period. Running it manually gives you immediate cleanup without waiting for the next scheduled run.

Fix 3 — Delete the Windows.old Folder

If a major Windows upgrade was completed within the last 10 days, the Windows.old folder is likely consuming 15GB to 25GB on your C: drive.

Do not delete Windows.old manually through File Explorer — this can leave orphaned files. Use Disk Cleanup with Clean up system files enabled, which handles the deletion correctly and removes all associated components.

After deleting Windows.old, you can no longer roll back to the previous Windows version. If you are satisfied with the current version, this is safe to do.

Fix 4 — Uninstall Unused Applications

Open Settings, Apps, Installed apps. Sort by size using the Sort by dropdown to identify which applications are consuming the most space. Uninstall applications you no longer use, starting with the largest.

Also check Control Panel, Programs, Programs and Features for applications that may not appear in the Settings list.

Fix 5 — Move Large Files to External Drive

Large files — videos, ISO images, backups, large documents — can be moved to an external hard drive or USB drive to free space on C: without permanent deletion.

Connect an external drive. Move the large files from your C: drive to the external drive. Then retry Windows Update.

After the update completes successfully, you can move the files back if needed. For ongoing space management on small-storage devices, keeping large media on an external drive is practical long-term.

Fix 6 — Use External Storage for Windows Update

For devices with genuinely small drives where clearing space still leaves insufficient room, Windows Update has a specific feature for using external storage during the update process.

Connect a USB drive or external hard drive with at least 10GB of free space. Go to Settings, Windows Update. Windows may automatically detect insufficient space and offer to use the connected external storage for the update process. Follow the prompts to allow Windows Update to use the external drive for temporary files during the update.

For feature upgrades specifically — Microsoft recommends using this option on devices where the C: drive cannot be expanded.

Fix 7 — Disable Disk Quota (Quota-Restricted Devices)

If your device has Disk Quotas enabled — common on managed enterprise devices — disabling them may resolve 0x80070070 even if the drive appears to have adequate physical free space.

Open File Explorer. Right-click Local Disk C: and select Properties. Go to the Quota tab. If Disk Quota is visible, uncheck Enable quota management. Click Apply, then OK. Restart and retry Windows Update.

On enterprise-managed devices, Disk Quotas may be set by Group Policy — in which case uncheck must be done through the Group Policy Management console or by an IT administrator rather than locally.

Fix 8 — Clear Delivery Optimization Cache via Settings

If the Disk Cleanup did not fully remove Delivery Optimization files, clear them directly through Settings.

Go to Settings, Windows Update, Advanced Options, Delivery Optimization, Activity Monitor. Review the cached content size. Then go back to Settings, System, Storage, Temporary Files and select Delivery Optimization Files. Click Remove files.

This targets the Delivery Optimization cache specifically and may recover additional space beyond what Disk Cleanup found.

Fix 9 — Use Windows Media Creation Tool (Feature Update Alternative)

For feature update failures with 0x80070070 — particularly when upgrading to a new Windows 11 version — the Windows Media Creation Tool provides an alternative upgrade path that manages space differently from Windows Update.

Download the Windows 11 Media Creation Tool from Microsoft’s official software download page. Run it and select Upgrade this PC now. Choose Keep personal files and apps.

Bypass standard update mechanisms by downloading the Windows Media Creation Tool, selecting the Upgrade this PC now option, and choosing to keep personal files and apps.

The Media Creation Tool manages the upgrade staging differently from Windows Update and can sometimes complete upgrades on devices where the standard Windows Update method fails with 0x80070070.

Fix 10 — Extend VM Disk (Azure and Virtual Machine Environments)

For 0x80070070 on Azure VMs or other virtualized environments:

In the Azure Portal, navigate to your VM’s disk settings and extend the OS disk size. The change requires a restart of the VM. After the VM restarts, use Disk Management in Windows to extend the C: partition into the newly allocated space.

On VMware or Hyper-V, extend the virtual disk through the hypervisor management console and then extend the partition in Windows using Disk Management or diskpart.

After extending the disk and partition, retry Windows Update.

How Much Space Should You Have After Cleanup?

After cleanup, verify you have sufficient free space before retrying Windows Update.

Go to File Explorer, right-click C:, Properties. The free space shown should be at least 20GB for monthly cumulative updates. For feature upgrades such as moving to Windows 11 25H2, aim for 30GB or more.

If you have cleared everything possible and still cannot reach 20GB free on a small-storage device, consider whether a larger storage solution is needed — either upgrading the internal drive or permanently using an external drive for large files.

Keeping Space Available — Prevention

0x80070070 is a recurring issue on low-storage devices if space management is left to accumulate over time. These habits prevent it from coming back:

Enable Storage Sense on an automatic schedule — go to Settings, System, Storage, Storage Sense and set it to run every month. Configure it to delete temporary files and the previous Windows installation after 30 days.

After every major Windows feature update — wait 10 days, verify the upgrade is stable, then run Disk Cleanup with Clean up system files to remove the Windows.old folder.

Keep your Recycle Bin empty or set it to auto-delete after 30 days — right-click the Recycle Bin, select Properties, and set the maximum size appropriately.

Move media and large files to external storage or cloud storage on devices with 64GB or smaller drives.

Frequently Asked Questions