KB5055523 hanging at “Downloading” on a Lenovo laptop follows a familiar script: the percentage climbs a little, stalls, maybe flickers, and then nothing — for hours. The update package is fine. The download pipeline is not. Lenovo machines bring their own cast of suspects to this particular failure: Vantage’s background activity, power plans that strangle background transfers on battery, and network drivers that occasionally drop long downloads. This guide works through them in an order that respects your time.
Start on AC power with Vantage quieted. If you have fought this battle with a different KB before, the KB5036893 stuck-download guide for Lenovo covers the same Lenovo-specific ground for that package.
Lenovo laptops occupy an interesting middle ground in the Windows ecosystem: excellent hardware paired with a software layer — Vantage, power profiles, network utilities — that means well but occasionally meddles. Most of the time this layer is invisible. During large update downloads, though, its background scans, bandwidth management, and power throttling become load-bearing variables. That is why this guide treats Vantage and the power plan as first-class suspects rather than afterthoughts, and why the cumulative update failure guide is worth reading if KB5055523 is just the latest in a long line of troubled updates.
It is also worth understanding what “stuck at downloading” means mechanically. Windows Update downloads through BITS, which transfers in the background at low priority and is designed to survive interruptions — pausing when the network drops and resuming later. A truly stuck download means this resume machinery has wedged: BITS believes it is still working, Windows believes BITS is working, and the partial file sits incomplete while nothing actually transfers. Every fix below aims at unwedging that machinery or bypassing it entirely, which is why the manual install in Fix 7 is so effective — it does not use BITS at all.
Why this happens
- BITS stall: The transfer service freezes after a network blip and never resumes, reporting “Downloading” forever.
- Corrupt partial file: A damaged partial download that every resume attempt chokes on at the same point.
- Vantage contention: Lenovo Vantage’s scans and updates competing for bandwidth and file locks.
- Battery power throttling: Lenovo power plans limiting background network I/O when unplugged.
- Network driver issues: Lenovo Wi-Fi/Ethernet drivers that mishandle sustained large transfers.
- Metered connection settings: Windows holding back the download because the connection is flagged metered.
- VPN or proxy breakage: Long-lived update connections dying inside tunnels or corporate proxies.
- Disk space: Insufficient staging room causing a silent stall rather than a clean error.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Stabilize the environment
- Connect the AC adapter — non-negotiable for this process.
- Open Lenovo Vantage and pause automatic updates, driver scans, and Wi-Fi security features.
- Disconnect VPNs and pause bandwidth-heavy apps (cloud sync, streaming, game downloads).
- In Windows Update, click Retry and observe for 15 minutes. If the percentage moves, let it run.
Fix 2: Pause and resume to reset the transfer
- Pause updates for 7 days, wait 3 minutes, then resume.
- Watch whether the download restarts from zero (good — fresh transfer) or snaps back to the frozen percentage (bad — corrupt partial file).
- If it re-freezes, continue to the cache clear.
Fix 3: Restart the transfer services
- Open services.msc and restart Windows Update and Background Intelligent Transfer Service.
- In an elevated Command Prompt, run
bitsadmin /reset /allusersto kill wedged jobs. - Check for updates again.
Fix 4: Clear the SoftwareDistribution cache
- In an elevated Command Prompt:
net stop wuauserv,net stop bits,net stop cryptsvc. - Delete the contents of C:\Windows\SoftwareDistribution.
net startthe three services, reboot, and check for updates for a fully fresh download.
Fix 5: Update Lenovo network and chipset drivers
- Go to Lenovo Support , enter your exact model.
- Install the latest Wi-Fi, Ethernet, and chipset drivers.
- Restart and retry the download — this fixes the pattern where transfers start fast and die midway.
Fix 6: Check connection flags and free space
- In Settings, Network & internet, confirm the connection is not metered.
- Free at least 20 GB on the system drive via Disk Cleanup (include Windows Update Cleanup).
- Run
netsh winsock resetin an elevated Command Prompt and restart if downloads still stall at the network level.
Fix 7: Install KB5055523 manually
- Find KB5055523 on the Microsoft Update Catalog and download the x64 package.
- With Vantage still quieted, run the installer and restart when prompted.
- Verify in Update history. Manual installation bypasses every download-pipeline issue above in one move — it is the definitive fallback, and there is no shame in using it first if you are short on time.
Fix 8: Reset the network stack and change the route
When downloads stall at the network layer, reset the layer and try a new path.
- In an elevated Command Prompt, run
netsh winsock resetandnetsh int ip reset, then restart. - Connect via Ethernet if possible \u2014 wired connections eliminate Wi-Fi driver stalls entirely.
- If Ethernet is not available, try a phone hotspot to rule out your router; stale NAT sessions stall long transfers.
- Retry the update on the new route. If it completes, the laptop was innocent \u2014 update the Wi-Fi driver from Lenovo Support or restart the router before returning to normal.
Closing
Lenovo’s extra software layer makes stuck downloads slightly more likely and slightly more confusing \u2014 but the fix set is the same shape as everywhere else: calm the environment, reset the transfer machinery, clear the cache, refresh the drivers, change the network route, or walk around the pipeline with a manual install that bypasses BITS entirely. Once KB5055523 is in, re-enable Vantage, let the laptop return to its routine, and remember the lesson for next time: a download that has not moved in an hour is not going to move. Diagnose, reset, and move on.
