Fix Windows 11 Not Updating

Windows Update refusing to install is one of those problems that creates genuine stress precisely because the stakes feel high — every missed update is a security patch not applied, and the longer it drags on the more exposed the machine feels. The most common cause, though, is entirely mundane: a corrupted download cache. Before working through anything else, run this in an administrator Command Prompt and restart:

net stop wuauserv && net stop bits
rd /s /q C:WindowsSoftwareDistributionDownload
net start wuauserv && net start bits

This clears out partially-downloaded update files that Windows keeps trying — and failing — to use. After restarting, go back to Windows Update and try again. It fixes the problem more often than it has any right to, and it takes about 90 seconds. If that doesn’t do it, read on. For a broader walkthrough, our Complete Guide to Fixing Windows, Browser, and Software Errors is a good next read.

Understanding What’s Actually Failing

Windows 11 not updating is a symptom, not a single cause. The error pattern tells you where to look:

Stuck at 0% downloading — The download isn’t starting. Likely causes: corrupted download cache (fix above), BITS service stopped, or the delivery optimization service has a problem. Also possible: the machine is connected to Wi-Fi but the connection is too unstable for sustained downloads.

Downloads but fails during installation — Something is wrong on the system side. Corrupted system files (use SFC/DISM), insufficient disk space, or a conflicting driver or service. Error codes in this case are your friend — right-click the failed update in Windows Update history and search the specific code.

Shows “You’re up to date” when you know updates exist — Usually a WSUS policy issue (especially on corporate machines) or the machine is on a deferred update ring. Check Settings → Windows Update → Advanced options for any “Pause updates” setting that was set and forgotten.

Installs then immediately rolls back — Compatibility failure. The update ran into something that caused Windows to automatically undo it — often a third-party driver or a system file integrity issue. Run DISM and SFC before attempting the update again.

Fix 1: Run the Troubleshooter (It Actually Works)

The Windows Update troubleshooter has a bad reputation because people expect it to fix everything, and it doesn’t. But it reliably fixes a specific set of issues — stopped services, misconfigured registry settings, and cache state problems — and those happen to be some of the most common causes. Worth running first since it’s automatic and takes three minutes:

Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run.

Apply whatever it recommends. If it says it found and fixed something, restart and try the update again. If it comes back saying it couldn’t fix anything, the issue is something it doesn’t handle and you need the manual steps below.

Fix 2: SFC and DISM for System File Corruption

This is the fix to run when updates download fine but fail during installation — particularly if they fail with error codes like 0x800f0988, 0x8007001f, or 0x80070490. These codes typically mean the update installer ran into corrupted Windows components it couldn’t work with.

1. Open Command Prompt as administrator
2. Run DISM first — it repairs the component store that SFC draws from:
   DISM /Online /Cleanup-Image /RestoreHealth
   This takes 10–20 minutes and needs an internet connection. Don’t interrupt it.
3. Then run SFC:
   sfc /scannow
4. Restart after both complete, then try Windows Update

If SFC reports “found corrupt files and repaired them” — that was likely your problem. If DISM fails because it can’t connect to Windows Update servers (circular dependency), you’ll need to provide the source files from a Windows 11 ISO instead.

Fix 3: Check Disk Space

Feature updates need significant room to work — downloading, extracting, staging the new system files, and keeping a rollback copy simultaneously. The requirement is usually 15–20 GB of free space, but Windows doesn’t always give a clear error when it runs out mid-process. It just fails.

Check free space on C: in File Explorer. If it’s under 20 GB, run Disk Cleanup (search in Start) → Clean up system files → tick Windows Update Cleanup, Previous Windows installations, and Temporary Windows installation files. Those three categories alone often recover 10–25 GB on machines that have had a few updates applied. Run this regularly on machines with smaller SSDs — 256 GB drives fill up faster than expected when you factor in update overhead.

Fix 4: Reset Windows Update Components Manually

When the troubleshooter and cache clear don’t fix it, a more thorough reset of the Windows Update infrastructure sometimes does. This re-registers the core update DLLs and resets Winsock, which clears a category of problems the troubleshooter doesn’t touch:

1. Open administrator Command Prompt
2. Stop all update-related services:
   net stop wuauserv && net stop cryptSvc && net stop bits && net stop msiserver
3. Rename the corrupted cache folders (renames rather than deletes, so they can be recovered):
   ren C:WindowsSoftwareDistribution SoftwareDistribution.old
ren C:WindowsSystem32catroot2 catroot2.old
4. Reset Winsock and IP stack:
   netsh winsock reset
netsh int ip reset
5. Restart all services:
   net start wuauserv && net start cryptSvc && net start bits && net start msiserver
6. Restart the PC and try Windows Update

Fix 5: Install the Update Manually via the Update Catalog

This bypasses the entire Windows Update delivery mechanism — all the caching, the update agent, the download manager — and installs the update directly. It’s the right move when everything else has failed and you know which specific update keeps failing.

Find the KB number from Windows Update (the error in Windows Update history shows it, or check the update name). Go to catalog.update.microsoft.com and search for the KB number. Download the correct version for your architecture (x64 for most modern machines) and run the .msu file as administrator. It installs the update directly without going through the update service at all.

This also works as an immediate fix when you need a specific security patch applied urgently but Windows Update is completely broken. Get the patch, install it directly, sort out Windows Update as a separate issue.

Fix 6: Delivery Optimization — When It’s Throttling Downloads

Windows 11 can download updates from Microsoft’s servers, from other PCs on your network, or from other Windows PCs across the internet (peer-to-peer). When Delivery Optimization is misconfigured or struggling to find peers, it can throttle the download to near-zero and the update appears permanently stuck at a low percentage.

Check this: Settings → Windows Update → Advanced options → Delivery Optimization → Advanced delivery optimization options → Download settings. If there’s a fixed bandwidth limit set (absolute or percentage), remove it or increase it substantially. Also check whether “Allow downloads from other PCs” is enabled and causing issues — disabling it and downloading directly from Microsoft sometimes speeds things up significantly on networks where peer-to-peer is unreliable.

Corporate Machines: The Policy Situation

If this machine is domain-joined or managed by an organisation’s IT department, Windows Update may be intentionally controlled. Check: run reg query HKLMSOFTWAREPoliciesMicrosoftWindowsWindowsUpdate in Command Prompt. If entries appear (especially WUServer, WUStatusServer, or UseWUServer = 1), a WSUS or Microsoft Endpoint Configuration Manager server is controlling updates — not Microsoft directly. Updates won’t install until IT approves and deploys them. On a managed device, this isn’t something to work around; contact IT instead.

Our guide on Windows 11 black screen after update covers the boot failures that occasionally follow a successful update — worth reading if you get updates working but then face a different problem. For persistent system file corruption that makes SFC fail repeatedly, the Windows 11 not booting guide covers the recovery environment approach to running these repairs offline. Microsoft’s Windows Update troubleshooting documentation maintains a list of known update issues by KB number, which is worth checking when a specific update keeps failing — the fix is sometimes a single registry key change or a specific pre-requisite that needs installing first.

Fix 7: Check the Windows Update Service Dependencies

Windows Update depends on several services running correctly — not just the Windows Update service (wuauserv) itself, but also Background Intelligent Transfer Service (BITS), Cryptographic Services (cryptSvc), and Windows Installer (msiserver). If any of these are stopped or set to the wrong startup type, updates fail. The troubleshooter catches some of these but not all.

Open services.msc (Windows + R → type services.msc → Enter). Check each of these services:

• Windows Update — Should be: Running, Startup type Manual (Trigger Start)
• Background Intelligent Transfer Service (BITS) — Should be: Running, Startup type Manual (Trigger Start)
• Cryptographic Services — Should be: Running, Startup type Automatic
• Windows Installer — Should be: Running, Startup type Manual

If any of these shows Stopped and won’t start, or is set to Disabled, right-click → Properties → change the Startup type to the value listed above → Apply → then right-click again → Start. After getting all four running, try Windows Update again. A disabled BITS service is a surprisingly common hidden cause — some system optimisation tools and third-party applications disable it without obvious indication.

Fix 8: Check for Conflicting Applications

Security software, particularly endpoint protection products and some VPN clients, can interfere with Windows Update’s download and installation process. The interference usually manifests as updates downloading successfully but failing during installation, or downloading extremely slowly as the security software scans every downloaded file before passing it to the update installer.

Test this by temporarily disabling real-time protection (not full protection — just real-time) in your antivirus before running Windows Update. If the update installs successfully with real-time protection disabled, add the Windows Update cache folder (C:WindowsSoftwareDistribution) to the antivirus exclusion list rather than leaving protection permanently disabled. This prevents the antivirus from scanning files that Windows Update needs to use immediately during installation, while still scanning everything else.

VPN software that routes all traffic through a VPN server can also cause Windows Update failures — if the VPN server’s exit IP is in a region that Microsoft’s update delivery network treats differently, the update CDN may serve a different version or throttle downloads. Disconnecting the VPN before running Windows Update confirms whether this is the cause.

Fix 9: Windows Update Error Code Reference

The specific error code shown in Windows Update history (Settings → Windows Update → Update history → right-click failed update → View details) provides the most direct path to the right fix. Common codes and what they mean:

When researching an error code, searching “Windows 11 update error [code]” plus the current year usually finds community threads with machine-specific causes that Microsoft’s generic documentation doesn’t cover — particularly useful for obscure codes that appear on only certain hardware configurations or after specific software conflicts.

One last thing worth noting: if Windows 11 has been missing updates for weeks or months, it may need to install cumulative updates in sequence — you can’t always jump straight to the latest. Check Windows Update history to see how far behind it is, and if it’s several versions behind, it may need to install a catch-up cumulative update first before the current one will apply. This is more common on machines that are rarely restarted and rarely check for updates.

Fix 10: In-Place Upgrade as a Last Resort

When Windows Update is so broken that nothing above fixes it — SFC can’t complete, DISM can’t restore health, the troubleshooter loops without finding anything, and manual KB installs fail — an in-place upgrade reinstalls Windows 11 over itself without removing your files, applications, or settings. It’s a more aggressive operation than a standard update and takes 30–60 minutes, but it’s not a factory reset and you won’t lose your data.

Download the Windows 11 ISO from Microsoft’s official Windows 11 download page. Mount it by double-clicking in File Explorer. Run setup.exe from the mounted drive. Choose “Keep personal files and apps” when prompted. Let the upgrade complete — it will restart several times. After finishing, Windows Update typically starts working again because the entire update infrastructure has been rebuilt as part of the process.

This approach also resolves persistent Windows Update failures caused by registry corruption, missing or misconfigured Windows components, and damage to the system that SFC can’t fully repair because the repair files themselves are affected. It’s not quick, but it works when nothing else does, and it preserves everything that matters on the machine. Our guide on Windows 11 Taskbar Not Working covers an adjacent issue.