Windows 11 update stuck — progress bar frozen, “Working on updates” screen that doesn’t move, or a percentage that hasn’t changed in 45 minutes — usually resolves itself if you wait long enough. That’s the honest answer. Updates that look stuck often aren’t. You’ll find the complete rundown in our Complete Guide to Fixing Windows, Browser, and Software Errors.
Before doing anything: how long has it actually been frozen? Under 45 minutes at any percentage isn’t stuck — it’s slow. Feature updates (the big annual upgrades) can take 90+ minutes on slower machines. The “Working on updates” screen with no visible progress is particularly misleading; it can stay that way for 20 minutes while actively doing things you can’t see.
If you’re past 45 minutes with no change: open Task Manager → Performance → Disk. Disk activity above 0 means it’s working. Disk at zero for 20 continuous minutes means it’s genuinely stuck.
Safe actions when genuinely stuck
If disk is at zero for 20 minutes: a forced restart is the safest move at that point. Hold the power button 5 seconds. Windows handles interrupted update installations better than most people expect — it either completes on next boot, rolls back cleanly, or shows an error code that guides the next step. The “don’t turn off your PC” warning is real but applies to active installation; a completely frozen process isn’t actively installing anything.
After the forced restart: Windows shows one of three things. The update completes successfully (most common). “Undoing changes” appears — Windows rolled back cleanly. Or Windows boots normally with the update not applied, which you’ll see in Update history as Failed.
Fix 1: Clear the update cache
Corrupted partially-downloaded update files cause stalls at consistent percentages — often 0% downloading or a specific installation stage. The solution is deleting those files and starting fresh.
net stop wuauserv
net stop bits
rd /s /q C:WindowsSoftwareDistributionDownload
net start wuauserv
net start bitsAdministrator Command Prompt. This stops the update services, deletes only the download cache (not any installed updates), and restarts them. Attempt the update again after restarting.
Fix 2: Windows Update troubleshooter
Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run. It automatically handles: stopped services, corrupted download cache, and common registry issues. Takes two minutes. Apply recommendations → try the update again. Not always the complete solution but catches the easy stuff automatically and costs nothing to try first.
Fix 3: SFC and DISM
System file corruption causes update installation to stall when the installer encounters a file it can’t modify. These commands repair corrupted files:
DISM /Online /Cleanup-Image /RestoreHealthFirst (requires internet, 15–20 minutes). Then:
sfc /scannowAdministrator Command Prompt, restart after both complete, then attempt the update. If SFC reports “found corrupt files and repaired them” — that was the cause.
Fix 4: Manual update via Update Catalog
When the automatic process keeps stalling on a specific update: install it manually. Find the KB number in Windows Update history → go to catalog.update.microsoft.com → search it → download the correct x64 version → run the .msu file as administrator. The manual installer bypasses Windows Update Agent entirely and often succeeds where the automatic process stalls repeatedly.
Disk space — frequently overlooked
Feature updates need 15–20 GB free. When the drive is low on space, the update downloads fine but stalls during staging because it can’t create the temporary working space it needs. Check: Settings → System → Storage. Under 20 GB free? Run Disk Cleanup → Clean up system files → remove Windows Update Cleanup and temporary files → retry. This is a faster fix than it sounds if disk space is the actual problem.
Fix 5: Antivirus pausing installation
Real-time antivirus scanning holds file locks on update files as it scans them. The update installer encounters the lock, waits, and eventually times out — appearing as a stall. Temporarily disable the antivirus’s real-time protection (not the whole antivirus, specifically real-time scanning) → immediately run Windows Update. Re-enable after the update completes. If this works: add the SoftwareDistribution folder to the antivirus exclusion list to prevent it from scanning update files during future installations.
Fix 6: Reset Windows Update components completely
More thorough than the cache clear alone:
net stop wuauserv && net stop bits && net stop msiserver && net stop cryptSvc
ren C:WindowsSoftwareDistribution SoftwareDistribution.old
ren C:WindowsSystem32catroot2 catroot2.old
net start wuauserv && net start bits && net start msiserver && net start cryptSvcThis renames the entire update database rather than just the download folder, forcing a completely fresh start for the update mechanism. Restart after running these commands.
Feature update specifically — the Media Creation Tool
When a major version upgrade keeps stalling through normal Windows Update: use the Media Creation Tool instead. Download from Microsoft’s Windows 11 page → “Upgrade this PC now” → it downloads and installs the feature update through a completely different code path than Windows Update. Keeps all files and applications. This bypasses a broken Windows Update infrastructure rather than trying to repair it.
Specific error codes
Windows Update history shows error codes for failed updates. These codes are specific and searchable. Common ones: 0x80070070 = disk space. 0x80240034 = Windows Update client issue. 0x800f0988 = component store corruption (fix with DISM). 0xc1900101 = driver incompatibility during feature update (update drivers first). Each code narrows the fix significantly compared to generic troubleshooting.
Our guide on Windows 11 not updating covers persistent update failures that go beyond a single stuck update — when updates consistently fail rather than just stalling once. For the post-update issues that occasionally appear once an update finally completes, the no internet after update guide covers the network stack changes updates sometimes cause. Microsoft’s Windows Update troubleshooting covers the full UsoClient.exe scan and the Windows Update log format for diagnosing specific installation failure reasons that the error codes don’t fully explain.
VPN interference with update downloads
A connected VPN routes Windows Update traffic through the VPN server. Corporate VPNs sometimes block Windows Update domains (to force updates through WSUS), and personal VPNs can cause download stalls when their server is slow or in a distant geographic region. Disconnect the VPN and attempt Windows Update again. If the update proceeds normally, reconnect the VPN after completion. For corporate machines where VPN can’t be disconnected: IT should handle updates through WSUS or WSUS proxy.
Pause and resume as a simple reset
If an update is stalled at a specific percentage: Settings → Windows Update → Pause updates → pause for 1 week → immediately click Resume updates. This forces the Windows Update service to restart its current state without clearing downloaded files. Occasionally a paused state within the download process causes stalls, and the pause/resume cycle kicks it out of the stuck state without requiring a full cache clear.
Driver conflicts causing feature update failures
Feature updates (major version upgrades) have a compatibility check that flags incompatible drivers. When a driver is incompatible with the target Windows version, the update downloads but stalls during the installation phase, eventually rolling back with error 0xc1900101 or similar. Device Manager → look for any devices with yellow warning triangles → update their drivers from manufacturer websites. Then retry the feature update.
The Windows 11 compatibility tool (available from Microsoft’s Windows 11 page → “Check if your PC is compatible”) specifically identifies driver incompatibilities before attempting the upgrade — running this before a feature update saves the time of repeated failed installation attempts.
BIOS and Secure Boot affecting updates
Feature updates to newer Windows 11 versions increasingly enforce Secure Boot requirements. If Secure Boot was recently disabled for hardware testing or software installation and wasn’t re-enabled: the feature update may stall or fail when it detects the non-compliant state. BIOS/UEFI → Secure Boot → re-enable → save → retry Windows Update.
The update keeps failing on the same specific KB
A pattern worth recognising: if the same KB update fails repeatedly while other updates install fine, it’s that update’s installation package that’s the issue rather than a general Windows Update problem. Options: install manually from the Update Catalog, wait for a revised version of that specific update, or search for that KB number specifically on Microsoft’s Known Issues page — Microsoft sometimes acknowledges specific update failures and provides targeted workarounds.
Event Viewer for update failure details
When Windows Update history shows “Failed” without a useful error code: Event Viewer → Windows Logs → Setup → look for error entries around when the update attempted to install. The Setup log captures the exact sequence of installation events and the specific failure point — which component failed, which file couldn’t be written, which service timed out. This level of detail often reveals the fix directly (a specific service that needs to be started, a specific file that’s corrupted and needs SFC) rather than requiring trial-and-error with multiple approaches.
Running Windows Update in a clean boot state
When third-party software is interfering with the update process (antivirus, system management tools, VPN clients), a clean boot isolates the issue. Win + R → msconfig → Services tab → Hide all Microsoft services → Disable all → Startup tab → Disable all → OK → restart. After restarting in clean boot state, run Windows Update. If the update installs successfully, re-enable services and startup items in groups to identify which specific software was interfering.
Large pending updates accumulating
Machines that have been off or offline for extended periods may have 10–20 cumulative updates pending. Installing this many updates at once occasionally causes the update stack to time out or stall — there are simply too many sequential operations for the installer to complete in a single session without hitting a service timeout.
Install updates in batches: install the first available batch → restart → install the next batch → restart. Repeat until fully updated. This is slower but more reliable than attempting all pending updates at once. The machine may need 4–5 restart cycles to fully catch up after a long offline period, which is normal.
Windows Update standalone installer
For machines where the Windows Update service is fundamentally broken: the Windows Update standalone installer (wusa.exe) can install individual update packages from the Update Catalog without using the Windows Update service at all. Download the .msu file from catalog.update.microsoft.com → run it directly as administrator → wusa.exe handles the installation directly. This is the most direct possible bypass of a broken Windows Update infrastructure.
Handling “Undoing changes” loops
An update that installs, fails, shows “Undoing changes made to your computer,” then restarts and tries again — in a loop — needs more aggressive intervention. On the next boot before the update re-attempts: boot into Windows Recovery Environment (interrupt startup three times to trigger WinRE) → Troubleshoot → Advanced options → Uninstall updates → remove the most recent update that’s causing the loop. After removing it, Windows boots normally and you can address the root cause before allowing the update to attempt again.
One thing that saves a lot of unnecessary troubleshooting: confirming the update hasn’t actually finished before concluding it’s stuck. Windows Update history (Settings → Windows Update → Update history) shows the completion status of every update attempt. An update listed as “Installed” despite the progress bar appearing frozen means the installation completed successfully and the screen just hasn’t refreshed — restarting the machine will reveal the completed state. Check the history before running any repair commands.
The practical order: wait 45 minutes before acting → check disk activity to confirm it’s actually frozen → forced restart → if it fails, check Update history for error codes → cache clear → troubleshooter → SFC/DISM → manual KB install from Catalog → Media Creation Tool for feature updates. Most situations resolve somewhere in the first three steps; the rest are for cases where the update is genuinely broken rather than just slow.
For machines that consistently have Windows Update problems — not just one stuck update but a persistent pattern of failures — the Windows Update service infrastructure itself may need deeper repair. The PowerShell command Get-WindowsUpdateLog (run from an administrator PowerShell, outputs a readable log to the Desktop) creates a comprehensive log of all Windows Update activity including the detailed failure reasons that the Settings UI doesn’t surface. Microsoft support uses this log for cases where standard troubleshooting hasn’t identified the root cause. It’s worth generating and reviewing even without contacting support — the log often contains the specific error and the exact component that failed, pointing directly at a fix.
A final note on patience versus action: the most common outcome of “my update is stuck” is that the update completes successfully when left alone. The instinct to intervene — force restart, run commands, delete files — creates more risk than the stuck update itself in most cases. The interventions above are appropriate when disk activity has been zero for 20+ minutes, which is the only reliable indicator that the update is genuinely frozen rather than just slow. Treating slow as stuck is how people create the update rollback loops and corrupted update states that are significantly harder to fix than a slow but working installation. You might also run into Windows 11 Update Stuck or Slow? The Step That Skips the Loop.
