Windows Update Stuck Downloading at the Same Percentage

An update sitting at 0% for forty minutes feels broken. Usually it is not — the progress figure in Windows Update is an estimate stitched together from several operations running in parallel, and some of those stages report nothing at all while they work.

So the first job is not to fix anything. It is to find out whether anything is actually wrong.

Tell a stalled download from a slow one

Open Task Manager with Ctrl+Shift+Esc, go to Performance, and click your network adapter.

• Sustained traffic, even a few hundred Kbps — the download is running. Leave it. The percentage will jump in a block when a stage completes.
• Flat zero for 15 minutes or more — nothing is being fetched and the update has genuinely stalled.

Worth checking the Processes tab too: TiWorker.exe or Windows Modules Installer Worker consuming CPU means Windows is unpacking or servicing components locally, which also produces a motionless percentage bar.

Set a realistic baseline before declaring failure. A monthly cumulative update is a few hundred megabytes to a gigabyte. A feature update is several gigabytes, and it is entirely normal for it to show 0% for ten minutes, leap to 40%, then sit there again.

The three causes worth separating

Check what is blocking it first

These take two minutes and resolve a decent share of cases on their own.

Is the connection metered? Settings → Network & internet → Wi-Fi → click your network name → check Metered connection. Turn it off temporarily. Windows deliberately holds back large downloads on metered links.

Are updates paused? Settings → Windows Update. If a pause is active the page shows a resume date. Click Resume updates.

Is there enough free space? A feature update needs roughly 20GB free, including space for the rollback copy. Settings → System → Storage shows it. If C: is nearly full, freeing up disk space on Windows covers what is safe to remove.

Is a VPN running? Windows Update uses Delivery Optimisation, which struggles through some VPN tunnels and corporate filters. Disconnect fully and quit the client, rather than just disconnecting.

Clear the update cache

This is the fix for a genuinely stalled download. You are deleting a partial, likely corrupt package so Windows fetches a clean one.

Open Terminal as administrator — right-click the Start button, choose Terminal (Admin).

Stop the services that hold the files open:

net stop wuauserv
net stop bits

Then delete the cached downloads. In File Explorer, open:

C:\Windows\SoftwareDistribution\Download

Select everything inside and delete it. Delete the contents, not the SoftwareDistribution folder itself, and do not touch C:\Windows\System32 while you are in there. If a file refuses to delete, the services did not stop — check the commands returned success.

Start the services again:

net start wuauserv
net start bits

Go back to Settings → Windows Update and click Check for updates. The download begins again from zero, and on a reasonable connection a cumulative update completes in a few minutes.

Run the built-in troubleshooter

Worth doing before the heavier repair, because it resets registration of the update components automatically and occasionally finds a service set to the wrong startup type.

Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run. On Windows 10 the path is Settings → Update & Security → Troubleshoot → Additional troubleshooters.

It is not magic, and it reports “no problems found” more often than it fixes anything. It costs two minutes.

Repair the underlying component store

If updates download but fail at install with an error code, the problem is usually damaged files in the Windows component store rather than the download at all.

In Terminal (Admin), run these in order and let each finish:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

The first repairs the component store using files pulled from Windows Update; the second checks protected system files against it. DISM frequently sits at 20.0% for several minutes and at 62.3% for longer. That is normal and not a hang.

Expect 10–30 minutes in total on a mechanical drive, less on an SSD. Restart afterwards, then retry the update.

When the update keeps failing on the same build

A single update that fails repeatedly while others succeed usually has a specific known problem, and the error code is the key to it. Settings → Windows Update → Update history lists each failure with a code such as 0x80070002. Searching that exact code alongside the KB number is more productive than general troubleshooting.

Two practical routes when one update will not install:

• Download it manually from the Microsoft Update Catalog using the KB number, and run the .msu file directly. This bypasses the download machinery entirely.
• Use the Installation Assistant or Media Creation tool for a feature update that will not come through Windows Update. An in-place upgrade from the ISO keeps your files and applications and replaces the system files wholesale.

An in-place upgrade is the heavy option but it is not a reset — your files, settings and installed programs survive. It is the usual last resort before considering a clean install.

What does not help

• Repeatedly clicking Check for updates. It queues another check behind the one already running.
• Disabling Windows Update permanently to make the error go away. Unpatched machines are the single most common ransomware entry point.
• Registry “update fix” scripts from forums. Many were written for Windows 7 and set values that no longer exist or no longer mean what they did.
• Third-party updater utilities. They drive the same API that is already failing.
• Waiting indefinitely. If network traffic has been flat for an hour, another hour changes nothing.

Realistic expectations

Clearing the SoftwareDistribution download cache resolves the majority of genuinely stalled downloads, and the replacement download usually completes in the time the stuck one had been frozen for.

Feature updates are different, and worth more patience: several gigabytes, long motionless stretches, then a restart that spends 20–40 minutes on a black screen showing a percentage. On a mechanical hard drive that stage can take over an hour. Interrupting it is the one genuinely risky thing you can do here.

If updates install fine but the machine feels worse afterwards, that is a separate and well-understood pattern — Windows 11 running slowly after an update covers the drivers and background tasks responsible.