A Windows 10 update stuck downloading follows the same script every time: the progress bar sits at 0% — or freezes partway — for hours while everything else on the laptop works perfectly. No error message, no crash, just a download that refuses to download. On Windows 10 this is especially common around Patch Tuesday, when Microsoft’s servers are hammered and the local download pipeline is at its most fragile.
The reassuring fact is that a download stall is the safest update failure there is: nothing has been installed, nothing has been modified, and interrupting it carries zero risk. The suspects are the download pipeline itself — BITS (Background Intelligent Transfer Service) and its job queue, the Windows Update orchestration service, the network path, and the cache receiving the files. The fixes below unstick each layer, starting with the most common.
Why this happens
- Wedged BITS job queue. Dead transfer jobs block new downloads — the number one cause of 0% stalls.
- Metered connection pausing. Windows 10 aggressively defers downloads on metered connections by design.
- Corrupted partial downloads. Damaged cache files that the updater retries instead of replacing.
- Windows Update service hung. The orchestration service itself stuck and not dispatching work to BITS.
- VPN, proxy, or firewall interference. Network intermediaries throttling or breaking the large transfers.
- Antivirus network filtering. Security software inspecting the download stream and stalling it.
- Disk space exhaustion. Downloads with nowhere to be written stalling instead of failing clearly.
- Corrupted Delivery Optimization cache. Windows 10’s peer-to-peer download sharing can cache damaged update chunks that fail validation repeatedly, freezing the download at the same percentage on every attempt.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Verify the stall and check the deliberate blocks
Rule out the settings that pause downloads on purpose before repairing anything.
- Open Task Manager’s Performance tab and watch network activity for 5 minutes — real traffic means it is downloading despite the frozen percentage.
- Go to Settings > Network & Internet > Wi-Fi (or Ethernet), click your connection, and check Set as metered connection — turn it off; Windows 10 defers downloads on metered links.
- Disconnect any VPN and retry. VPN endpoints frequently throttle Microsoft’s update servers.
- With zero network activity for a full hour and no metered/VPN block, the pipeline is genuinely wedged — continue to Fix 2.
Fix 2: Reset the BITS queue
The classic 0% fix: clear the dead transfer jobs so fresh downloads can start.
- Open Command Prompt as administrator (search
cmd, right-click, Run as administrator). - Run
bitsadmin /reset /allusersto clear all stuck transfer jobs. - Open
services.msc, find Background Intelligent Transfer Service, set it to Automatic, and start it. - Go to Settings > Update & Security > Windows Update and click Check for updates — the download should begin within minutes. If the percentage still does not move, open Disk Cleanup, check Delivery Optimization Files, and clean them — stale peer-cached chunks are a common hidden cause of repeat stalls at the same percentage.
Fix 3: Restart the Windows Update services
If BITS is healthy, restart the orchestration layer around it.
- In an administrator Command Prompt:
net stop wuauserv,net stop bits,net stop cryptsvc. - Wait 30 seconds, then:
net start wuauserv,net start bits,net start cryptsvc. - Check for updates again.
- If downloads start but repeatedly stall at the same percentage, the cache is corrupted — move to Fix 4.
Fix 4: Rebuild the download cache
Wipe the damaged partial downloads and force Windows to fetch clean copies.
- In an administrator Command Prompt, stop the services:
net stop wuauserv,net stop bits,net stop cryptsvc. - Rename:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.oldandren C:\Windows\System32\catroot2 catroot2.old. - Restart the services:
net start wuauserv,net start bits,net start cryptsvc. - Check for updates — the download restarts from zero with a clean cache.
Fix 5: Free disk space and clear network interference
Downloads need landing room and a clear path.
- Ensure at least 10 GB free on C: (Settings > System > Storage); feature updates need closer to 20 GB.
- Run Disk Cleanup with Clean up system files to remove old update backups.
- Temporarily disable third-party antivirus web shields and retry.
- Try an alternate network (phone hotspot) to rule out router or ISP throttling, and run
ipconfig /flushdnsin an elevated prompt as a precaution.
Fix 6: Run the Windows Update troubleshooter
Windows 10’s troubleshooter automates the service and component checks — run it after the manual resets.
- Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update and run it.
- Apply every suggested fix, then restart.
- Check for updates again.
- If the troubleshooter will not run, our guide to the troubleshooter not working covers that separately (written for Windows 11, but the mechanics match).
Fix 7: Install the update manually from the Update Catalog
Bypass the broken pipeline with a browser download and direct install.
- Identify the stuck update’s KB number in View update history.
- Search the Microsoft Update Catalog
for that KB and download the x64
.msu. - Double-click the
.msuto install directly, then restart when prompted. - Verify in Update history. If the manual route also stalls, the issue is the network path — try a different connection. For the monthly-failure pattern on Windows 10, our guide to cumulative update failures covers the deeper repairs.
Closing
A Windows 10 download stall is a pipeline problem with pipeline fixes: reset BITS, restart the services, rebuild the cache, and check the metered-connection and VPN settings that pause downloads deliberately. Because nothing is installed yet, every step here is safe to try. Once downloads flow, keep the pipeline healthy — and if the download finishes but the install then fails, our guide to updates that fail to install picks up at the next phase (the techniques apply to Windows 10 as well as 11).
