Windows Update has been sitting at the same percentage for hours, or it keeps failing and rolling back with an error code you don't recognize. This is one of the most common Windows frustrations, and it is different from a computer that won't boot after an update finishes — here, the update itself never completes. In almost every case it is fixable in under an hour without losing any files.
This guide covers all 12 proven fixes in order from least invasive to most thorough. Most people resolve a stuck or failing update by fix 4 or 5. If your update actually finished installing and now Windows won't start, that is a different problem — see our companion guide Windows Won't Boot After Update instead. This article focuses only on updates that are stuck at a percentage, hang on "Checking for updates," or fail and roll back before Windows ever restarts into the new build.
Emergency Quick-Start: What Are You Seeing Right Now?
- Frozen at a specific percentage for over 2 hours, no disk activity: Start at Fix 1 (confirm it's really stuck) then Fix 2 (safe restart)
- An error code appeared (0x800f0922, 0x80070002, etc.): Jump to the Error Code Reference table below, or Fix 5 (reset update components)
- "Checking for updates" spinning forever with no progress: Fix 3 (Windows Update Troubleshooter)
- Downloads fine but fails during install, every time: Fix 4 (free disk space) then Fix 5 (reset components)
- Tried everything, still stuck or failing: Fix 11 (manual install from Microsoft Update Catalog) or Fix 12 (in-place repair install)
Quick Checks Before You Troubleshoot
Why Windows Update Gets Stuck or Fails
Knowing the cause helps you pick the right fix faster. When Windows Update won't finish or keeps failing, one of the following is usually happening:
- Not enough free disk space: Update files need to be staged alongside your existing system files before Windows switches over — without enough room, the process stalls or fails outright
- Corrupted update cache: Partially downloaded or damaged files in the SoftwareDistribution folder cause the same update to fail repeatedly
- A stopped or conflicted Windows Update service: The background services that manage downloading and installing updates (wuauserv, bits, cryptsvc) can hang or crash
- Third-party antivirus or VPN interference: Security software sometimes blocks the update process from replacing system or driver files
- A slow or interrupted internet connection: Large feature updates can fail to download completely over unstable Wi-Fi
- Corrupted system files or component store: Pre-existing Windows file corruption, unrelated to the current update, can prevent any update from completing
- A conflicting driver or peripheral: External hardware or an outdated driver package can cause a specific update to fail on that PC while working fine elsewhere
Can't fix it yourself? Skip the trial-and-error.
Our certified bilingual tech remotes in, reads your update logs, and resolves it on the spot — same day, from $119.99. No fix, no fee.
Fix 1: Confirm It's Actually Stuck, Not Just Slow
Rule Out a Legitimately Long Update First
A monthly cumulative update usually finishes in 20 to 45 minutes. A major feature update (a full version upgrade, like moving to a new annual release) can legitimately take 1 to 3 hours, especially on a mechanical hard drive, an older CPU, or a slower internet connection. During this time the percentage can appear frozen even while Windows is actively working in the background.
What to check: Look for a hard drive activity light (if visible) or listen for fan/drive noise. On a laptop, check whether the fan is spinning up periodically — a sign of active CPU work. If there has been zero percentage movement and zero drive activity for a full 2 hours, treat it as genuinely stuck and move to Fix 2. If there is still activity, keep waiting.
Fix 2: Force Restart Safely
Windows Is Designed to Roll Back a Failed Update
Once you've confirmed the update is truly frozen with no disk activity, a force restart is safe. Windows Update includes a built-in rollback mechanism: if an installation is interrupted, the next boot detects the incomplete state and automatically reverts to the last working configuration rather than leaving Windows broken.
Steps: Hold the power button for 10 seconds until the PC turns off completely. Wait 10 seconds, then power it back on. Windows may take a few extra minutes on this boot to finish rolling back — let it run. Once you're back at the desktop, note the error message if one appeared (Settings › Windows Update › Update history) and continue to Fix 3.
Fix 3: Run the Windows Update Troubleshooter
Let Windows Diagnose the Problem Automatically
Microsoft's built-in troubleshooter checks for the most common causes of stuck and failing updates — corrupted cache files, misconfigured services, and pending reboots — and fixes many of them without any manual commands.
Steps: Go to Settings › System › Troubleshoot › Other troubleshooters. Find Windows Update and click Run. Wait for the scan to complete (2–5 minutes). If it finds and fixes an issue, restart and retry the update. If it reports no problems found, proceed to Fix 4.
Fix 4: Free Up Disk Space
Updates Need Room to Stage Before They Install
Microsoft recommends at least 20 GB free for a cumulative monthly update and up to 64 GB temporarily free for a major feature update, since new system files are staged alongside the old ones before the switch happens. A drive with less than 15 GB free is one of the single most common causes of an update that stalls partway through or fails with a disk-space error.
Steps: Go to Settings › System › Storage. Turn on Storage Sense or click Temporary files to clear the Downloads folder, Recycle Bin, and Windows Update cleanup files. For a bigger cleanup, run Disk Cleanup (search from the Start menu), check "Clean up system files," and select previous Windows installations and temporary files. Retry the update once you have at least 20 GB free.
Fix 5: Reset the Windows Update Components
Clear a Corrupted Update Cache Without Losing Files
This is often the single most effective fix for an update that fails and re-downloads the exact same way every time. The SoftwareDistribution and catroot2 folders store Windows Update's temporary files and configuration — when they become corrupted, every retry fails identically. Resetting them forces Windows to rebuild both from scratch.
Steps: Open Command Prompt as administrator and run these commands one at a time:
net stop wuauserv
net stop bits
net stop cryptsvc
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start bits
net start cryptsvc
net start msiserver
Restart the computer and retry Windows Update. This does not delete any personal files — only Windows Update's own temporary cache.
Fix 6: Run SFC and DISM RestoreHealth
Repair Corrupted System Files Blocking the Update
If system files or the Windows component store are damaged, no update will complete successfully until they are repaired — this is unrelated to the specific update being attempted. Running SFC and DISM together resolves the majority of this class of failures.
Steps: Open Command Prompt as administrator and run:
sfc /scannow
Let it finish (5–15 minutes), then run:
DISM /Online /Cleanup-Image /RestoreHealth
This step contacts Windows Update servers to download replacement files and can take 10–20 minutes. When both commands complete, restart and retry the update. If SFC reported it "could not fix some of them," running DISM first and SFC again afterward resolves it in most cases.
Still Stuck After the First Six Fixes?
If Fixes 1 through 6 haven't resolved it, IT Cares technicians provide remote support across Canada. We fix Windows Update failures the same day, including corrupted update caches, driver conflicts, and stubborn error codes.
Fix 7: Temporarily Disable Third-Party Antivirus
Security Software Can Block Update Components
Third-party antivirus, VPN clients, and some firewall software can intercept the update process — particularly when it tries to replace system-level or driver files — causing the installation to hang or fail without a clear error message. This does not apply to Windows Defender, which is designed to work alongside Windows Update.
Steps: Open your antivirus program and temporarily disable real-time protection (usually a right-click on the system tray icon, or a toggle inside the app). Retry the update. Once it completes successfully, re-enable your antivirus immediately — never leave your PC unprotected longer than necessary. If this resolves the issue, check for an update to your antivirus software, since most vendors patch these conflicts quickly.
Fix 8: Disconnect Non-Essential Peripherals
External Hardware Can Interfere With Driver Updates
External hard drives, docking stations, USB hubs, printers, and secondary monitors can all interfere with an update that includes driver components, sometimes causing the installer to hang while waiting on a device that never responds correctly.
Steps: Unplug everything except your keyboard, mouse, and (on a laptop) the power adapter. If using a docking station, connect directly to a wall outlet and a single monitor instead. Retry the update. Reconnect peripherals one at a time afterward if you want to identify which device was the culprit.
Fix 9: Clean Up the Component Store with DISM
Remove Superseded Files Taking Up Room
Windows keeps copies of superseded system files to allow uninstalling recent updates. Over time, especially on drives that are low on space, this component store bloat can itself prevent new updates from staging correctly.
Steps: Open Command Prompt as administrator and run:
DISM /Online /Cleanup-Image /StartComponentCleanup
This can take 10–30 minutes depending on how long it's been since the last cleanup. For a more aggressive cleanup that also removes the ability to uninstall the current update (use only once you're confident the current version is stable), add /ResetBase to the same command. Restart and retry the update afterward.
Fix 10: Uninstall a Recently Failed Driver Update
Remove the Specific Update Causing the Loop
If failures started right after a specific optional or driver update was offered — commonly a graphics, chipset, or network driver — removing that specific update from history often breaks the failure loop for good, letting other pending updates install normally.
Steps: Go to Settings › Windows Update › Update history › Uninstall updates. Look for the entry with a date matching when the failures began. Select it and click Uninstall. Restart, then check Settings › Windows Update › Advanced options › Pause updates for a week if you want time to update the driver manually from the manufacturer's website first.
Fix 11: Download and Install the Update Manually
Bypass the Windows Update Client Entirely
The Windows Update client itself can be the point of failure even after the underlying cause is fixed. Downloading the update package directly and installing it manually sidesteps the client altogether.
Steps: In Settings › Windows Update › Update history, find the KB number of the update that keeps failing (formatted like KB5012345). Go to the Microsoft Update Catalog website, search for that KB number, and download the .msu file matching your Windows version and architecture (x64 in almost all cases). Double-click the downloaded file to install it directly. This method works even when the standard update client is completely stuck.
Fix 12: Run an In-Place Upgrade Repair Install
Rebuild Windows While Keeping Your Files and Apps
If nothing else has worked, an in-place upgrade repair install replaces all Windows system files with fresh copies while keeping your personal files, installed programs, and settings intact. This resolves nearly every stubborn update failure that survives the fixes above, without the data loss of a clean install.
Steps: Download the official Windows 11 (or 10) ISO from Microsoft's website onto the affected computer, or use the Media Creation Tool. Double-click the ISO to mount it, then run setup.exe from inside it. When prompted, choose Keep personal files and apps. The process takes 30 to 90 minutes and effectively reinstalls Windows in place, which almost always clears whatever was blocking the update.
Common Windows Update Error Codes and Fixes
If Windows Update shows an error code when it fails, use this table to identify the likely cause and the best fix to try first:
| Error Code | Meaning | Best Fix |
|---|---|---|
0x800f0922 |
Update could not be staged or committed — often low disk space or a full EFI System Partition | Fix 4, then Fix 5. See our dedicated 0x800f0922 guide for the ESP-specific steps |
0x80070002 / 0x80070003 |
Required update files not found — usually a corrupted download cache | Fix 5 (reset update components) |
0x8024402c / 0x80072ee2 |
Connection to Windows Update servers timed out | Check internet stability, then Fix 3 (troubleshooter) |
0x800f0900 |
Generic servicing failure during install | Fix 6 (SFC + DISM RestoreHealth) |
0x8007000d |
Corrupted or unreadable update file | Fix 5, then Fix 11 (manual install) |
0x80073712 |
A component-store file needed by the update is missing or damaged | Fix 6 (SFC + DISM), then Fix 9 (component cleanup) |
| Stuck at 0% for over an hour | Update download never started or the queue is jammed | Fix 3 (troubleshooter), then Fix 5 |
| Stuck at 100%, "Working on updates" | Update is finalizing — legitimate if disk activity continues | Fix 1 (wait), then Fix 2 (safe restart) if truly frozen |
| Fails and re-downloads the same way every time | Corrupted local update cache | Fix 5 (reset update components) resolves this in most cases |
Real Canadian Case Studies
Case 1 — Stuck at 47% for six hours (Toronto, ON)
A home-office consultant's laptop had been "installing" a monthly cumulative update overnight and was still frozen at 47% the next morning, with the fan silent and no drive activity. A safe force restart triggered Windows' automatic rollback, but the same update failed identically on the next three attempts. The cause turned out to be a corrupted SoftwareDistribution folder from an earlier interrupted update months prior. Resetting the Windows Update components cleared the stale cache, and the update installed cleanly in 22 minutes on the next try.
Case 2 — Repeated 0x800f0922 failures (Halifax, NS)
A retiree's desktop kept failing the same feature update with 0x800f0922 four nights in a row, each time rolling back automatically after about 40 minutes. The system drive had only 9 GB free — well under the 20 GB minimum for a cumulative update, let alone the space a feature update needs. After running Disk Cleanup with "system files" included and removing an old Windows.old folder taking up 26 GB, the update completed successfully on the first retry.
Case 3 — Overnight update loop, third-party antivirus conflict (Calgary, AB)
A small law office's front-desk PC was stuck at "Working on updates 30%" every night for a week, always requiring a forced restart in the morning before the office could open. IT Cares connected remotely and found a third-party antivirus suite blocking a driver component the update needed to replace. Temporarily disabling real-time protection allowed the update to complete in 18 minutes; updating the antivirus software to its latest version resolved the underlying conflict permanently.
How Much Does Fixing a Stuck Windows Update Cost?
All 12 fixes in this guide are completely free — Microsoft does not charge for update troubleshooting tools. What costs something is the time lost to a business or a household without a working computer, and if you get stuck beyond your comfort level, professional help finishing the job. Here is a realistic budget picture:
| Path | Cost | Best for |
|---|---|---|
| Self-troubleshooting (Fixes 1–4) | Free | Straightforward cases: disk space, a safe restart, the built-in troubleshooter |
| Self-troubleshooting via Command Prompt (Fixes 5–9) | Free, but time-consuming | Comfortable typing commands and following multi-step instructions carefully |
| IT Cares remote diagnosis and fix | From $119.99, no fix – no fee | Stuck, out of time, or not comfortable with Command Prompt |
| IT Cares business fleet update triage | Quoted after a quick review for multiple affected PCs | An office with several machines stuck on the same failing update |
| In-place upgrade repair or clean install | Free (DIY) or included in a remote/on-site visit | Last resort after every targeted fix has failed |
The real cost of a stuck Windows Update is rarely the fix itself — it is the hours of downtime for a business, or the anxiety of not knowing whether the computer is safe to touch. Getting it diagnosed correctly the first time is almost always faster than working through all 12 fixes alone.
When to Call IT Cares
- The update has been stuck or failing for more than a day despite trying the free fixes above
- It's a business computer you cannot afford to leave offline while you troubleshoot
- You are not comfortable running Command Prompt commands like DISM, SFC, or the service reset
- The same update keeps failing identically after a component reset and a component cleanup
- You want a full health check after the fix to prevent the same issue from recurring on the next update cycle
IT Cares technicians connect remotely, diagnose the exact cause from your update logs, and get Windows Update working again the same day, anywhere in Canada.
How to Prevent Windows Update Problems in the Future
Once your update finally completes, take these steps so it doesn't happen again next time:
- Keep 30+ GB free at all times — set a calendar reminder to run Disk Cleanup monthly, or turn on Storage Sense to do it automatically
- Set Active Hours in Windows Update settings so large updates don't start mid-workday and get interrupted
- Restart weekly instead of only sleeping/hibernating — a full restart lets pending updates apply cleanly instead of stacking up
- Keep antivirus software up to date, since vendors regularly patch conflicts with new Windows Update behavior
- Don't interrupt an update in its first 30–60 minutes — most failures technicians see start from an update that was force-closed too early
- Maintain regular backups so that even in the rare case a repair install is needed, nothing important is ever at risk
Success Rate by Fix
Based on IT Cares technician experience with stuck and failing Windows Update cases: Fixes 4 and 5 (disk space and component reset) together resolve approximately 55% of cases. Fix 3 (troubleshooter) catches another 15% on its own. Fixes 6 through 10 account for roughly 20% more. Fixes 11 and 12 are needed in only about 10% of cases — and even then, personal files are preserved in nearly every situation.
Frequently Asked Questions
Nine questions answered directly for people troubleshooting a stuck or failing Windows Update.
Comments (3)
Fix 5 (resetting the update components) fixed an update that had failed identically five nights in a row. I was terrified I'd lose files renaming those folders but nothing was touched — just the update cache. Worked perfectly on the next try.
The error code table sent me straight to Fix 4 for a 0x800f0922 error. Had no idea my drive was down to 8 GB free. Cleared 40 GB with Disk Cleanup and the update went through on the first try after that.
Update was frozen at 63% for over 4 hours on my work laptop with the fan completely silent. Waited the full 2 hours like the guide said before force-restarting, and Windows rolled itself back cleanly. The troubleshooter caught the actual issue after that — a stopped BITS service.
Leave a Comment