Windows Update stuck on downloading
Safely address an update download that stops progressing.
- Updated
- September 3, 2026
- Reading time
- 7 min read
- Windows support
- Windows 11 · Windows 10
Quick diagnosis
Safely address an update download that stops progressing. The key distinction is whether “Percentage stops” occurs by itself or together with “downloading repeats.” That difference helps separate slow connection from low space.
Symptoms
- Percentage stops
- Downloading repeats
Likely causes
- Slow connection
- Low space
- Pending restart
Quick reversible checks
- Wait while checking activity
- Restart and free 20 GB
Establish the scope
Confirm when percentage stops and whether downloading repeats. 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
Connect power, correct date and time, finish pending restarts, and run the Windows Update troubleshooter.
- Record the current state related to wait while checking activity.
- Apply the narrow change, then check whether percentage stops.
- Continue only if the result still points toward low space.
Investigate the cause
If other Windows components fail, run DISM RestoreHealth followed by SFC. Let both complete even if the percentage pauses.
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 slow connection, low space, pending restart for support.
Verification
- Repeat the affected task under the same conditions used to confirm percentage stops. 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 downloading repeats.
When to stop
Do not continue with broader resets when servicing repairs fail repeatedly or the same KB returns a specific 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.