After a Big Windows Update: The Files You Can Remove

What the update left behind

A feature update does not patch your existing Windows in place; it stages and installs a complete new build, then keeps the pieces needed to undo the whole operation. Windows.old is the old operating system, user profiles included, parked at the root of C: — commonly 20 to 30 GB, occasionally more. Alongside it sit the update payloads under C:\Windows\SoftwareDistribution\Download, the peer-distribution cache of Delivery Optimization, setup folders such as $GetCurrent, and superseded versions of components inside the WinSxS store. None of this is junk in the malicious sense; it is rollback insurance, and it expires.

That expiry is the part people miss: ten days after a feature update, Windows deletes Windows.old on its own through Storage Sense's automatic cleanup, and the WinSxS store trims itself gradually. If you can tolerate the full ten days, the machine cleans itself, and the only thing you are deciding is when, not whether. Cleaning earlier is legitimate — you lose the rollback option, that is all — and the safe ways to do it are built in.

The safe-delete checklist

Everything below is removable through Windows' own interface, in minutes, without boot media or anything exotic. The last item is the one to memorize, because it is the trap.

• Windows.old: Settings → System → Storage → Temporary files → Previous Windows installation(s) — or Disk Cleanup's item of the same name; removes the rollback and frees the bulk of the space
• Windows Update Cleanup: the Disk Cleanup item that removes superseded components from WinSxS; as irreversible as removing Windows.old, and the single biggest reclaim on machines that took several feature updates in a row
• Delivery Optimization files: Settings → System → Storage → Temporary files → Delivery Optimization files, or the advanced options of Delivery Optimization itself — gigabytes on update day
• $GetCurrent and $WINDOWS.~BT: hidden setup folders at the root of C: that linger after a successful upgrade; safe to delete once the build is stable, though Storage Sense eventually takes them anyway
• CBS and DISM logs: C:\Windows\Logs\CBS grows on heavy update days; these are plain logs, deletable while no update is mid-flight (some are held by the service — skip those)
• The Windows ESD folder — never: the ESD item in Disk Cleanup deletes the reset image, and Reset this PC stops being able to rebuild itself locally; the space saving is not worth a broken reset

Order of operations, and when not to bother

Do it in this order: confirm the new build is stable for a few days first, then remove Windows.old and the update caches, and only then run Windows Update Cleanup — because component cleanup makes the earlier steps pointless when done in reverse. The command DISM /Online /Cleanup-Image /StartComponentCleanup performs the same WinSxS trimming on demand if you prefer the command line. Keep two things in mind: if the update was a major jump and you have any doubt, the ten-day rollback window is cheap insurance you have already paid for in disk space; and if System Restore is on, the update process creates and rotates its own restore points, so an old point you remember may already be gone before your cleanup touches anything.

Questions and Answers

Read next