Fix it now
0x80070070 is Win32 112, ERROR_DISK_FULL, reported straight from Windows. 0xC190020E is MOSETUP_E_INSTALLDISKSPACE_BLOCK, setup’s own check refusing because the system does not pass the disk space requirements to install the payload. The distinction that matters is which check refused: installing, or downloading.
cleanmgr
Dism.exe /online /Cleanup-Image /StartComponentCleanup
powercfg /hibernate off
- In Disk Cleanup, after choosing Clean up system files, tick Previous Windows installation(s), Temporary Windows installation files, Delivery Optimization files and the Recycle Bin. The previous installation is usually the largest single item on a machine upgraded recently.
- Let the component cleanup finish. It removes superseded components from the servicing store, which grows quietly across years of cumulative updates.
- Turn off hibernation only if the machine does not need it; the hiberfile is sized in proportion to installed memory.
- Check what is left in Settings, System, Storage and deal with the largest categories rather than guessing.
- If the drive is genuinely small, attach an external drive and let setup use it. Microsoft documents a minimum of 8 GB, with 16 GB recommended, formatted NTFS – FAT32 hits file size limits.
- Restart and run the upgrade again.
Microsoft’s published figures for an upgrade are 16 GB of free hard drive space for a 32-bit and 20 GB for a 64-bit installation. Windows 11’s own published requirement is separate and larger: 64 GB or greater available disk space.
If setup gets past its space checks into the download or copy phase, you are done. If not, the next section covers where the space actually goes and which check is failing.
Why it happens
An upgrade needs room for three things at once: the payload it downloads, the expanded image it applies, and a full copy of the current installation so the machine can roll back. That last one surprises people. It is why a download of a few gigabytes wants tens of gigabytes of headroom, and why freeing exactly enough space to fit the download does not help.
Setup checks for that room twice, and the codes tell you which check refused. 0xC190020C is MOSETUP_E_DOWNLOADDISKSPACE_BLOCK: the system does not pass the disk space requirements to download the payload. 0xC190020E is MOSETUP_E_INSTALLDISKSPACE_BLOCK: it does not pass the requirements to install it. The first means you never got the payload; the second means you have it and cannot use it. Knowing which one you are looking at tells you whether the download has already consumed some of the space you are now trying to free.
0xC19001DF is MOSETUP_E_DISK_FULL, the install cannot continue because the system is out of disk space, and 0x80070070 is the underlying Win32 error 112, ‘There is not enough space on the disk’. Microsoft’s tables group 0xC190020E with 0x80070070 paired against several extend codes and give them one shared mitigation: free up drive space before proceeding.
0x80070008 is the odd one out and it is worth reading properly. It is Win32 8, ERROR_NOT_ENOUGH_MEMORY, ‘Not enough memory resources are available to process this command.’ That is memory, not disk. If you are freeing gigabytes and this code keeps coming back, you are working on the wrong resource.
Ordinary accumulation on the system drive
You have this one if A machine several years old with a full drive, several user profiles and a previous Windows installation still present.
- Run Disk Cleanup as administrator and use Clean up system files so the system categories appear.
- Remove previous Windows installations, temporary installation files, delivery optimisation files and the recycle bin.
- Check Settings, System, Storage for what remains and work down the largest categories.
- Remove profiles that no longer sign in, through System Properties, Advanced, User Profiles.
Remove Windows.old through Disk Cleanup rather than by hand. It carries links and permissions a manual delete handles badly.
The servicing store has grown unchecked
You have this one if WinSxS is large, the machine has years of cumulative updates behind it, and Disk Cleanup alone does not free enough.
- Run
Dism.exe /online /Cleanup-Image /StartComponentCleanupand let it complete. - If more is needed and you accept the consequence,
Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBasecompacts further. - Restart and re-check free space before deciding whether to go further.
Microsoft’s warning on /ResetBase is exact: all existing update packages cannot be uninstalled after the command completes, though it does not block uninstalling future update packages. Do not run it on a machine you may need to roll an update back on.
The drive is simply too small for a feature update
You have this one if A tablet or budget device with a small eMMC drive, where cleanup frees a little and it is consumed again immediately.
- Attach an external drive before starting and accept setup’s offer to use external storage. Microsoft documents at least 8 GB, 16 GB recommended, formatted NTFS.
- Move the profile’s large folders to a memory card or external drive first.
- Consider
compact /compactos:always, which compresses the operating system binaries and sets the system to Compact state until an administrator changes it. - If none of that is enough, the device has reached the end of what can be upgraded in place.
Microsoft notes that USB drives are preferred over SD cards, because SD card drivers are not migrated on devices that do not support Connected Standby.
The space is free, but not where setup wants it
You have this one if A large data partition has plenty of room while the system partition is full.
- Extend the system partition into adjacent unallocated space with Disk Management, if the layout allows it.
- Relocate the page file to another volume from System Properties, Advanced, Performance settings.
- Move the profile’s data folders to the larger volume from each folder’s Location tab.
Extending a partition needs unallocated space immediately after it. Where a recovery partition sits in the way this becomes a repartitioning job, and that deserves a backup and its own maintenance window.
The failure is memory rather than disk
You have this one if 0x80070008 rather than 0x80070070, on a machine with little RAM or a very large number of installed applications.
- Restart, sign in, and start the upgrade without opening anything else first.
- Close background applications, particularly synchronisation clients and search indexers.
- Confirm the page file is enabled and system-managed rather than switched off by a tuning script.
Full reference
Which check refused
| Code | Published meaning |
|---|---|
0xC190020C |
MOSETUP_E_DOWNLOADDISKSPACE_BLOCK: does not pass the disk space requirements to download the payload |
0xC190020E |
MOSETUP_E_INSTALLDISKSPACE_BLOCK: does not pass the disk space requirements to install the payload |
0xC19001DF |
MOSETUP_E_DISK_FULL: the install cannot continue because the system is out of disk space |
0x80070070 |
Win32 112, ERROR_DISK_FULL: there is not enough space on the disk |
0x80070008 |
Win32 8, ERROR_NOT_ENOUGH_MEMORY: not enough memory resources are available |
Reclaiming space in order of return
| Action | What it typically frees |
|---|---|
| Remove a previous Windows installation with Disk Cleanup | The largest single item on a recently upgraded machine |
Dism.exe /online /Cleanup-Image /StartComponentCleanup |
Superseded components in the servicing store |
powercfg /hibernate off |
A file sized in proportion to installed memory |
| Relocate or resize the page file | Another file sized in proportion to installed memory |
| Set cloud-synced folders to online-only | Whatever the local copies are holding |
| Move user data off the system drive | On shared machines, often most of the used space |
The numbers, and which one applies
Two different figures get quoted at each other and they answer different questions. Microsoft’s guidance for the upgrade itself is 16 GB of free hard drive space for a 32-bit operating system and 20 GB for a 64-bit one, with the note that an external drive of at least 8 GB – 16 GB recommended, formatted NTFS – can be used for the process. Windows 11’s own minimum hardware requirement is different: 64 GB or greater available disk space, which is a statement about the machine rather than about headroom for the operation. A device can meet the second and still fail the first.
Using external storage properly
- Attach the drive before starting setup, not part way through.
- Format it NTFS. FAT32 runs into file size limits on the image.
- Prefer a USB drive over an SD card; SD card drivers are not migrated on devices without Connected Standby support.
- Accept setup’s offer to use it when prompted rather than pointing setup at it afterwards.
- Leave it connected until the upgrade has finished and the machine has restarted cleanly.
Before you run /ResetBase
- Ask whether you might need to uninstall a currently installed update. If the answer is yes, do not run it.
- Run
StartComponentCleanupon its own first and measure what it freed; frequently that is enough. - Understand what the warning does and does not say: existing update packages cannot be uninstalled afterwards, but future ones still can.
- Restart afterwards and re-measure before deciding you still need more space.
- On a fleet, decide the policy once rather than per machine, because it changes your rollback options across all of them.
When the space is there and setup still refuses
Check that you are measuring the volume setup cares about. On a machine with several volumes it is the system volume that matters, and a large free D: drive changes nothing. Check the recovery partition too – a full one produces its own family of failures around servicing rather than around the upgrade payload. And if the code is 0x80070008, stop freeing disk: that one is memory, and the answer is a restart and fewer things running.
When a licence is the actual fix
Freeing space costs nothing and should be the whole job on most machines. The licence question only arrives at the far end, on the small devices where cleanup frees a little and it is immediately consumed again – a 32 or 64 GB eMMC tablet that cannot hold the payload, the expanded image and a rollback copy at the same time. Those devices do not become upgradeable by buying anything, and an external drive is the supported way to get one more upgrade out of them rather than a permanent answer. If you decide to replace or rebuild such a machine, the replacement needs its own Windows entitlement, and where you are also moving from Home to Pro for management or encryption features, that is a Windows 11 Pro upgrade licence bought for the edition rather than for the space. A machine that is already licensed for the edition you are installing needs nothing: the digital licence survives an in-place upgrade and reactivates on its own. Try an external drive before you conclude the device is finished.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC190020E |
MOSETUP_E_INSTALLDISKSPACE_BLOCK: the system does not pass the disk space requirements to install the payload | Microsoft Learn |
0x80070070 |
Win32 112, ERROR_DISK_FULL: there is not enough space on the disk | Microsoft Learn |
0x80070008 |
Win32 8, ERROR_NOT_ENOUGH_MEMORY: not enough memory resources are available to process this command – memory rather than disk | Microsoft Learn |
0xC19001DF |
MOSETUP_E_DISK_FULL: the install cannot continue because the system is out of disk space | Microsoft Learn |
0xC190020C |
MOSETUP_E_DOWNLOADDISKSPACE_BLOCK: the system does not pass the disk space requirements to download the payload | Microsoft Learn |
Confirm the fix worked
- Free space on the system volume is comfortably above what setup asked for, not exactly at it.
- Setup moves past the preparation stage into the copy and restart phases.
winverreports the new build after the upgrade completes.- Disk Cleanup offers a previous Windows installation to remove once you are satisfied with the result, which reclaims the rollback copy.
- The machine still has working free space after the upgrade rather than being full again immediately.
Questions people ask about this
How much free space do I actually need?
Microsoft’s published guidance for the upgrade is 16 GB free for a 32-bit and 20 GB for a 64-bit installation. That is separate from Windows 11’s minimum hardware requirement of 64 GB or greater available disk space, which describes the machine rather than the operation. Aim comfortably above whichever applies.
Is it safe to delete Windows.old?
Yes, once you are satisfied with the upgrade – but do it through Disk Cleanup with Clean up system files rather than by hand. Removing it also removes your ability to roll back to the previous build, so wait until the machine has been in normal use for a few days.
Do I need a bigger drive or a new licence?
Neither, in most cases. Cleanup is usually enough, and an external drive gets a small device through an upgrade it could not otherwise do. A licence only enters it if you are replacing the machine or changing edition.
Does using an external drive slow the upgrade down?
Somewhat, because setup is writing to removable storage. It is the documented route for devices without the internal space, and a slower upgrade that completes beats a fast one that refuses to start.
I keep getting 0x80070008 and the drive has plenty of space. Why?
Because that code is about memory, not disk. It is Win32 error 8, not enough memory resources. Restart, start the upgrade before anything else, close synchronisation clients, and check the page file has not been switched off.
