Windows 11 25H2: What the Release Actually Changes for Your Disk

What 25H2 is — and what it is not

An enablement package activates code that is already present in the 24H2 servicing branch, so a PC on 24H2 gets a download measured in hundreds of megabytes, not gigabytes, and the familiar build number 26100 becomes 26200. Devices coming from 23H2 or older still take the full jump, which includes the usual Windows.old aftermath. Servicing stays shared: cumulative updates ship once for the whole 24H2/25H2 family, and features keep arriving through those updates rather than waiting for the next annual name change.

The practical consequence for disk watchers: there is no new component store, no restructured WinSxS, and no second wave of system files. Everything you know about component cleanup, reserved storage and Delivery Optimization carries over without a footnote. If your cleanup habits were right for 24H2, they remain right for 25H2.

The storage-side changes worth knowing

Nothing here is revolutionary, but the Settings-first direction continues, and these are the items that actually touch your free space:

• Settings → System → Storage keeps consolidating: cleanup recommendations, temporary files and per-category disk usage in one place
• Cleanup recommendations now cover temporary files, large or unused files, files already synced to the cloud, and apps you have not opened in months
• The legacy Disk Cleanup tool (cleanmgr) still launches but keeps fading toward icon status — the Settings page is the maintained path
• Delivery Optimization still caches update files locally and on the local network — worth a purge on small drives after a big upgrade
• Windows.old after the jump holds the previous installation for about ten days, typically 20 GB and more, and is removable from the temporary files list

What to do with your free space after upgrading

The week after any feature update is the one time cleanup genuinely pays: the update leaves behind Windows.old, log files and temporary setup data that nothing will clean on its own. Open the temporary files list in Settings, keep the box for the previous installation unchecked until you are sure everything works, and remove the rest right away. If the machine runs fine after a few days, release the previous installation and reclaim the space — waiting does not make it safer.

Two honest notes to finish. First, enablement releases do not bring storage miracles, and any tool promising to "unlock 25H2-specific gigabytes" is selling the same WinSxS cleanup that was valid last year. Second, reserved storage, the chunk Windows sets aside for updates, behaves the same on 25H2 — on a 64 GB drive it is a real factor, on anything larger it is noise.

Questions and Answers

Read next