Fixing a Windows Update Stuck Downloading

An update stuck downloading (as opposed to stuck installing, a distinct and separately-covered problem) usually traces to a corrupted download cache or a stuck background service, both fixable without waiting indefinitely.

Step 1: confirm it’s genuinely stuck, not just slow

Settings → Windows Update →
  watch the percentage over several minutes

A percentage that’s stable but not moving at all for 15+ minutes, on a connection that’s otherwise working, is a reasonable threshold for “stuck” rather than “slow.”

Step 2: run the built-in Windows Update Troubleshooter

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

This checks for and automatically fixes a number of common causes without manual intervention.

Step 3: restart the Windows Update services

net stop wuauserv
net stop bits
net stop cryptsvc
net start wuauserv
net start bits
net start cryptsvc

These three services (Windows Update, Background Intelligent Transfer Service, Cryptographic Services) handle the actual download and verification pipeline — restarting them clears a stuck in-memory state without touching any downloaded data yet.

Step 4: clear the SoftwareDistribution download cache

net stop wuauserv
net stop bits
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
net start wuauserv
net start bits

Renaming (rather than deleting) the folder lets Windows Update rebuild it fresh on the next attempt, while preserving the old contents in case something needs to be recovered from it.

Step 5: check actual network connectivity to Windows Update’s servers specifically

Test-NetConnection -ComputerName update.microsoft.com -Port 443

A general internet connection can work fine while something (a captive portal, a corporate proxy, a firewall rule) specifically blocks Windows Update’s own servers — distinct from a truly stuck download.

Step 6: retry the update after clearing the cache

Settings → Windows Update → Check for updates

Step 7: use the standalone Update Troubleshooter tool for a more thorough reset

Microsoft’s downloadable Windows Update Troubleshooter (distinct from the built-in one in Settings) performs a more thorough reset of update-related registry keys and services for cases the lighter built-in version doesn’t resolve.

Step 8: manually download and install via the Microsoft Update Catalog, as a last resort

For a specific update that consistently fails to download through the normal pipeline, downloading the standalone package directly from the Microsoft Update Catalog and installing it manually bypasses the download pipeline that’s stuck, entirely.

Why clearing SoftwareDistribution resolves most stuck-downloading cases

A corrupted partial download sitting in the SoftwareDistribution cache is the single most common cause of a download that never progresses — Windows Update keeps retrying against the same corrupted local data rather than starting fresh. Renaming that folder forces a clean restart of the download from scratch, which is why this step resolves the majority of genuinely stuck (rather than just slow) downloads.

Checking Delivery Optimization as a distinct, separate cause

Settings → Windows Update → Advanced options → Delivery Optimization

Delivery Optimization — Windows’ own peer-to-peer update distribution feature, sharing already-downloaded update chunks with other Windows machines on the local network or, depending on configuration, the wider internet — is a distinct download pathway from the direct Microsoft-server download the earlier steps address, and it can itself get stuck or throttled independently. If a download is stalled specifically while Delivery Optimization is configured for peer sharing beyond the local network, temporarily switching it to “PCs on my local network” only, or disabling it entirely as a test, isolates whether the peer-to-peer mechanism itself, rather than the direct download pipeline covered above, is the actual source of the stall.

Checking available disk space, an easily overlooked prerequisite

Get-PSDrive C

Windows Update requires meaningful free disk space to stage a download before installation, and a drive that’s nearly full can cause a download to stall silently rather than failing with an explicit, informative “not enough disk space” error message — confirming genuinely sufficient free space is available on the system drive is a quick, easily-overlooked check worth ruling out before working through the more involved service-restart and cache-clearing steps above, especially on a machine where storage has been running low for other, unrelated reasons.

When a corporate WSUS or Intune policy is silently controlling update behavior

On a domain-joined or Intune-managed machine specifically, update behavior may be centrally controlled by a Windows Server Update Services (WSUS) server or Intune policy rather than reaching Microsoft’s own servers directly at all — a stuck download in this configuration may reflect a problem on the organization’s own update-distribution infrastructure, not anything fixable from the individual client machine. Checking gpresult /r for any Windows Update-related Group Policy settings, or asking IT whether other managed machines are experiencing the identical symptom, distinguishes this organizational cause from a genuinely local, client-side problem before spending further time on the steps above.

Related:

Sources: