I've lost count of how many times a Windows 11 PC has stared at me with "Downloading 0%" or "Installing 0%" and not moved for half an hour. Sometimes I walk away, come back, and it's at 87%. Sometimes I come back and it's still at zero, the Windows Update service is idle, and nothing is on the wire.
The Settings app is not a progress bar you can trust. It often sits at 0% while the client is still resolving metadata, waiting on Delivery Optimization, or retrying a file that already failed. If you reboot and retry from Settings alone, you can spend an evening in a loop.
Here's the order I actually use.
Don't trust 0% until you know which phase you're in
Windows Update is a few services working in sequence: the Windows Update client (wuauserv), the Update Orchestrator (UsoSvc), and the component-based servicing stack that actually applies packages. "0%" can mean any of these:
- The client is still scanning or fetching the update's file list.
- Delivery Optimization is waiting on peers or a metered connection policy.
- A previous update is pending a reboot, so the new one never starts.
- The download cache or servicing store is damaged, so the client retries and reports no progress.
Until I know which one it is, I don't reset anything. Resetting SoftwareDistribution too early just throws away a download that was slowly working.
Read the log before you touch the cache
On modern Windows, the useful client traces live as ETL files under C:\Windows\Logs\WindowsUpdate. They are not a plain text WindowsUpdate.log until you merge them. In an elevated PowerShell window:
Get-WindowsUpdateLog -LogPath $env:USERPROFILE\Desktop\WindowsUpdate.log Microsoft documents the log locations and what each file is for in its Windows Update log files guide. After the merge, I search the text log for the last 20–30 minutes and look for obvious failure language: FAILED, 0x800, 0x802, DownloadManager, ComApi, and Idle.
A few patterns come up over and over:
- Lots of download activity and changing byte counts: you're probably not stuck, you're just looking at a stale percentage. Wait, or check Task Manager for
svchost/ Delivery Optimization network use. - Repeated
0x80240022,0x80070BC9, or similar, with no byte growth: the client is failing, not crawling. Time to check pending reboots and the cache. - Almost no new events after you clicked Download: the orchestrator never kicked off the job. That's a service, policy, or network-restriction problem, not a slow mirror.
I also glance at %windir%\Logs\CBS\CBS.log if the hang is on Installing rather than Downloading. Installation hangs belong to the servicing stack more often than to the download client.
Check for a pending reboot and a metered path
Before I delete anything, I check two boring things that waste more time than they should.
First, a pending reboot. If HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired exists, or if Component Based Servicing shows RebootPending, I restart and only then look at Settings again. A new cumulative update will sit at 0% forever if the previous one never finished. In PowerShell:
Test-Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired' Get-Item 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootPending' -ErrorAction SilentlyContinue Second, the network path. In Settings > Network, I make sure the Wi-Fi or Ethernet connection is not marked metered. Delivery Optimization will throttle or pause on metered links, and the Settings page still shows 0%. On a work laptop I also check whether a VPN or SSL-inspecting proxy is in the way; update downloads fail quietly in those environments.
Retrying the scan is fair after those two checks. It is not fair before them.
When the log says the download is dead, reset the cache
Once the log shows a stuck or failing download, the fastest recovery is to stop the update services, rename the download cache, and let Windows rebuild it. I don't do this as step one, but I do it as soon as the traces show the client is spinning.
If you want a straightforward click-through of that GUI and services path, including the usual SoftwareDistribution and catroot2 reset, this walkthrough on how to get Windows Update moving again when it sits at 0% covers the sequence clearly.
The short version I use from an elevated prompt:
Stop-Service wuauserv, bits, UsoSvc, cryptsvc -Force Rename-Item C:\Windows\SoftwareDistribution SoftwareDistribution.bak -ErrorAction Stop Rename-Item C:\Windows\System32\catroot2 catroot2.bak -ErrorAction SilentlyContinue Start-Service cryptsvc, bits, wuauserv, UsoSvc Then I run Check for updates again. If the rename fails because a file is locked, something is still holding the service. I reboot once and retry the rename before I go any further.
I leave the .bak folders around for a day in case I need a file from them, then delete them after a successful install.
If it still hangs on install, look at the servicing stack
A download that completes and then sits on "Installing 0%" is a different problem. That's usually CBS: a pending.xml that never cleared, a corrupted component store, or a servicing stack update that didn't apply.
In that case I run:
sfc /scannow DISM /Online /Cleanup-Image /RestoreHealth I give DISM a real chance to finish. If RestoreHealth itself hangs, I note the last lines of CBS.log and consider an in-place repair install as the clean fallback — the same Windows 11 ISO, "Keep personal files and apps." I treat that as a repair, not a wipe, and I only reach for it after the cache reset and DISM have failed.
Microsoft's Get-WindowsUpdateLog cmdlet is worth rerunning after each of these steps so you can see whether the client started a new, healthy session or is replaying the same error.
What I don't do first
I don't download random "Windows Update repair" utilities. I don't flip undocumented registry values I found in a forum thread. And I don't jump to a clean install because Settings looked frozen for twenty minutes.
Most of the 0% hangs I see resolve to one of four things: a pending reboot, a metered or filtered network, a dead download cache, or a servicing store that needs DISM. Read the log, decide which one you have, and then take the matching step. The percentage will move when the client actually has work to do — not when you stare at it.
![UI Practice - Duolingo [1]](https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F8uawvr6a0e07ilktpkk7.png)

