Every Windows 11 Storage Change Since 24H2, Explained Without the Hype

24H2 (October 2024): checkpoints, enablement and the rollback debt

The 2024 update set the pattern that everything after it follows. Cumulative updates moved to a checkpoint model, so Windows Update downloads only the delta since the last checkpoint instead of re-fetching the whole payload — smaller monthly downloads and less cache churn. The upgrade itself came in two very different sizes: a small enablement package for PCs already on 23H2, and a full feature update for everyone else, which parked a Windows.old folder of typically 15–25 GB on drive C: for a ten-day rollback window.

24H2 also quietly raised the FAT32 formatting limit from 32 GB to 2 TB, ending a decades-old absurdity for large flash drives and SD cards. On the cleanup side, the writing went on the wall for the legacy Disk Cleanup utility: cleanmgr still launches, but Settings > System > Storage kept absorbing its categories release after release. And nothing changed underneath — WinSxS still accumulates superseded components, and DISM's StartComponentCleanup is still the honest tool for it.

25H2 (October 2025) and the cumulative cadence since

25H2 was an enablement release on the 24H2 base — build 26200, a download measured in hundreds of megabytes, with servicing shared across the whole 24H2/25H2 family. The storage story since then has been consolidation rather than revolution, which is exactly what an enablement release promises. The recurring items:

• Cleanup recommendations in Settings became the main door: temporary files, large or unused files, cloud-synced content and long-unopened apps in one list
• The temporary-files list covers the heavy categories directly — previous installations, Windows Update Cleanup, Delivery Optimization files — no cleanmgr needed
• Checkpoint updates kept download sizes down across the 24H2 family; Delivery Optimization still caches update files locally, so small drives still benefit from a purge after big upgrades
• Reserved storage behaves the same as before: a real factor on 64 GB devices, noise on anything larger
• Windows.old and the ten-day rollback rule are unchanged — the one guaranteed 15–25 GB win after any full upgrade, once you trust the machine

What still hasn't changed — and why that matters

An honest changelog includes the non-events. The component store floor still sits around 8–9 GB on a fresh install, and no update since 24H2 has found a way to shrink it meaningfully. The page file, the hibernation file and System Restore still claim their fixed slices of C:, and third-party “Windows 11 optimizers” promising to unlock build-specific gigabytes are selling the same DISM cleanup that has been valid for years.

So the maintenance playbook has actually gotten simpler, not more complicated. Enable Storage Sense for the weekly debris, run one deliberate pass through Settings > System > Storage > Temporary files after each feature update, and touch WinSxS only through StartComponentCleanup when the component store is genuinely fat. That routine was correct on 24H2, survived 25H2 unchanged, and — unless Microsoft restructures the component store outright — it will still be correct after the next annual name change.

Questions and Answers

Read next