Windows Update is supposed to run quietly in the background, but when it stalls at “Downloading” with a percentage that never moves, it can hold a PC hostage for hours. Microsoft has shipped Windows 11 updates to hundreds of millions of devices, yet download stalls remain one of the most reported update problems in support forums. The frustrating part is that the fix is rarely a single button. It is usually a short sequence of service resets, cache clears, and integrity checks that most people never try in the right order. This guide walks through what actually works, in the order that saves the most time, and flags where the official advice and the popular internet advice disagree. (Decky loader not working steam deck fix 2026)
Why Windows Update Gets Stuck on Downloading
Before touching anything, it helps to know what is happening underneath. Windows Update relies on two services working together: the Windows Update service (wuauserv), which orchestrates the update process, and the Background Intelligent Transfer Service (BITS), which handles the actual file transfer. When either service hangs, loses its network connection mid-transfer, or collides with a corrupted partial download, the progress bar freezes.
The most common culprits are:
- A corrupted partial download sitting in the update cache
- A hung or disabled BITS or wuauserv service
- A VPN, proxy, or metered connection interrupting the transfer
- Low disk space on the system drive
- Damaged system files that break the update pipeline
Microsoft’s own troubleshooting guidance starts with the built-in troubleshooter rather than manual resets, and that is a sensible first move because it is reversible and takes under two minutes. Everything after that is progressively more manual.
Step 1: Run the Built-In Windows Update Troubleshooter
The fastest check is the official one. On Windows 11, open Settings > System > Troubleshoot > Other troubleshooters, find Windows Update, and select Run. On Windows 10, the path is Settings > Update & Security > Troubleshoot > Additional troubleshooters.
The troubleshooter restarts the relevant services, checks component registration, and clears some stuck states automatically. It does not fix everything, but when it works, it works in minutes. A practical tip from years of support threads: run it twice. The first pass often clears the obvious fault, and the second pass catches a secondary issue the first run created. If the troubleshooter reports it fixed something, reboot before checking for updates again. Skipping the reboot is the single most common mistake people make here, and it makes a successful fix look like a failure. (How to fix a website that will not load)
Step 2: Restart the Update Services Manually
If the troubleshooter does nothing, restart the two services by hand. This is the step that resolves the largest share of stuck downloads because it forces a fresh connection to Microsoft’s servers.
- Press Windows + R, type `services.msc`, and press Enter.
- Scroll to Windows Update, right-click it, and choose Restart (or Stop, then Start).
- Do the same for Background Intelligent Transfer Service.
- If either service is set to Disabled, open Properties, change Startup type to Manual or Automatic, and start it.
- Return to Settings and check for updates again.
If you spend a lot of time in Windows menus, it is worth learning a few keyboard shortcuts to move between Settings, Services, and Explorer faster. Small time savings add up when you are troubleshooting.
Step 3: Clear the SoftwareDistribution Folder
This is the classic fix, and it is classic for a reason. The SoftwareDistribution folder at `C:WindowsSoftwareDistribution` is where Windows stores downloaded update files before installing them. If a download is corrupted or half-finished, Windows can keep retrying the same broken file forever.
The correct order matters:
- Stop the Windows Update and BITS services as described above.
- Open File Explorer and navigate to `C:WindowsSoftwareDistribution`.
- Rename the folder to `SoftwareDistribution.old` rather than deleting it outright. Renaming is safer; if something goes wrong, you can restore it.
- Restart both services.
- Run Windows Update again.
Windows recreates the folder automatically on the next check. A word of caution: some online guides tell people to delete the entire `C:WindowsSoftwareDistribution` tree while services are still running. That can leave locked files behind and produce cryptic errors. Stop the services first, every time.
Step 4: Check Disk Space, Network, and Metered Connections
Sometimes the update is not stuck at all. It is waiting. Three conditions cause Windows to pause downloads without a clear error:
| Condition | What Happens | Quick Check |
|---|---|---|
| Low disk space | Download pauses or fails silently | Settings > System > Storage |
| Metered connection | Windows defers large downloads | Settings > Network & Internet > Wi-Fi > properties |
| VPN or proxy | Transfer stalls or times out | Disconnect VPN, retry update |
Microsoft recommends keeping at least 20 GB free on the system drive for feature updates, and even cumulative updates need several gigabytes of working room. If the drive is nearly full, free space before doing anything else. Similarly, if a VPN is active, disconnect it and retry. Corporate proxies are a frequent hidden cause on work laptops, and in that case the IT department, not the user, usually needs to allow the update endpoints.
If the stall coincides with broader connectivity weirdness, the same diagnostic habits apply as when you troubleshoot a website that will not load: test another site, another network, and another browser before assuming the PC is at fault.
Step 5: Repair System Files with SFC and DISM
When services and cache resets fail, the problem often lives in damaged system files. Two Microsoft-documented commands address this, and they should be run in order:
- Open Command Prompt as administrator.
- Run `DISM /Online /Cleanup-Image /RestoreHealth` and wait for it to finish. This can take 10 to 20 minutes.
- Then run `sfc /scannow`.
- Reboot and retry the update.
DISM repairs the component store that Windows Update depends on, while SFC repairs protected system files. Running SFC first is a common mistake because SFC pulls replacement files from the component store; if that store is damaged, SFC cannot do its job. DISM first, SFC second.
If the machine has been sluggish in other ways too, it is worth checking for background problems separately. For example, if Task Manager shows an unrelated process eating the CPU, a guide on fixing antimalware service executable high CPU usage covers that scenario, and a machine under heavy load can make update downloads crawl.
Step 6: Reset Windows Update Components Fully
When nothing else works, a full component reset re-registers the update DLLs and rebuilds the update pipeline. This is a longer procedure, usually run from an elevated Command Prompt with a series of `net stop`, `regsvr32`, and `net start` commands, and it is well documented in Microsoft’s support library. The key discipline is to run the commands in the published order and reboot afterward.
A word about third-party “update fixer” tools: they are widely recommended in forum threads, but they are not Microsoft-supported, and some bundle unwanted software. They are a reasonable last resort only after the built-in steps have failed, and only from a reputable vendor. If you are already worried about what else might be running on the machine, checking for malware is a sensible parallel step; a scan with a reputable tool costs little, and the same approach used to check for viruses on a Windows PC applies here.
Windows 10 End of Support Changes the Calculus
One important context point: Windows 10 reached end of support on October 14, 2025, according to Microsoft’s published lifecycle. That does not mean Windows 10 machines stop working, but it does mean update-related advice written for Windows 10 may no longer match what Microsoft ships. If a Windows 10 PC is stuck downloading, the practical question is less “how do I unstick this update” and more “should this machine move to Windows 11 or an extended support option.” Spending hours resurrecting an update pipeline on an unsupported OS is often the wrong trade. (Windows Update)
For Windows 11, the troubleshooting paths have shifted between releases, so menu names may differ slightly from what a guide shows. When in doubt, trust the path you see on screen over the path in any article, including this one.
When to Stop Troubleshooting and Reset
There is a point where further tinkering costs more than it saves. Consider a reset or reinstall when:
- The same update fails at the same percentage after every fix above
- DISM reports errors it cannot repair
- The update failure is accompanied by other system instability
Before that, back up important files. A reset is not a disaster, but it is disruptive, and preparation makes it a minor inconvenience instead of a bad week. If you have already been through a round of troubleshooting on another device, some of the same habits carry over; for instance, knowing the undo shortcut for Windows and Mac is a good reminder that a quick Ctrl+Z can rescue a mistaken settings change before it becomes a bigger problem.
Practical Habits That Prevent Stuck Downloads
A few habits reduce how often this problem appears at all:
- Keep at least 20 GB free on the system drive
- Avoid running updates on a metered connection or over a flaky VPN
- Let updates finish rather than force-restarting mid-download
- Reboot after any service or cache change before judging the result
- Check for updates during off-hours when Microsoft’s servers are less congested
None of these are glamorous, but they address the conditions that cause most stalls in the first place.
Conclusion
A Windows Update stuck on downloading is rarely a sign of a dying PC. It is usually a hung service, a corrupted partial download, or a network condition pausing the transfer. The sequence that resolves most cases is straightforward: run the built-in troubleshooter, restart wuauserv and BITS, rename the SoftwareDistribution folder with services stopped, verify disk space and connection type, then run DISM followed by SFC. Only after those fail should anyone reach for component resets or third-party tools. And on Windows 10, remember that the operating system is past its support date, which changes what “fixed” should mean. Work through the steps in order, reboot when told to, and most stuck downloads will resolve in under an hour.
FAQ
Why does Windows Update stay at the same percentage for hours?
The progress bar reflects a single download stream. If BITS loses its connection or the partial file is corrupted, Windows may keep retrying the same file without advancing. Restarting the BITS and Windows Update services, or clearing the SoftwareDistribution folder, usually breaks the loop.
Is it safe to delete the SoftwareDistribution folder?
It is safe to rename or delete its contents while the Windows Update and BITS services are stopped. Windows recreates the folder automatically. Deleting it while services are running can leave locked files and cause errors, so stop the services first.
How much free disk space does Windows Update need?
Microsoft recommends keeping roughly 20 GB free on the system drive for feature updates, and cumulative updates need several gigabytes of working space. Below that threshold, downloads may pause or fail without a clear message.
Does a VPN cause Windows Update to get stuck?
It can. VPNs and proxies sometimes interrupt the connection to Microsoft’s update servers, causing the transfer to stall. Disconnect the VPN, retry the update, and reconnect afterward if it succeeds.
Should I use a third-party Windows Update fixer tool?
Only as a last resort. These tools are not Microsoft-supported, and some bundle unwanted software. The built-in troubleshooter, service restarts, cache clears, and DISM/SFC repairs resolve most cases without third-party software.
Does Windows 10 end of support affect update troubleshooting?
Yes. Windows 10 reached end of support on October 14, 2025, so update behavior and available fixes may differ from current Windows 11 guidance. On an unsupported machine, weigh the effort of repairing updates against moving to a supported version.
