If Windows Update is stuck at 0%, first identify where it stops, before download, during download, or after restart; a cache reset fixes download stalls, while servicing corruption usually needs the update components repaired. Skipping that step wastes time and can leave security fixes, drivers, and feature updates half-applied. This guide covers common checks and fixes for Windows 10 and Windows 11.
What the 0% screen usually means
At 0%, Windows may still be checking metadata, starting services, or waiting on a download queue. A real stall may look different from slow progress: no disk activity, no network activity, no response when you try to start or restart the update services in Services, and no visible change after a reasonable wait. Microsoft notes that the process can look stuck while Windows is still working in the background.
Download, install, and after-restart stalls are different
0% downloading usually points to service startup, network blocking, metered access, VPN filtering, or a bad update cache. 0% installing more often points to servicing problems, damaged system files, or blocked components. 0% after restart often means Windows is applying changes and may either resume or roll back on the next boot.
Say your laptop shows “Checking for updates” at 0% for a small security patch and the disk light never blinks. That is a different problem from a feature update that sits at 0% after a reboot for ten minutes while the fan is active and the drive is busy.
Which fix should you try first?
Start with the shortest path for the exact symptom you see. If the update has not moved for a long time, use the table below to decide whether to wait, reset the cache, restart services, or move to repair tools. That is faster than trying random fixes in the wrong order.
| Symptom pattern | Likely cause | First fix to try | Escalation step | When to stop waiting |
|---|---|---|---|---|
| 0% downloading, no network activity | BITS, wuauserv, VPN, metered connection, or cache block | Check services, then run the troubleshooter | Rename SoftwareDistribution and catroot2 | No change after 2 hours, or no disk/network activity |
| 0% installing, update screen open | Servicing corruption or blocked system files | Run DISM, then SFC | Manual KB install from Microsoft Update Catalog | Nothing changes for hours and Task Manager shows no update activity |
| 0% after restart | Boot-time servicing or rollback in progress | Wait briefly, then use Startup Repair if it stays frozen | Safe Mode or Uninstall Updates in recovery | No progress after a long wait, especially with no drive activity |
| Error code present | Metadata, service, or component-store failure | Record the code and run the troubleshooter | DISM, SFC, or manual KB installation | Once the same code repeats after a retry |
Run the Windows Update troubleshooter
The built-in troubleshooter checks the update path for blocked services, bad metadata, and download problems. Microsoft support lists it under Installation & updates and calls out “Troubleshoot problems updating Windows.” Run it before deeper repairs, then run it again after you reset the cache or restart update services.
- Open Settings > System > Troubleshoot > Other troubleshooters on Windows 11, or Settings > Update & Security > Troubleshoot > Additional troubleshooters on Windows 10.
- Select Windows Update.
- Choose Run and let it check for blocked services, cache issues, and update metadata problems.
- Retry Windows Update after it finishes.
- Run it again after any cache reset or service restart.
Check the update services
Windows Update depends on wuauserv and Background Intelligent Transfer Service (BITS). BITS moves update files in the background, and Microsoft support specifically tells you to verify it. If either service is stopped, updates can sit at 0% with no clear error.
- Press Win + R, type
services.msc, and press Enter. - Find Background Intelligent Transfer Service and confirm that its startup status is not Stopped.
- Find Windows Update, then right-click it and choose Restart.
- If a service will not start, open an elevated Command Prompt and run:
net stop wuauserv
net stop bits
net stop cryptsvc
net stop msiserver
net start wuauserv
net start bits
net start cryptsvc
net start msiserver
If BITS or wuauserv refuses to stay running, the problem is usually below the update UI. Move on to cache reset and repair steps instead of retrying the same download.
Clear the Windows Update cache
Renaming the update cache forces Windows to rebuild it. That often clears a download stall or broken metadata path. Stop the services first, or Windows can lock the folders and block the rename.
- Open an elevated Command Prompt.
- Run:
net stop wuauserv
net stop bits
net stop cryptsvc
net stop msiserver
- Rename the cache folders:
ren %windir%\SoftwareDistribution SoftwareDistribution.bak
ren %windir%\System32\catroot2 catroot2.bak
- Restart the services with the same four
net startcommands. - Reboot the PC, then retry Windows Update.
SoftwareDistribution stores Windows Update cache files. catroot2 holds update catalog data and rebuilds after reboot. If the stall returns, run the troubleshooter again after the reset.
Suppose a feature update stays at 0% downloading on a laptop that is on battery, connected through a VPN, and nearly full on C:. Fixing only one of those blocks may not be enough. You need the service state, network path, and free space to line up.
Why is Windows update stuck at 0 downloading?
A download-stage stall usually means the network path or update download service is blocked. Metered connections, VPNs, third-party antivirus, external USB devices, docks, and low C: space can all interrupt the download queue. Check those before moving to deeper repair.
- Turn off any VPN and pause third-party antivirus temporarily.
- Disconnect external drives, docks, and nonessential USB devices.
- Open Settings > Network & internet > your connection and confirm that Metered connection is off.
- Check C: in File Explorer and free space before retrying a feature update.
- Rerun the Windows Update troubleshooter if the download still stays at 0.
Feature updates can take hours and need enough free space on C:. Microsoft also says eligible devices may receive version 26H2, and rollout can be controlled with safeguard holds. That means a delayed download is not always a fault, but a locked 0% with no activity is a problem.
Repair Windows files if updates still stall
If services and cache reset do not help, repair the component store before running SFC. DISM repairs the servicing image that Windows Update depends on, and SFC checks protected Windows files after that. This order matters.
- Open an elevated Command Prompt.
- Run:
DISM /Online /Cleanup-Image /RestoreHealth
- Wait for the repair to finish.
- Then run:
sfc /scannow
- Restart the PC.
- Try Windows Update again.
If DISM or SFC reports unrepaired corruption, the next step is manual installation or an in-place upgrade. Those paths bypass some of the same update plumbing that may be failing.
Use the Microsoft update catalog
When automatic update keeps failing on the same KB, manual installation can skip a broken download path. The important part is matching the correct KB, architecture, and build. An x64 package will not help on ARM64, and a package for the wrong build can fail or do nothing useful.
- Open the update details in Settings > Windows Update and note the KB number.
- Search the Microsoft Update Catalog for that KB.
- Match x64, ARM64, or x86 to your device.
- Download the package that matches your Windows build.
- Run the downloaded update, then reboot.
If the catalog package installs, retry Windows Update afterward so the device can pick up anything else that was pending.
Still not working?
If the update still stops at 0 after cache resets, service restarts, DISM, and manual KB installation, move to a repair install. An in-place upgrade keeps personal files, settings, and apps while replacing the Windows system files that standard repair tools may miss. For a feature update, that is often the shortest final path.
- Use Windows 11 Installation Assistant if it is offered for your version.
- Or download the Windows 11 ISO, right-click it, choose Mount, and run setup.exe.
- Choose the option to keep personal files, settings, and apps.
- Let the setup finish and reboot when prompted.
If Windows still hangs on the boot screen after repeated restarts, use the recovery environment to repair the startup sequence, then choose Troubleshoot > Advanced options > Startup Repair. If that fails, use Uninstall latest quality update first, then Uninstall latest feature update if needed.
Prevention: keep the device off metered mode during large updates, leave space on C:, and avoid closing the lid or disconnecting power during a feature update.
Frequently asked questions
What to do if Windows update is stuck at 0?
Check whether it is stalled before download, during download, or after restart. Then use the matching fix path: run the Windows Update troubleshooter, confirm BITS and wuauserv are running, and if needed rename SoftwareDistribution and catroot2 before trying again.
How do I fix Windows update stuck at 0?
Start with Settings > System > Troubleshoot > Other troubleshooters > Windows Update on Windows 11, or Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update on Windows 10. If that fails, restart BITS and Windows Update, then run DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow.
Why is my Windows update stuck at 0?
The usual causes are a blocked update service, a broken cache, a network filter such as VPN or metered access, or servicing corruption. The update stage matters. A download stall and a post-restart stall do not use the same fix path.
Why is Windows update stuck at 0 installing?
An install-stage stall often points to component-store or file-integrity problems. Run DISM /Online /Cleanup-Image /RestoreHealth first, then sfc /scannow. If the same KB still fails, install it manually from the Microsoft Update Catalog with the correct architecture and build.
Should I wait or restart when Windows update is stuck at 0?
Wait if the device is still showing disk or network activity. If nothing changes for a long stretch, especially past 2 hours with no visible progress, use the service and cache fixes instead of forcing random restarts. A hard power-off should be saved for a frozen post-restart screen.
How do I clear a stuck Windows update download?
Stop wuauserv, bits, cryptsvc, and msiserver, then rename SoftwareDistribution and catroot2. Restart the services, reboot, and try again. If the download still stays at 0, confirm that VPN, antivirus, and metered connection settings are not blocking traffic.