Why Windows Updates Take Forever — and What Actually Fixes It

The download is the fast part

An update runs in three phases: download, online install, and the offline commit at reboot that you watch as "Working on updates." The offline phase lands tens of thousands of small files into the component store, and every single one is a random read-write. On an SSD that's seconds per batch; on a five-year-old mechanical drive it's minutes, and the progress counter in between reports nothing honest.

The online install is heavier than it looks too: the servicing stack verifies signatures, snapshots the current state for rollback, and a third-party antivirus typically inspects every file being replaced. That's why the same update takes 15 minutes on one machine and three hours on another — same network, same version of Windows.

The usual suspects, in order

Support queues fill with machines described as "slow to update" where the update isn't slow at all — it's retrying, failing, rolling back and starting over. Before blaming Windows, check the six things that actually decide update speed.

• A mechanical drive as C: — the single biggest factor: servicing is small random I/O, where an HDD is dozens of times slower than an SSD
• Months of skipped updates — the cumulative payload grows, and component store cleanup hasn't run once in all that time
• Less than 10–15% free on C: — Windows needs working room for staging, snapshots and rollback; without it, phases stretch and fail
• Third-party antivirus in aggressive mode — rescanning every replaced file doubles the install phase
• A corrupted component store — repeating 0x800f08xx errors and retry loops; fixed with DISM /RestoreHealth, not with patience
• A metered connection and Delivery Optimization limits — they throttle the one phase that is actually about the network

What actually speeds it up

Fix the pattern, not the symptom: if C: still lives on an HDD, migrate to an SSD; keep at least 10–15% of the drive free; and let monthly updates install monthly instead of banking them for a rainy weekend. Plug the laptop in before the reboot phase — on battery, Windows deliberately stretches updates so it doesn't die mid-commit. And if a specific update has failed twice, don't hit retry a third time: repair the store first with DISM /Online /Cleanup-Image /RestoreHealth, then run sfc /scannow, and only then try again.

After a big feature update, the leftovers become the next slowdown: Windows.old holding 20–30 GB, Delivery Optimization files, superseded components. That's the part Kleaner PRO clears in one pass, so the next update has room to work.

Questions and Answers

Read next