The short answer
Wait at least three hours before intervening, and watch the hard drive light rather than the percentage — the number regularly sits still while real work happens. Interrupting an update that is mid-write is what turns a slow update into a broken installation.
Updates appear frozen far more often than they actually are. Large feature updates move millions of files, and the progress indicator is an estimate that can stall for long stretches at 0, 27, 61 or 99 percent while the machine works underneath.
Telling stuck from slow
- Drive activity light. If it is flickering, work is happening. On machines without one, listen for a mechanical drive; an SSD is silent, so use the next test.
- Fan behaviour. Fans cycling up and down suggests real processing.
- Time elapsed. On an older machine with a hard drive, a feature update can take three to six hours. On an SSD, 20 to 40 minutes is typical.
- Percentage over an hour. Note the number, come back an hour later. Identical and no drive activity is the point at which it is genuinely stuck.
Cutting power while Windows is writing system files can leave an installation that will not boot. If you must intervene, intervene at Downloading, not while it is applying. Wait out the applying phase however long it takes.
If it really is stuck
Force a restart, once
Hold the power button until the machine switches off, wait 30 seconds, and start it again. Windows usually detects the incomplete update and rolls it back automatically, which can itself take a while. Let it finish.
Disconnect peripherals and retry
External drives, printers, docks and card readers all cause update failures far more often than people expect. Unplug everything except keyboard, mouse and power, then retry the update.
Run the built-in troubleshooter
Settings, System, Troubleshoot, Other troubleshooters, then run Windows Update. It resets the update components automatically and fixes a reasonable share of cases without any manual work.
Clear the update cache manually
Open Command Prompt as administrator and run these in order: net stop wuauserv, then net stop bits, then rename the folder with ren C:\\Windows\\SoftwareDistribution SoftwareDistribution.old, then net start wuauserv and net start bits. This discards a corrupted download so Windows fetches a clean copy.
Free up disk space
Feature updates need 20 GB or more of free space, and a nearly full drive is a common silent cause of a stalled update. Settings, System, Storage, Cleanup recommendations.
Repair the system files
Run DISM.exe /Online /Cleanup-image /Restorehealth, let it complete, then sfc /scannow. Together they repair the component store that updates install into.
Install it manually
Find the update’s KB number in your update history, download it from the Microsoft Update Catalog, and run it directly. For a feature update, the Installation Assistant or the Media Creation Tool performs an in-place upgrade that keeps your files and apps.
Frequently asked questions
How long should a Windows update take?
Cumulative monthly updates take 10 to 30 minutes. Feature updates take 30 minutes to an hour on an SSD, and several hours on a mechanical hard drive. Age of machine matters more than the size of the update.
Is it safe to turn off a PC stuck at 100 percent?
Not immediately. The final phase writes system files, and 100 percent does not mean finished. Give it at least two hours at 100 percent before forcing a restart.
Why do updates keep failing on my PC?
Most often insufficient disk space, a corrupted update cache, or an attached peripheral. The troubleshooter plus clearing SoftwareDistribution addresses the majority of repeat failures.
Can I skip an update that will not install?
You can pause updates for up to five weeks in Settings, which is reasonable while a problematic release is patched. Skipping security updates indefinitely is not advisable.
Watch the drive light, not the percentage, and give it three hours before you touch anything.
