Windows Update stuck at 0% can mean the download has not started, the installation is still preparing, or Windows has stopped progressing after a restart. The percentage alone cannot tell you which problem you have.
Check the wording beside it first. Downloading 0% calls for connection and download checks. Installing 0% calls for installation troubleshooting. A full-screen update message after restarting needs more caution because Windows may already be changing system files.
Before You Change Anything, Read the Update Status
Open Settings > Windows Update in Windows 11, or Settings > Update & Security > Windows Update in Windows 10, if you can still reach the desktop.
Note the update name, its KB number, and whether it says Downloading, Installing, Pending restart, or Retry. Take a screenshot if an error appears. These details matter more than the fact that the progress bar shows zero.
A feature upgrade, a cumulative update, and a driver update are different packages. When only one of them fails, you have a more focused problem than when every update refuses to start.
Also check whether another item in the update list is already progressing or waiting for a restart. Windows may be handling a prerequisite before moving on to the package you are watching.
Downloading 0%: Check What Could Be Blocking the Transfer
A download that stays at zero does not automatically mean Windows files are damaged. Start with the route between your PC and the update service.
Test the Connection and Its Restrictions
Open a few websites in a browser. Complete any Wi-Fi sign-in page, then return to Windows Update. If the connection keeps dropping, try a more stable Wi-Fi network or Ethernet before attempting repairs.
On a personal PC, disconnect a VPN temporarily if the download started failing while it was active. Then check for updates again. A browser working normally does not prove that a VPN or proxy is allowing the update service through.
Check whether your connection is metered under Settings > Network & internet, in the properties for your Wi-Fi or Ethernet connection. Metered connections can limit which updates download automatically. Use an unmetered connection when available, or explicitly allow the download if you accept the data usage.
On a managed work or school PC, leave organization-required VPN and proxy settings alone. An administrator may control the update source or approval schedule. Report the stalled update to IT with its name and status.
Make Sure Windows Has Somewhere to Put the Update
Open Settings > System > Storage and check the Windows drive. Updates need room for downloaded files and installation work, so a nearly full drive deserves attention even when the progress is still at zero.
Review Temporary files or Cleanup recommendations and remove items you recognize. Check the Downloads category carefully before selecting it, since it can contain files you want to keep.
There is no single free-space figure that guarantees every update will install. Follow any space requirement Windows displays for the particular update.
Restart Normally, Then Try the Update Troubleshooter
If you are still on the desktop and the download remains stalled, save your work and choose Start > Power > Restart. After signing in, reopen Windows Update and select Check for updates or Retry, as appropriate.
For Windows 11, open Get Help and search for “Windows Update troubleshooter.” Microsoft now directs users to that automated diagnostic tool. You may also find it through Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run.
Follow the prompts, restart if requested, and test the same update again. Microsoft’s Windows Update troubleshooting guidance is the official reference for the available repair options.
Installing 0%: Look for Preparation or a Repeat Failure
Installation progress can remain unchanged while Windows prepares an update. A short pause at zero is not enough evidence to reset the update system.
Keep the laptop connected to power and give the installation time to work. If you can access the desktop, Task Manager may show ongoing CPU or disk activity, although that activity does not prove the update itself is progressing. Equally, a quiet interval does not prove it has frozen.
A stronger sign of a problem is the same package repeatedly returning to zero, failing, or producing an error after a normal restart. In that situation, record the error and run the update troubleshooter before making manual changes.
Do not stop update services or remove update folders while installation is visibly progressing. Those steps belong to troubleshooting a failed attempt, not interrupting an active one.
After Restart: Do Not Treat the Update Screen Like a Download Window
The full-screen message saying that updates are underway is a different stage. You cannot fix it by changing Wi-Fi settings in Windows or clearing a folder while that screen is displayed.
Leave the PC plugged in. Avoid closing a laptop lid if doing so puts it to sleep, and allow the update to continue. The time needed varies with the update and the computer; there is no universal minute count after which 0% proves the installation has failed.
When the screen remains unchanged for several hours, the possibility of a genuine stall becomes more reasonable. Drive activity, changing messages, and automatic restarts can provide clues, but none is a perfect test on its own.
If the computer appears completely unresponsive after a prolonged wait and there is no normal restart option, a forced shutdown may become a last resort. It can interrupt installation and leave Windows needing recovery. Avoid repeated power cycling to try to hurry the process along.
For a PC stuck on the preparation message, use Stuck on Getting Windows Ready for the next steps. If you are inside the Windows Setup installer rather than Windows Update, Windows 11 Setup Stuck at 46% addresses that separate situation.
When Clearing the Update Cache Is Worth Trying
Consider a cache reset when you are back on the desktop, connection and storage checks pass, the troubleshooter has not resolved the issue, and downloads keep failing or restarting.
The cache holds downloaded update files. Resetting it can make Windows download fresh copies when the existing files or update state are causing trouble. It cannot repair an unreliable connection, remove an organization’s update restriction, or guarantee that a defective package will install.
Follow How to Clear Windows Update Cache for the service controls, folder locations, and permission checks. Finish the procedure by restarting the services and checking for updates again.
Avoid deleting random Windows folders or running a bulk repair script from an unfamiliar source. Make one change, retry the same update, and note whether the result changed.
The Same KB Still Fails: Investigate That Update
Repeatedly resetting the cache becomes less useful when a fresh download fails at the same point with the same error.
Press Windows + R, enter winver, and note your Windows version. Use that version and the KB number to check Microsoft’s Windows release health information. Look for a documented issue or workaround that matches your situation rather than assuming every recent update is broken.
If Windows itself is also malfunctioning, or the update reports a system-component problem, a repair may be more appropriate than another download reset. Supported Windows 11 devices can offer a repair reinstall that preserves files, apps, and settings. My guide to reinstalling the current Windows version to repair system files explains the option and its availability. Back up important files before repair work.
For Windows 10, remember that ordinary support ended on October 14, 2025. Receiving further security updates depends on the edition and applicable support or Extended Security Updates eligibility. Fixing a stuck download does not change those requirements.
Once the update completes, return to Windows Update and check whether another restart is required. Keep the KB number and any error you recorded until you confirm the installation succeeded. That makes it much easier to distinguish a resolved download problem from a package that is still failing.
