Windows Update remains at 0 percent
Determine whether an update is preparing, blocked, or unable to start.
- Updated
- September 3, 2026
- Reading time
- 7 min read
- Windows support
- Windows 11 · Windows 10
Quick diagnosis
Determine whether an update is preparing, blocked, or unable to start. The key distinction is whether “Downloading stays at 0%” occurs by itself or together with “updates remain queued.” That difference helps separate preparation delay from metered policy.
Symptoms
- Downloading stays at 0%
- Updates remain queued
Likely causes
- Preparation delay
- Metered policy
- Network filtering
Quick reversible checks
- Wait 30 minutes
- Verify time, internet, and space
Establish the scope
Confirm when downloading stays at 0% and whether updates remain queued. Note the exact time and the last relevant change, then compare the closest known-good device, account, connection, or application using the same task.
Apply the safer fix first
Finish pending restarts, review Pause updates and metered settings, then run the built-in troubleshooter.
- Record the current state related to wait 30 minutes.
- Apply the narrow change, then check whether downloading stays at 0%.
- Continue only if the result still points toward metered policy.
Investigate the cause
Test a trusted network if allowed. Managed PCs may be governed by policy; preserve results for IT rather than bypassing controls.
Protect the recovery path
Before work that could affect windows update, protect relevant files and sign-in or recovery credentials. Keep the original error wording and the results involving preparation delay, metered policy, network filtering for support.
Verification
- Repeat the affected task under the same conditions used to confirm downloading stays at 0%. Confirm the symptom is gone, not merely that a Windows status label changed.
- Repeat the relevant connection, startup, sign-in, sleep, application, or device transition and specifically check whether updates remain queued.
When to stop
Do not continue with broader resets when a managed policy applies or several networks produce the same service error. Preserve the observations already collected and use the device maker, network administrator, Microsoft support, a qualified repair technician, or data-recovery help according to the evidence.
Review the safe troubleshooting workflow before any broader recovery step.