Rightek Rescue · Guides · Stuck on "Working on updates"

Stuck on "Working on updates" for hours? Here's how to fix it

When an update jams mid-install, Windows can loop on “Working on updates” or “Undoing changes” and never finish. Your files are safe — the update just needs to be un-stuck.

Updated · written and tested by Rightek IT Services

What you're seeing

  • “Working on updates 100% complete — don't turn off your PC” for hours
  • “Undoing changes made to your computer” that never completes
  • “Getting Windows ready — don't turn off your PC” stuck on a spinner
  • A restart loop after Windows Update

Why it happens

  • An update got interrupted (power loss, forced restart) and left a pending operation half-applied
  • A servicing file is corrupt, so Windows can neither finish nor cleanly undo it
  • Not enough free space for the update to complete

Fix it yourself — the manual steps

  1. Give it real time first — a genuine large update can take 1–2 hours. If it's been much longer with no disk activity, it's stuck.
  2. Force off (hold power ~10s) and back on 2–3 times to reach Advanced Startup.
  3. Try Troubleshoot → Advanced options → Uninstall the latest quality update.
  4. Or from Command Prompt, revert the pending servicing operation with DISM (/RevertPendingActions against the offline image) — advanced.
  5. Reboot.

Stuck, or just slow? How to tell

Interrupting an update that was actually working is a good way to cause the very corruption you were worried about, so it is worth being sure. Three signals, in order of reliability:

  • The drive activity light. Flickering means work is happening, however slow. Completely dark for twenty minutes or more means it has stopped.
  • Time elapsed. A feature update on a mechanical hard drive can genuinely take two hours or more, and the percentage sits still for long stretches. On an SSD, anything past about an hour with no disk activity is stuck.
  • Does the machine respond at all? Caps Lock toggling its light means Windows is alive. Nothing at all suggests it has hung completely.

The honest advice is to give it longer than feels reasonable, once. Most "stuck" updates that people force off were twenty minutes from finishing.

Check free space before anything else

The most common cause of an update that cannot finish or cleanly roll back is simply not enough room. A feature update wants around 20 GB free, and it fails in awkward ways when it does not have it — including getting far enough to be mid-flight and then unable to complete.

From a Recovery Command Prompt, dir D:\ reports free space at the end. If it is under a few gigabytes, freeing space is the fix rather than any repair command.

Reverting the pending operation

If it really is wedged, the goal is to let Windows abandon the half-applied update rather than keep retrying it. From Advanced options → Command Prompt, with your Windows volume identified (it is usually not C: in here):

  • DISM /Image:D:\ /Cleanup-Image /RevertPendingActions — tells Windows to undo servicing operations that were started and not finished. This is the command that specifically addresses this state.
  • Then rename the update queue so Windows cannot immediately retry the same thing: ren D:\Windows\SoftwareDistribution SoftwareDistribution.old. Windows rebuilds that folder on the next successful boot.
  • Reboot. Expect one more slow start while it tidies up.

If it boots, let Windows Update run again when convenient — the update still needs applying, and it usually succeeds on a machine with room and a clean queue.

Stopping it happening again

Updates get interrupted for mundane reasons, and two of them are worth fixing:

  • Keep 20 GB free on the Windows drive. Storage Sense will do it automatically, and Windows Update Cleanup in Disk Cleanup usually recovers several gigabytes on its own.
  • Set active hours, so it does not begin installing while the machine is about to be shut down or unplugged — the two most common causes of an interrupted update.

⚡ The one-click way: let Rightek Rescue do it

Rescue detects a jammed update and reverts or finishes the half-applied changes so Windows can start — automatically, no DISM commands. It covers supported stuck-update states and tells you if yours isn’t one of them; some repairs need a Windows image or an internet connection. On any working PC: download Rescue, put it on a USB (one click makes it bootable), boot the affected PC from it, and choose Fix My PC. It tells you what it found first, and your files, accounts and programs stay where they are. Not sure what's wrong? It tells you free before it fixes anything.

FAQ

Will I lose my files?

Very unlikely. This is a boot/system problem, not a data problem - your files are almost always intact. Rescue repairs the system side and leaves your personal files where they are. Any repair on a damaged drive carries some risk, so copy irreplaceable files off first if you can.

Do I need a second computer?

Yes - any working PC to download Rescue and make the USB. Any USB stick 8GB+ works.

Which Windows versions are supported?

Windows 10 and 11. Rescue runs from the USB, outside your broken Windows, so it works even when Windows won't start.

How long is too long for Working on updates?

On a mechanical hard drive, a feature update can legitimately take two hours or more and the percentage may not move for long stretches. On an SSD, past about an hour with no drive activity it is stuck. The drive activity light is a better guide than the clock — flickering means progress, however slow.

Is it safe to force the PC off during an update?

It is exactly what causes this problem in the first place, so avoid it until you are reasonably confident nothing is happening. Check the drive activity light first. Once it genuinely is stuck, forcing off is the only option left and is how you reach the recovery tools.

Why did the update get stuck at all?

Most often not enough free space — a feature update wants around 20 GB and fails awkwardly without it. After that, an interrupted install from a forced restart or power loss, or a corrupt servicing file that Windows can neither apply nor cleanly undo.