A feature upgrade stages a complete new installation beside the current one, which is why it needs far more free space than an ordinary monthly update. When the system volume has less room than the upgrade expects, setup stops early or fails part way, and sometimes leaves the previous installation removed without completing the new one.
Microsoft states a minimum for the download and staging area, and the practical figure is higher once the previous installation is retained. The upgrade needs room for the new image, for migration data, and for the rollback copy.
A 128 GB SSD with 4 GB free will not upgrade, even though the machine is otherwise eligible. A 256 GB SSD with 25 GB free usually will, but leaves very little working space afterwards.
Check the free space on the system volume itself, not across all disks. Space on another drive cannot be used by setup.
Move large personal folders to another disk, uninstall programs you no longer use, and clear the temporary files that Storage settings reports. Empty the Recycle Bin separately.
Do not delete the Windows.old folder until the upgrade is complete. It is the rollback path, and removing it during a failed upgrade removes the option to go back.
Disconnect secondary drives that hold backups before starting setup. A setup that writes to the wrong disk is the most common cause of data loss during upgrades.
If unallocated space sits directly after the Windows volume on the same disk, extending it is straightforward. If another partition sits between them, the space has to be moved first, which is a larger change.
A recovery partition at the end of the disk often blocks the only free space on the disk. Moving it is safe with a partition tool that plans the whole operation before writing.
Take an image of the system before resizing. A resize is reversible in theory, but not after a failed upgrade has begun.
Qiling Disk Master can extend the system volume into free space, move a blocking partition, and show the resulting layout before anything is written.
Open the program and confirm the disk number against Disk Management. Note where the unallocated space sits relative to the Windows volume.
If the free space is adjacent, extend the Windows volume directly. If a partition blocks it, move that partition toward the end of the disk first, then extend.
Review the pending operations list, then apply. A system volume change is completed at restart, so plan the reboot.
Confirm the new size in File Explorer, aim for at least 30 GB free, then start the upgrade and keep the machine powered throughout.
No. Setup stages the new installation on the system volume, and unallocated space on a different disk cannot be used.
It is the documented minimum. Practical headroom of 30 GB or more avoids a failure near the end of the process.
It can resize or replace it. A blocked partition at the end of the disk is a common reason an upgrade cannot proceed.
Roll back within the retention window if Windows.old is intact, and copy any new files out before attempting the upgrade again.
For a failed upgrade with a specific error code, see 26H2 upgrade failed with 0x800F0922.