Why free space decides the outcome
Setup needs room for three things at once: the downloaded payload of several gigabytes, the staged copy of the new OS, and the safety copy of your current system that becomes Windows.old. On a disk with 10 GB free, the update downloads, stages, runs for forty minutes and then rolls back with an error in the 0x80070070 family — disk full, expressed in hexadecimal. Windows will refuse to start an update well below its needs, but it underestimates, and users with 128 GB SSDs learn this every fall.
The working number is 20 GB free before you begin, 30 if you can, which sounds like superstition until you see what the folders weigh after the fact: Windows.old alone typically holds 15–25 GB. Space is cheap insurance — reclaiming it beforehand is a ten-minute chore, while an update that fails at 92% and rolls back is an evening.
The night-before checklist
Run this the evening before the update, not during the countdown screen. Every item takes minutes and each one removes a distinct failure mode.
- 20 GB free on C: minimum, 30 GB comfortable — check Settings → System → Storage
- Delete the previous Windows.old if one is still there; it is dead weight the new update cannot reuse
- Empty the Recycle Bin and %TEMP%, and clear old update files via Disk Cleanup → Clean up system files
- Copy irreplaceable files — documents, photos, project folders — somewhere that is not this disk
- Save the BitLocker recovery key where you can reach it from another device: it is asked for after some updates
- Plug in AC power, budget 30–90 minutes, and do not plan to work during the restart cycles
What a backup that counts looks like
Windows.old is not a backup, whatever it feels like from the outside: it is a rollback mechanism that Windows deletes automatically after ten days, and it lives on the same physical disk that the update is actively rewriting. If the update fails halfway or the drive dies, Windows.old dies with it. A backup that counts is a copy on different hardware — an external drive, a NAS, or cloud storage — made before the update starts.
The pragmatic minimum is your data folders copied to an external drive plus a quick sanity check that the copy opens. The gold standard is a full disk image with a tool that can restore the whole system, verified once by actually restoring something small. For the space side, Kleaner PRO clears the update leftovers, old Windows.old folders and temp junk in one pass, which is the fastest honest route to that 20 GB threshold on a drive that has been tight for years.
Questions and Answers
How much free space does a Windows feature update need?
Plan for 20 GB free on C: minimum, 30 GB to be comfortable: the payload, the staged OS and the future Windows.old of 15–25 GB all compete for the same space. Updates that start with 10 GB routinely roll back with 0x80070070-family errors.
Should I delete Windows.old before updating?
Yes, if it is from a previous update — it frees 15–25 GB and the new update builds a fresh one. Keep it only if you are still inside the ten-day rollback window for that previous update and might still need to roll back.
Know what is included before you buy.
The one-time 30-minute trial covers core tools. PRO-labelled features stay locked until a paid license is activated.
Read next
Write to us: [email protected]