Few things are more frustrating than watching Windows Update sit at 100 percent for an hour, then another hour, with no sign that your computer is actually finishing anything. The message says not to turn off your PC, the fan is spinning, and you have work to do. Is it really working, or has it frozen completely?
In most cases, an update stuck at 100 percent is not a disaster. Windows may be cleaning up in the background, verifying files, or waiting for a service that has stalled. Sometimes, though, a corrupt download, a conflict with antivirus software, or a full system drive genuinely stops the process. This guide walks you through how to tell the difference and how to fix it safely, starting with the least disruptive steps first.
How to Tell If Windows Update Is Really Stuck
Before you press the power button, spend a few minutes checking for signs of life. A healthy update that looks stuck is very different from a frozen system, and the fix you need depends on which one you have.
Check Disk and CPU Activity
Look at the drive activity light on your desktop case or laptop, if your machine has one. Regular flickering suggests Windows is still writing files. Press Ctrl + Alt + Delete. If the security screen appears quickly, the system is responsive. If nothing happens after a minute, the system is far more likely to be genuinely frozen.
Leave the computer plugged in and untouched for at least two to three hours if a large feature update is installing. Major upgrades can sit at 100 percent for a long time on slower drives while Windows migrates settings and user files.
When Waiting Is No Longer Enough
If the screen has not changed for more than three hours, there is no disk activity at all, and keyboard input does nothing, waiting is unlikely to help. That is the point where a controlled restart and the repair steps below become the right move. Do not panic about data loss. Modern Windows Update is designed to roll back incomplete changes, and your personal files are stored separately from the update process.
Step 1: Disconnect External Devices and Wait Briefly
External hardware is a quiet but common cause of update stalls. USB drives, SD cards, printers, and docking stations can confuse the final configuration stage, especially when Windows tries to update their drivers at the same time.
Unplug everything except your keyboard, mouse, power cable, and network cable if you use wired internet. Leave the machine alone for another 20 to 30 minutes after disconnecting. Many users find the update completes shortly after a conflicting device is removed. Note what you unplugged, because you will want to reconnect items one at a time afterwards and check for driver updates for anything that caused trouble.
Step 2: Restart Your PC Safely If It Is Frozen
If the system is completely unresponsive, hold the power button for five to ten seconds until the machine switches off. Wait 30 seconds, then turn it back on. On a laptop, keep the charger connected during this restart.
When Windows restarts, one of three things usually happens. It may finish the update normally. It may show a message that changes are being undone and roll back to your previous working state. Or it may boot to the desktop with the update marked as failed in the history. All three outcomes are workable. What you want to avoid is repeated forced shutdowns during active disk writing, so only use this step when you are confident the system has truly frozen.
Step 3: Run the Windows Update Troubleshooter
Windows includes a built-in troubleshooter that checks update services, clears simple faults, and repairs common permission problems automatically.
On Windows 11
Go to Settings > System > Troubleshoot > Other troubleshooters. Find Windows Update in the list and select Run. Follow the prompts, apply any fix it suggests, then restart your PC even if the tool does not ask you to.
On Windows 10
Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters, then choose Windows Update and run it. Microsoft maintains detailed guidance on this process in its official Windows Update troubleshooter support page, which is worth reading if the tool reports a specific error code.
After the troubleshooter finishes, open Settings > Windows Update and select Check for updates. Let the update download and install again from the beginning. In many cases, the second attempt succeeds because the underlying service fault has already been cleared.
Step 4: Restart the Windows Update Services
If the troubleshooter finds nothing, the update services themselves may be stuck in a bad state. Restarting them manually often clears the blockage.
Press Windows key + R, type services.msc, and press Enter. In the Services window, locate Windows Update, right-click it, and choose Restart. Do the same for Background Intelligent Transfer Service and Cryptographic Services. If a service is stopped, choose Start instead, and check that its Startup type is not set to Disabled.
Close the window, restart your computer, and try the update again. A hung service cannot hand off downloaded files to the installer, even when everything else is healthy.
Step 5: Clear the SoftwareDistribution Download Cache
When an update file downloads incompletely or becomes corrupted, Windows can loop forever trying to use it. Clearing the download cache forces a clean download.
First, stop the services from the previous step so the files are not locked. Then open File Explorer and go to C:\Windows\SoftwareDistribution\Download. Select everything inside that folder and delete it. You are not deleting installed updates, only downloaded installation files, so this is safe. Empty the Recycle Bin if you need the space back immediately.
Restart the Windows Update and Background Intelligent Transfer Service services, reboot the PC, and return to Settings > Windows Update to download the update again. Because the cache was cleared, the download will take longer this time, but it will be a fresh copy. For more background on how these components fit together, our practical Windows troubleshooting guides for everyday PC problems cover the update system in plain language.
Step 6: Free Up Space and Run System File Checks
Windows needs working room to unpack and install updates. If your system drive has less than about 10 GB free, a large update can stall right at the end. Open Settings > System > Storage to see what is using space, and use Storage Sense or Disk Cleanup to remove temporary files.
Repair Corrupted System Files
Open the Start menu, type cmd, right-click Command Prompt, and choose Run as administrator. Run this command first and wait for it to finish:
DISM /Online /Cleanup-Image /RestoreHealth
Then run:
sfc /scannow
DISM repairs the Windows component store that updates depend on, while System File Checker replaces corrupted system files. Microsoft documents both tools in its guide to repairing missing or corrupted system files. Restart after both scans and try updating again.
Step 7: Try Installing the Update Manually
If one specific update keeps failing, note its KB number from Settings > Windows Update > Update history. Search for that KB number in the Microsoft Update Catalog, download the version that matches your Windows edition and processor type, and run the installer yourself. Manual installation bypasses some of the automatic delivery machinery and frequently succeeds where the normal process loops.
If a feature update is the problem, the Windows Installation Assistant offers another supported route. Back up important files first.
Common Mistakes to Avoid
The biggest mistake is repeatedly forcing power off during the first hour. That turns a slow update into a corrupted one. A second mistake is disabling the Windows Update service permanently to stop the prompts. That leaves your PC without security patches and usually causes a bigger failure later.
Avoid downloading update fixer tools from random websites. Many bundle unwanted software, and none can do anything the built-in troubleshooter, DISM, and cache reset cannot. Also avoid deleting folders outside SoftwareDistribution. Fix one problem at a time so you know what worked.
Conclusion
An update stuck at 100 percent usually means Windows is either finishing quietly, waiting on a stalled service, or struggling with a damaged download. Give it genuine time first, remove external devices, and only force a restart when the system is clearly frozen. Then work through the troubleshooter, service restarts, cache clearing, disk space checks, and system file repairs in order. Most PCs are fixed long before the manual installation step. Once the update completes, restart once more, reconnect your devices one by one, and check Update history to confirm everything is current and protected.
Frequently Asked Questions
How long should I wait if Windows Update is stuck at 100 percent?
Wait at least two to three hours for a large feature update, especially on an older hard drive. If there is no disk activity, no response to keyboard input, and no change after three hours, treat it as frozen and restart safely.
Will turning off my PC during an update damage it?
A single forced shutdown rarely causes lasting damage because Windows is designed to roll back incomplete updates. Repeated forced shutdowns during active installation raise the risk of corruption, which is why you should only do it when the system is truly unresponsive.
Why does the update reach 100 percent and then start again?
This often means a downloaded file failed verification, so Windows discards it and retries. Clearing the SoftwareDistribution download folder and letting Windows fetch a fresh copy usually breaks the loop.
Can low storage really stop an update at 100 percent?
Yes. Windows may download an update successfully but have nowhere to unpack and configure it. Keeping at least 10 to 20 GB free on the system drive gives large updates the working space they need.
Should I disable Windows Update to stop this happening again?
No. Disabling updates removes important security fixes and tends to create a larger, more difficult update later. Fix the root cause instead, and future updates will normally install without drama.
Leave a Reply