Windows Update remains at 0 percent
Determine whether an update is preparing, blocked, or unable to start.
- Updated
- September 18, 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.
Symptoms
- Downloading stays at 0%
- Updates remain queued
Likely causes
- Preparation delay
- Metered policy
- Network filtering
Quick reversible checks
- Observe status changes and disk/network activity while Windows remains responsive
- Check power, date/time, connection, free space, and any displayed prerequisite
Establish the scope
Use this path when an update stays queued or at 0% without any observed download progress. Look for paused updates, a metered-connection notice, a restart request, or managed-policy messages. Preparation can use disk activity without changing the number; if downloading previously advanced and stopped, use the related stuck-download article instead.
Apply the safer fix first
Keep power stable and allow preparation to continue while activity is evident. When Windows responds, review Pause updates, metered-connection notices, and requested restarts; change only settings you control. If no prerequisite explains the lack of progress, run the built-in Windows Update troubleshooter and save its result.
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
Do not override organization update policy or disable security filtering. Preserve the displayed status before changing an allowed setting.
Verification
- Check whether the queued update begins downloading or Windows now explains a remaining prerequisite.
- If the update moves beyond 0%, follow its final installation result rather than repeatedly changing preparation settings.
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.