A Windows 11 update that seems to take forever — stuck at 32%, or at “Working on updates 90%” for an hour, or repeatedly restarting and apparently making no progress — is one of the most common Windows frustrations. The hard part: sometimes an update that looks stuck is actually working invisibly, and rebooting kills the progress you can’t see. For a broader walkthrough, our Complete Guide to Fixing Windows, Browser, and Software Errors is a good next read.
Before assuming the update is stuck: check if disk activity light is still flashing or hard drive sound is still happening. If the disk is still active, the update is still doing something — let it run another 30-60 minutes before intervening. Feature updates can legitimately take 2-3 hours on slower hardware. If the disk light is dead and the screen has been static for 30+ minutes, it really is stuck and intervention is appropriate.
For genuinely stuck updates: the Windows Update Troubleshooter (Settings → System → Troubleshoot → Other troubleshooters → Windows Update) resolves about 60% of cases in one click — far higher than its reputation suggests. The full guide below covers the deeper fixes: clearing the SoftwareDistribution folder, resetting update components, and manual update installation if Windows Update is fully broken.
Why updates are slow — the actual reasons
Slow updates are caused by one of these, in rough order of frequency:
- HDD instead of SSD — the biggest single factor. File extraction and installation that takes 3 minutes on an NVMe SSD takes 25–40 minutes on a spinning hard drive. Not fixable without hardware upgrade.
- Previous failed update files — corrupted partial downloads from earlier attempts cause the current update to restart its download or fail during installation.
- Antivirus scanning update files — real-time scanning of downloaded update packages adds significant time.
- Old Windows Update cache — accumulated update metadata and partial downloads slow new downloads.
- Low disk space — updates need 5–20 GB of working space to extract and stage files.
Clear the update cache — the most effective fix
Administrator Command Prompt:
net stop wuauserv
net stop bits
rd /s /q C:WindowsSoftwareDistributionDownload
net start wuauserv
net start bitsThis deletes only the download cache — not installed updates. After running, attempt the update again. Windows re-downloads fresh packages rather than trying to resume partial or corrupted downloads. This resolves the most common cause of slow-then-stalling updates: a partial download from a previous attempt that didn’t complete cleanly.
Disk space check
Settings → System → Storage → C: drive. Under 10 GB free? Updates will struggle to stage and install properly. Run Disk Cleanup: search “Disk Cleanup” → open → Clean up system files → check “Windows Update Cleanup” and “Temporary files” → OK. This can free several GB that Windows reserves for old update files.
The “Windows Update Cleanup” option in Disk Cleanup specifically removes update packages that were already installed and are only being kept as rollback insurance. Removing them doesn’t affect Windows stability — it just removes the ability to roll back to those specific versions.
Run the troubleshooter
Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run. The troubleshooter checks for stopped services, corrupted download cache, and common configuration issues. It takes 2 minutes and sometimes resolves slow updates caused by service interruptions without requiring manual investigation. Low effort, worth trying before the more involved steps.
SFC and DISM for slow update installation
Updates that download quickly but install slowly (or fail during installation) often encounter corrupted system files that slow down or block the installation. Fixing those files before re-attempting the update:
DISM /Online /Cleanup-Image /RestoreHealthThen after it completes:
sfc /scannowAdministrator Command Prompt. DISM restores the component store; SFC repairs individual system files. Run DISM before SFC (DISM provides the clean source that SFC uses for repairs). After both complete: retry the update. If SFC finds and repairs corruption: the next update attempt is typically significantly faster.
Antivirus and update download speed
Real-time antivirus scans every file Windows Update downloads and writes to disk. On machines with aggressive antivirus configurations: this scanning adds 30–50% to download and extraction time. Temporarily pausing real-time scanning during an update (not disabling the antivirus, just the real-time scanning component) noticeably speeds up the process.
Re-enable real-time scanning immediately after the update completes. The risk window is small — Windows Update content from Microsoft’s servers is trusted, and the risk of temporarily not scanning those specific files is minimal compared to the time saved.
Manual update via Update Catalog
For a specific update that keeps downloading slowly or failing: install it manually. Find the KB number in Update history → go to catalog.update.microsoft.com → search it → download the correct x64 version → run as administrator. This bypasses the Windows Update Agent’s download mechanism entirely, which can get stuck or rate-limited, and installs the same update through a direct path.
Our guide on Windows 11 update stuck covers the update repair commands and the Media Creation Tool for major feature upgrades when the standard update path has deeper problems. For the post-update issues that sometimes appear once a slow update finally completes, our performance guide covers the background processes that sometimes ramp up after updates. Microsoft’s Windows Update documentation covers the UsoClient.exe scan command and the Windows Update log analysis (Get-WindowsUpdateLog PowerShell command) for detailed investigation of specific slow update causes.
Delivery Optimization slowing your download
Windows Update Delivery Optimization (WUDO) uploads portions of updates to other PCs while downloading updates. This peer-to-peer sharing can slow your download if upload bandwidth is being consumed by sharing with others on the internet. Settings → Windows Update → Advanced options → Delivery Optimization → Allow downloads from other PCs → if set to “PCs on my local network and the internet”: the machine is sharing updates with strangers, consuming upload bandwidth that affects download speed on asymmetric connections.
Change to “Devices on my local network only” or disable it during the current update: this eliminates the upload overhead while maintaining the ability to get peer-to-peer downloads from others. You can re-enable internet sharing after the update completes.
Pending restart and update accumulation
Updates that require a restart are staged but not applied until restart. On machines that haven’t restarted in weeks: multiple updates accumulate in the “pending restart” state. The next update attempt has to wait for all pending updates to process before it can begin its own installation — which appears as extreme slowness when it’s actually sequential processing of a backlog.
Restarting first (Settings → Windows Update → Restart now if a restart is pending) clears the accumulated queue. The next update check after the restart installs fresh against a clean update state rather than processing on top of a backlog.
Feature updates vs cumulative updates — very different timelines
Windows 11 has two types of major updates: cumulative monthly updates (security patches, bug fixes) and annual feature updates (new Windows version). These have completely different installation timelines:
- Monthly cumulative updates: 15–30 minutes on SSD, 30–60 minutes on HDD. Progress is usually linear once download completes.
- Annual feature updates: 30–120 minutes on SSD, 60–180 minutes on HDD. Extended periods at specific percentages (40%, 70%, 100%) are normal as the installation stages different phases.
Knowing which type is installing changes the “is this too slow?” assessment significantly. Feature updates stalling at 40% for 20 minutes are normal; monthly patches stalling at 40% for 60 minutes warrant investigation.
Update background service restarts
Win + R → services.msc → confirm these are Running: Windows Update, Background Intelligent Transfer Service (BITS), Cryptographic Services, and Windows Update Medic Service. Restart any that are stopped. BITS specifically handles the background download of update files — if it’s stopped, updates download at reduced speed or not at all.
Also check: Services → Windows Update → Properties → Startup type → should be “Automatic (Delayed Start)” — this ensures the service starts automatically but waits until other critical services are running. If set to “Manual”: updates won’t download automatically.
Network bandwidth and update server selection
Windows Update selects Microsoft’s update servers automatically. On some network configurations — corporate proxies, VPNs, or ISPs with poor routing to Microsoft’s CDN — the selected server may be suboptimal. A VPN that routes through a distant country adds significant latency to every file chunk in the update download.
Disconnect any VPN before updating. If a corporate proxy is required: confirm the proxy allows traffic to windowsupdate.microsoft.com, update.microsoft.com, and download.windowsupdate.com at adequate speed. Proxy-side logging usually shows update download speeds that can confirm whether the proxy is the bottleneck.
Paused updates and delayed restart
Settings → Windows Update → Advanced options → “Pause updates” — if updates have been paused and are now past the pause period, Windows may try to install a large backlog all at once. The accumulated updates process sequentially, making the total update time appear extreme. Unpausing and allowing the machine to restart after each batch (rather than running everything in one marathon session) keeps each update cycle manageable.
Windows Update using high disk I/O
The Windows Module Installer (TrustedInstaller) process uses intensive disk I/O during update installation. On machines with HDDs, this process can run at near-peak disk capacity, making the machine feel completely unresponsive during updates. Task Manager → Performance → Disk → if at 90–100% during a slow update: TrustedInstaller is working normally but the HDD is the bottleneck.
Options: leave the machine alone during updates (don’t use it while TrustedInstaller is active), schedule updates during off-hours (Settings → Windows Update → Schedule the restart), or upgrade to an SSD which reduces TrustedInstaller’s disk I/O time from hours to minutes. An SSD upgrade is the single most effective improvement for Windows update speed on older machines — often reducing update time by 70% or more.
Reset Windows Update components completely
For persistent update slowness that the cache clear alone doesn’t resolve: a more complete reset includes renaming the entire SoftwareDistribution database (not just the Download folder):
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 forces Windows Update to rebuild its entire local database from scratch rather than using potentially corrupted accumulated state. The .old folders can be deleted after confirming updates work normally. This is more disruptive than the cache clear but addresses cases where the metadata database itself (not just the download cache) has become corrupted or excessively fragmented over time.
Using Windows Update for Business or WSUS — corporate scenarios
In corporate environments: Windows Update speed is often controlled by Windows Update for Business or WSUS (Windows Server Update Services) configuration. Updates are downloaded from the corporate WSUS server rather than Microsoft’s servers, and the WSUS server’s bandwidth, storage, and network position significantly affect update download speed for all managed machines.
If managed machines are consistently slow to download updates while home machines are fast: the WSUS server’s bandwidth or the network connection between client machines and the WSUS server is the bottleneck. IT can address this through WSUS server optimisation, enabling Delivery Optimization for peer-to-peer sharing within the corporate network, or configuring clients to download directly from Microsoft CDN for machines outside the office network.
In summary: for slow updates, the order of operations is patience first (confirm it’s actually slow, not just working invisibly), then disk space check, then cache clear, then antivirus pause. These four steps resolve the majority of slow update situations. The DISM/SFC approach is for slow installation specifically (not slow download), and the complete component reset is for persistent cases where the standard cache clear doesn’t take hold. The underlying hardware limit (HDD vs SSD) is the only cause that can’t be addressed through software changes — knowing whether the machine has an HDD or SSD immediately calibrates expectations for any Windows update.
Monitoring update progress accurately
The Windows Update percentage in Settings isn’t always accurate — it sometimes jumps, sometimes stalls at round numbers (0%, 40%, 100%) for extended periods that don’t reflect actual installation progress. For more reliable progress indication: open an administrator Command Prompt and run wuauclt /detectnow to trigger a fresh update check, or navigate to Event Viewer → Windows Logs → Setup → the Setup log records every step of the installation process with timestamps. Watching the Setup log update in real-time confirms the installation is actively progressing even when the Settings UI appears frozen. Our guide on Windows 11 Stuck on Identifying Network covers an adjacent issue.
One thing that helps with any update: keep the machine connected to power, on ethernet if possible, and leave it alone. Closing applications reduces CPU and disk competition during TrustedInstaller’s installation work. Switching from Wi-Fi to ethernet eliminates wireless variability from the download speed. And using power rather than battery prevents Windows from throttling the CPU to preserve battery, which would extend installation time further. These three steps are quick and collectively reduce update time noticeably on laptops where any of the three are non-ideal. See also Windows Update Stuck on Windows 11 for a related case.
