You click "Check for updates," the progress bar appears, and then… nothing. It sits at 0% for hours. No movement, no error code, just a frozen download. This is one of the most common headaches for Windows 10 users, and it usually means something is blocking the update process from even starting. The good news? The fix is almost always straightforward — no registry hacks or third-party tools required.

Why Does the Update Get Stuck at 0%?
Before diving into solutions, it helps to understand what's happening under the hood. When Windows Update starts downloading, it first checks for a clean connection to Microsoft's servers, verifies the update metadata, and then begins writing temporary files to the C:WindowsSoftwareDistribution folder. If any of these steps fail silently — due to corrupted cache, conflicting services, disk space issues, or network interruptions — the progress bar stays at zero.
Common culprits include:
- A bloated or corrupted SoftwareDistribution folder
- Windows Update services that have stopped or are stuck
- Insufficient free disk space (less than 20 GB for feature updates)
- Third-party antivirus or firewall blocking the download
- System file corruption that interferes with the update engine
Fix 1: Run the Built-in Windows Update Troubleshooter
Microsoft includes a dedicated troubleshooter that automates many of the basic checks. It's a good first step because it requires no manual commands and often resolves the issue on its own.
- Open Settings > Update & Security > Troubleshoot.
- Select Additional troubleshooters.
- Click Windows Update and then Run the troubleshooter.
- Follow the on-screen prompts. If it finds problems, it will attempt to fix them automatically.
If the troubleshooter reports that it couldn't identify the issue, move on to the manual methods below.
Fix 2: Reset the Windows Update Components Manually
This is the most reliable fix for a stuck 0% update. You'll stop the relevant services, clear the cache, and restart everything cleanly.
Step-by-step:
- Open Command Prompt as Administrator (right-click Start > Command Prompt (Admin) or Windows Terminal (Admin)).
- Stop the update services by running these commands one at a time:
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver - Rename the SoftwareDistribution and Catroot2 folders to force Windows to recreate them:
ren C:WindowsSoftwareDistribution SoftwareDistribution.old
ren C:WindowsSystem32catroot2 Catroot2.old - Restart the services you stopped:
net start wuauserv
net start cryptSvc
net start bits
net start msiserver - Close the command prompt and try checking for updates again.
This process clears out any corrupted temporary files and gives Windows Update a fresh start. In most cases, the download will begin immediately after this reset.

Fix 3: Check Disk Space and Run Disk Cleanup
Windows 10 requires a minimum of 20 GB of free space for feature updates and about 4 GB for cumulative updates. If your system drive is nearly full, the update will stall at 0% because it can't allocate temporary storage.
- Open File Explorer, right-click on C:, and select Properties.
- Check the free space. If it's below 20 GB, run Disk Cleanup (search for it in the Start menu).
- Click Clean up system files to remove old Windows updates, temporary files, and the recycle bin.
- If you still need more space, consider moving large files to an external drive or uninstalling unused applications.
Fix 4: Run System File Checker and DISM
Corrupted system files can prevent Windows Update from initializing. The built-in System File Checker (SFC) and Deployment Imaging Servicing and Management (DISM) tools can repair these.
- Open Command Prompt as Administrator.
- Run
sfc /scannow. This will scan and repair protected system files. It may take 15–30 minutes. - After SFC completes, run
DISM /Online /Cleanup-Image /RestoreHealth. This fixes the component store that SFC relies on. - Restart your computer and try the update again.
Fix 5: Temporarily Disable Third-Party Antivirus and Firewall
Some security software intercepts network traffic and can mistakenly block Windows Update downloads. To test if this is the issue, disable your antivirus real-time protection and any firewall rules temporarily.
- For Windows Defender: go to Virus & threat protection > Manage settings and turn off Real-time protection.
- For third-party software (Norton, McAfee, Bitdefender, etc.), right-click the tray icon and select Disable or Pause protection for 10–15 minutes.
- Also check if a third-party firewall is blocking
svchost.exeorwuauclt.exe. If you've previously configured custom firewall rules, you may need to review them.
Important: Re-enable your antivirus immediately after the update begins downloading. Do not leave your system unprotected.
Fix 6: Verify Date, Time, and Time Zone
Windows Update uses SSL certificates that rely on accurate system time. If your clock is off by even a few minutes, the update may fail to connect.
- Go to Settings > Time & Language > Date & time.
- Turn on Set time automatically and Set time zone automatically.
- Click Sync now under Synchronize your clock.
- Restart your computer and try the update again.
When All Else Fails: Use the Media Creation Tool
If none of the above methods get the update past 0%, you can bypass Windows Update entirely by using Microsoft's Media Creation Tool. This tool downloads the latest Windows 10 version directly and performs an in-place upgrade, preserving your files and applications.
- Visit the official Microsoft Download page for Windows 10 (search for "Media Creation Tool" from a trusted source).
- Download and run the tool.
- Select Upgrade this PC now.
- Follow the prompts. The tool will download the full update and install it, usually resolving any underlying corruption.
This is a nuclear option, but it works when the standard update mechanism is completely broken.
After applying any of these fixes, restart your computer before trying the update again. A clean reboot makes sure all stopped services and cleared caches take effect. If you're still stuck, open Event Viewer (Windows Logs > System) and look for error codes from WindowsUpdateClient — those codes can point you to more targeted fixes.
