Windows Update Stuck: How to Tell If It's Frozen & Safely Fix It

First question: is it actually stuck, or just slow?

This is the step almost everyone skips, and it's the one that prevents most disasters. A Windows update screen sitting at 27%, 100%, or on "Working on updates" looks frozen, but Windows is often grinding away in the background where you can't see it. Large feature updates and monthly cumulative updates move files, decompress packages, and reconfigure your system, and that work doesn't always show smooth percentage movement.

The single best signal is disk activity. On a laptop or desktop with a physical drive light, watch it: if it's flickering, the machine is working, not frozen. No activity light? Listen for the fan ramping up and down, or press the keyboard and watch for any caps-lock LED response. On a modern SSD-only laptop you may have no light at all, so the percentage and the clock become your tools.

Give a major update real time before judging it stuck. The mistake is forcing a power-off at 30% after ten minutes, which is exactly when you can corrupt your installation.

How long should you actually wait?

Patience here is free, and forcing a restart at the wrong moment is not. Here are realistic windows for 2026-era Windows 10 and Windows 11 on typical hardware:

• Monthly cumulative update: 15 to 40 minutes, sometimes longer on older spinning hard drives.
• Feature update (new build): 30 to 90 minutes, including multiple restarts where it sits on a percentage each time.
• "Working on updates, don't turn off your computer": can legitimately run 20 to 60+ minutes, especially after a big update.

A reasonable rule: if the percentage has not moved at all in two to three hours and there is zero disk activity, you can treat it as genuinely stuck. If it ever jumps, even from 61% to 62%, reset your clock and keep waiting. Overnight is fine for a feature update; many people wake up to a finished machine.

Genuinely stuck: force restart and let Windows roll back

Once you're confident it's frozen (hours, same percentage, no disk activity), a forced restart is the correct first move, not a last resort. Press and hold the power button for about 10 seconds until the machine powers off completely, wait a few seconds, then power back on.

In most cases Windows detects the interrupted update on boot and shows "Undoing changes made to your computer" or "We couldn't complete the updates, undoing changes." Let this finish; it's Windows safely rolling back to your previous working state. This can also take 20 to 40 minutes, so apply the same patience.

If the machine boots normally afterward, great. If it gets stuck on the rollback or enters a boot loop, restart again and Windows should eventually offer the recovery (Windows RE) screen, where you can choose Troubleshoot and, if needed, Uninstall the latest quality or feature update. That removes the problem update so you can boot, then retry it cleanly later.

Boot to Safe Mode and reset Windows Update

If Windows boots but the update keeps re-failing, the next step is to clear the update cache and start fresh. First try the built-in tool: Settings > System > Troubleshoot > Other troubleshooters > Windows Update. It quietly fixes a surprising number of stuck-update cases.

If that doesn't work, manually reset Windows Update. It's safest from Safe Mode (hold Shift while clicking Restart, then Troubleshoot > Advanced options > Startup Settings > Restart > press 4). Open an elevated Command Prompt (run as administrator) and stop the services:

• net stop wuauserv
• net stop bits
• net stop cryptsvc

Then rename the two cache folders so Windows rebuilds them clean:

• ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
• ren %systemroot%\System32\catroot2 catroot2.old

Restart the services with net start wuauserv, net start bits, and net start cryptsvc, then reboot and check for updates again. Windows downloads what it needs from scratch, which clears most corrupted-download jams.

Repair system files and free up disk space

Updates fail to install when the system image is damaged or there simply isn't room. From an elevated Command Prompt, run these two repair tools in order and let each finish:

• sfc /scannow — scans and repairs protected Windows files.
• DISM /Online /Cleanup-Image /RestoreHealth — repairs the underlying Windows image that updates build on.

Disk space is an underrated culprit. Feature updates can need 20 GB or more of free space to stage and install. If your drive is nearly full, the update can stall indefinitely. Open Settings > System > Storage, run Storage Sense or Disk Cleanup, and clear at least several gigabytes. If your drive is also pinned at 100% usage and crawling, that's a separate issue worth fixing first; see our guide on how to fix 100% disk usage in Windows.

Once space and system files are healthy, pause updates (Settings > Windows Update), reboot, then resume and install one update at a time so you can see exactly which one fails if a problem returns.

When one specific KB keeps failing

Sometimes everything else installs fine and a single update, identified by a KB number like KB5039000, refuses to go through and throws an error code. When that happens, you can bypass Windows Update entirely.

Note the exact KB number from Windows Update history, then go to the official Microsoft Update Catalog (catalog.update.microsoft.com), search that KB, and download the standalone .msu package that matches your version (for example, Windows 11 24H2 or 25H2, x64). Run it manually. This sidesteps the usual download-and-stage pipeline and installs the update directly, which often clears a stubborn single-KB failure.

If a specific update is what broke your machine and it's now in a boot loop or causing crashes such as a blue screen of death, uninstall that update from recovery first (as above), confirm the system is stable, then decide whether to reinstall it manually or wait for Microsoft to ship a fixed version.

Symptom, likely cause and fix at a glance

Use this quick reference to match what you're seeing to the right action. Find your nearest match and start there rather than trying everything at once.

Symptom	Likely cause	What to do
Stuck at a % but disk light flickering	Normal — still installing	Wait; do not power off
Same % for 3+ hours, no disk activity	Genuinely frozen	Hold power 10s, let it roll back
"Undoing changes" then boots fine	Update interrupted, rolled back	Reset Windows Update, retry
Loops on "Undoing changes" / won't boot	Damaged update or system files	Recovery > uninstall latest update
Download stuck at 0% or a fixed %	Corrupted update cache	Reset Windows Update (SoftwareDistribution)
Install fails repeatedly with error code	Damaged image or low disk space	SFC + DISM, free up space
One KB always fails, others install	Bad delivery of that package	Install it from Microsoft Update Catalog

If your PC won't power on at all after an interrupted update, that's a different problem; start with our guide on what to do when a laptop won't turn on.

One serious warning: never force-off during the install phase if the disk light is active. Cutting power mid-write can corrupt Windows and, in rare cases, your files. If you've already done that and the machine won't boot or files look missing, stop making changes and consider professional data recovery before you overwrite anything.