The screen says “Working on updates 30% complete. Don’t turn off your computer” — and it’s been saying that for two hours. Your instinct says force it off; your fear says that’s how PCs get bricked. Here’s the honest answer: most “stuck” updates are just slow, Windows is very good at rolling back failed updates on its own, and the safe move is a structured wait, then — only then — a controlled power-off that Windows treats as a failed attempt and reverses cleanly. This guide walks the full ladder: how to tell stuck from slow, when acting is safe, and how to fix the update properly once you’re back at your desktop.
Quick answer: give a quality update up to 2–3 hours (feature updates can take longer on older hardware), watching for any progress movement. If nothing has moved for hours, hold the power button for a full shutdown. Windows will either boot normally or revert the update and boot — it auto-uninstalls failed updates by design. Once you’re in, run the update troubleshooter, free up disk space, reset the update cache, and try again.
Stuck or just slow? How to tell
Microsoft doesn’t publish a fixed duration for updates — download size, install type, and hardware all change the math — which is exactly why “how long should I wait” is such a common question. Realistic anchors from real support threads: quality (monthly security) updates on a modern SSD usually finish in well under an hour; major annual feature updates can take well over an hour and sometimes a second long reboot cycle. Multiple users on Microsoft’s Q&A forums have reported their frozen-looking updates completing at the one-hour mark, at three hours, and overnight.
Signs the update is actually working, even when it looks dead:
- The hard-drive activity light is flickering (on desktops/laptops that have one) — disk activity means work is happening.
- The percentage changes at all, even slowly. Feature updates can sit at one number for 30+ minutes between steps.
- The number jumps backward or resets. Counter-intuitively, a bar that fills to some point and restarts from zero is the update installing in phases, not failing. A bar frozen at the exact same number for 2–3 hours is the actual worry sign.
One documented quirk worth knowing: Microsoft’s own troubleshooting notes describe a case where updates hang at “Working on updates 13%” for about 15 minutes and then the PC restarts with the updates uninstalled — that’s a built-in timeout doing its job, not damage.
The safe-wait timeline
| Elapsed (no progress) | What to do |
|---|---|
| 0–1 hour | Wait. Walk away. Nothing here is abnormal yet. |
| 1–3 hours | Still wait if the screen is a “Working on updates” percentage — especially for a feature update. Check the activity light. |
| 3+ hours, zero movement | Safe to force power off (next section). Windows rolls the update back. |
| Overnight, any state | If it’s still on the same screen in the morning, force power off with confidence. |
Why waiting is genuinely safer than acting early: Windows performs update work in committed stages, and interrupting mid-stage is the only realistic way a normal user turns a failed update into a broken one. Interrupting a stalled update mostly produces a rollback you’d have gotten anyway — but interrupting a working one risks corruption. You can’t always tell which is happening, so the wait buys certainty.
If you must force it off: do it safely
- Hold the physical power button for 5–10 seconds until the machine cuts power. Don’t pull the battery or switch off the PSU — same result, worse style.
- Turn it back on and watch. Three outcomes are normal: it boots to the desktop (update actually finished), it shows “Undoing changes made to your computer” and then boots (the common one), or it shows a “Choose an option” recovery screen — pick Start Windows normally / Continue.
- Don’t force it repeatedly. One forced shutdown to escape a genuine multi-hour freeze is safe. Repeatedly power-cutting a PC that’s mid-install is how you get an unbootable system — if the same screen reappears and freezes again, let it sit overnight before a second attempt.
Real-world confirmation, for the anxious: on Microsoft’s Q&A forums, a user whose 24H2 feature update had failed all week forced the shutdown after two hours on the update screen; the PC booted back, automatically reverted every change, and uninstalled the update. No data loss, no bricking — that rollback behavior is the designed path.
Once you’re back in: fix the update properly
Forced restarts get you a working PC, not a working update. The update is now pending again (or marked failed), and it’ll re-attempt — so fix the cause before it does. And check what else the failed attempt disturbed along the way: if your network connection no longer works, our ERR_INTERNET_DISCONNECTED guide covers the adapter-reset routine; if the keyboard or touchpad went strange, these keyboard troubleshooting steps fix most input oddities after updates.
Step 1: Run the Windows Update troubleshooter
Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run. It resets the update components automatically and fixes a surprising share of repeat failures. Microsoft’s troubleshooter page lists everything it touches.
Step 2: Free up disk space
Updates need free room to download, unpack, and stage — Microsoft’s troubleshooting documentation cites 16 GB free for 32-bit Windows and 20 GB for 64-bit, and support advisors suggest aiming much higher for the big annual feature updates. If you’re running near-full, clear space first: Disk Cleanup (run cleanmgr) → Clean up system files is the quick route. Low disk space is the most under-appreciated cause of updates that stall at 0%.
Step 3: Reset the update cache
The SoftwareDistribution folder is where Windows stages downloads; a corrupted staging area causes infinite “downloading 100%” or 0% hangs:
- Open Command Prompt or Terminal as administrator.
- Run:
net stop wuauservthennet stop bits - Rename the folder:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old - Restart the services:
net start wuauservthennet start bits - Check for updates again — Windows rebuilds the folder fresh.
(The “folder doesn’t exist” replies you see under forum advice usually mean Windows had already cleaned it, or OneDrive-style paths — the rename command fails harmlessly if it’s genuinely absent.)
Step 4: Repair system files
If an update keeps failing at the same percentage, Windows’ own files may be damaged. In an admin Command Prompt:
DISM /Online /Cleanup-Image /RestoreHealth— repairs the Windows component store (give it 10–20 minutes; it can look stuck at 62% — that’s normal).sfc /scannow— verifies and repairs system files. Microsoft’s sfc reference documents the switches and what the results mean.
Then run the update again.
Step 5: Install the problem update manually
If one specific update (a KB number in Update history) keeps failing, download it directly from the Microsoft Update Catalog and install it by hand — the standalone installer uses a different code path than Windows Update and often succeeds where the automatic route loops. Microsoft’s master update-troubleshooting page walks the complete ladder this section summarizes, including the advanced options.
What NOT to do
- Don’t cut power during the percentage screens on purpose “to cancel it” — that’s the one move that can corrupt Windows itself, and the way files genuinely get lost. If a bad shutdown ever does take files with it, our deleted-file recovery guide covers the recovery routes that actually work.
- Don’t hard-reset repeatedly. One attempt, then wait hours before another.
- Don’t start a feature update with a nearly full disk — that’s how you manufacture a stuck update in the first place.
- Don’t trust “registry fix” scripts from random videos. The legitimate tweaks (like Microsoft’s documented timeout adjustment) are documented on Microsoft’s own pages; everything else is roulette.
Windows 10 note for 2026
Windows 10 reached end of support in October 2025. Regular updates have stopped; only enrolled devices (via the Extended Security Updates program) receive security fixes, and they don’t include new features. If your Windows 10 PC keeps “failing” updates, check whether it’s actually stuck in an ESU-enrollment prompt — and know that a clean upgrade to Windows 11 (or a new PC) is the supported path forward.
FAQ
How long should a Windows update take?
There’s no official number — Microsoft says it depends on update size, internet speed, and your device. In practice: monthly updates typically finish in minutes to an hour on an SSD; annual feature updates can legitimately take several hours including multiple restarts. Microsoft’s update FAQ covers what affects the timing.
Is it safe to turn off my computer during an update?
During the percentage screens, only as a last resort after 3+ hours of zero progress — and one controlled power-off is enough. Windows handles the interrupted update as a failure and rolls it back. Never cut power repeatedly, and never during the earliest boot stages of a feature update.
Will a stuck update delete my files?
No. Updates modify Windows itself, not your documents. Even the rollback path (“Undoing changes”) only removes update components. Your files survive every outcome here — the rare disasters come from repeated power cuts mid-install, not from the update process.
My update is stuck at 99% — is it almost done?
The last percent includes cleanup and final configuration, and it can genuinely sit there for a long time on slower disks. Give it to the 2–3 hour mark like any other stage. A 99% hang that outlasts the evening is treated the same as any other freeze.
Why does my PC keep saying “Undoing changes” every time it restarts?
Windows attempted the update, failed at the same internal step, and rolled back — a loop. That means a cause needs fixing (steps 1–5 above) before the next attempt, or the loop repeats. The manual-install route in step 5 breaks this loop more often than anything else.
Can a stuck update brick my PC?
Effectively no, if you follow the rules: a single forced shutdown after a long freeze is recovered by Windows’ rollback or its recovery tools. True bricking requires interrupting the update many times or cutting power during the narrow initial-install window — which is exactly what the waiting timeline protects you from.
