Get a Frozen Windows Update Moving Again
A Windows Update screen that appears stuck at a percentage can be caused by a slow download, a delayed installation phase, limited disk space, corrupted update components, driver conflicts, or damaged system files. This guide explains how to tell a normal pause from a genuine failure, when it is safe to wait, and how to restart the update process without risking data. It covers basic checks such as power, internet access, storage, and peripheral devices, then outlines the built-in Windows Update troubleshooter, service resets, DISM and System File Checker repairs, and manual update options. It also explains when advanced recovery steps or professional help may be appropriate.
Seeing Windows Update sit at the same percentage can be unsettling, especially when the message says not to turn off the computer. In many cases, the update is still working in the background: large files may be unpacked, drivers may be migrated, or the system may be configuring components that do not change the visible progress counter for a long time. However, a percentage that does not move for hours can also point to a failed download, a damaged update cache, insufficient storage, or an underlying system-file problem. The safest response is to assess the situation first, then use increasingly targeted repair steps.
First, decide whether the update is truly stuck
A slow update is not necessarily a frozen update. Feature updates and cumulative updates can pause visually while Windows performs disk-intensive work. Older computers, devices with slower hard drives, and systems with limited free space can take substantially longer than expected.
Signs that Windows may still be working
- The drive activity light is blinking regularly.
- Fans, disk activity, or network activity continue intermittently.
- The percentage changes occasionally, even if only after a long delay.
- The device is installing a large feature update or has restarted into an update screen.
As a practical rule, leave a plugged-in computer connected to a reliable network for at least two to three hours before treating a stationary percentage as a fault. For a major version upgrade on a slower machine, allowing it to run overnight may be reasonable. Do not force a shutdown simply because progress is slow.
The percentage displayed during an update is an estimate, not a live measure of every task Windows must complete. A long pause can be normal, but repeated failure at the same point usually deserves troubleshooting.
Check the simple causes before repairing anything
If Windows is still usable and the update is stuck in Settings, start with basic conditions. These checks solve many download and installation stalls without changing system components.
- Connect a laptop to AC power and disable Battery Saver temporarily.
- Use a stable, unmetered internet connection. If possible, avoid a mobile hotspot.
- Restart the router only if other devices also have internet problems.
- Free storage space on the system drive. Aim for at least 20 GB free before a major update.
- Disconnect nonessential USB devices, docks, external drives, printers, and game controllers.
- Pause or temporarily remove third-party antivirus software only if its vendor documentation supports doing so. Re-enable protection afterward.
Open Settings > Windows Update and select Check for updates after addressing these items. If the same update repeatedly stops, note its KB number and any error code. That information is useful if you need to install the update manually or seek support.
Use the Windows Update troubleshooter
Windows includes a troubleshooter that checks common update settings and attempts to repair selected components. It is a low-risk first repair because it does not remove personal files.
- Open Settings.
- In Windows 11, go to System > Troubleshoot > Other troubleshooters. In Windows 10, go to Update & Security > Troubleshoot > Additional troubleshooters.
- Find Windows Update and select Run.
- Apply any suggested fixes, then restart the PC.
- Return to Windows Update and try again.
If the troubleshooter reports that it fixed an issue, a restart is important. Some service and cache changes do not fully take effect until Windows starts again.
Choose the right response for the update stage
The best action depends on where the update has stalled. A download inside Settings is generally safer to interrupt than a screen that appears before the sign-in screen and says that updates are being configured.
| Where it is stuck | Typical meaning | Recommended first action |
|---|---|---|
| Downloading at a percentage in Settings | Network, delivery optimization, or cache issue | Check the connection, run the troubleshooter, then reset the update cache if needed. |
| Installing at a percentage in Settings | Package, driver, storage, or system-file issue | Restart once if Windows allows it, disconnect peripherals, and run DISM and SFC. |
| Working on updates after restart | Offline configuration is in progress | Wait several hours with power connected; avoid a forced shutdown unless there is no activity for an extended period. |
| Repeated rollback or “Undoing changes” | Windows could not complete installation | Record the error, remove recent peripherals or drivers, and retry after component repair. |
Reset the Windows Update download cache
If the issue is a download that will not advance or an update that fails repeatedly, clearing the update cache can help. This does not uninstall Windows or erase documents; it removes locally stored update downloads so Windows can obtain fresh copies.
Open Terminal (Admin) or Command Prompt (Admin). Run the following commands one line at a time:
net stop wuauserv
net stop bits
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
net start bits
net start wuauserv
Restart the computer and check for updates again. If a command says that a service could not be stopped, restart Windows and try once more. Do not delete random folders under the Windows directory; use the specific SoftwareDistribution rename method so Windows can recreate the cache normally.
Repair the Windows image and system files
Corrupted component-store data or protected system files can prevent an update from completing. Microsoft provides two built-in command-line tools for this: Deployment Image Servicing and Management (DISM) and System File Checker (SFC). Run them in this order from an administrator Terminal or Command Prompt.
- Enter
DISM /Online /Cleanup-Image /RestoreHealthand wait for it to finish. - Restart if DISM requests it.
- Enter
sfc /scannow. - Restart Windows, then retry Windows Update.
DISM may take time and may appear to pause at certain percentages. Keep the computer online because DISM can use Windows Update as a repair source. If it fails, record the exact message rather than guessing at a fix.
Install one known update manually
When one cumulative update consistently fails, downloading that specific package from the Microsoft Update Catalog can bypass a damaged automatic download. In Windows Update history, identify the KB number, then search for that KB number in the catalog. Choose the package that matches your system architecture, usually x64 or ARM64, download it, and run the installer.
Manual installation is most useful for a single cumulative or security update. It is not usually the best first choice for a major Windows version upgrade. For version upgrades, use Microsoft’s official installation tools and make sure backups are current first.
When to use recovery options
If Windows repeatedly rolls back after every attempt, consider recent changes. Uninstall a newly added driver or device utility, remove unnecessary external hardware, and ensure there is adequate free storage. You can also start Windows in Safe Mode to remove problematic third-party software, then retry from a normal startup.
If the PC cannot boot after an interrupted update, Windows may enter Automatic Repair. From the recovery environment, use Troubleshoot > Advanced options > Uninstall Updates to remove the latest quality update first. Choose a feature update only when a quality-update removal does not resolve the boot problem. Back up important files before attempting more disruptive repairs such as Reset this PC or an in-place repair installation.
Prevent the next stalled update
Regular maintenance lowers the chance of update failures. Keep enough free space on the system drive, restart periodically instead of leaving Windows running for weeks, and obtain firmware and driver updates from the PC manufacturer when needed. Avoid registry cleaners and unofficial “update fix” tools; they can alter services or system settings in ways that create harder problems.
For managed work devices, update policies, VPN requirements, and endpoint security software can affect installation. Contact your organization’s IT team before resetting services or removing security controls. They may have a required update source or a known issue affecting your device model.











