KB5041585 downloads to 7% — and stays there. Or 0%. Or 100% “downloading” with nothing happening. The progress bar becomes a permanent fixture of your Windows Update screen, and every “Retry” just resumes the same frozen state. On Lenovo laptops this particular stuck-download pattern often traces back to network driver quirks or the update cache holding a corrupted partial file that the downloader keeps trying to resume.
Download-phase problems are actually good news: nothing has been installed yet, so there’s zero risk to your system, and the fixes are all about clearing the pipe and getting a clean copy. Work through them in order. If your issue is a different KB or the update downloads fine but fails at install, our cumulative-update install guide picks up where this leaves off.
One diagnostic that saves time: open Settings > Windows Update and watch the percentage for exactly five minutes. If it creeps upward even slowly, the download is working — just leave it alone, possibly overnight. If it’s byte-identical after five minutes on a connection you know is active (test by loading a webpage), the pipeline is wedged and the fixes below apply. Interrupting a slow-but-working download just forces it to restart from scratch, so confirm the stall before you clear anything.
Why this happens
- Corrupt partial download: A damaged chunk in SoftwareDistribution that resume keeps tripping over.
- Wedged BITS jobs: Background Intelligent Transfer Service jobs stuck in transient-error limbo.
- Metered connection throttling: Windows pausing the download without clearly saying so.
- VPN/proxy interference: Corporate VPNs and proxies breaking the CDN connection mid-transfer.
- Lenovo network driver issues: Outdated Wi-Fi/Ethernet drivers stalling sustained downloads.
- Delivery Optimization conflicts: Peer-to-peer sharing getting stuck on a bad peer.
- Disk space: Not enough room to stage the full package, silently halting the download.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Confirm it’s stuck, then pause and resume
Give the downloader one clean restart signal.
- Verify the percentage hasn’t moved for 60+ minutes on an active connection.
- In Settings > Windows Update, click Pause updates for 1 week, wait 2 minutes, then Resume updates.
- This resets the download session state — if it was a transient stall, the download restarts cleanly.
Fix 2: Check connection, VPN, and metered status
Eliminate the network side.
- Disconnect any VPN and disable proxy settings (Settings > Network & internet > Proxy).
- Check Metered connection on your active network — turn it off or enable Download updates over metered connections.
- Switch from Wi-Fi to wired Ethernet if possible for the download; Lenovo Wi-Fi drivers with power-saving bugs are a known stall source.
Fix 3: Clear the corrupted partial download
The highest-success fix for frozen percentages.
- Elevated Terminal:
net stop wuauserv,net stop bits. - Delete the contents of
C:\Windows\SoftwareDistribution\Download(leave the folder itself). net start wuauserv,net start bits, then Check for updates — the download restarts from zero with clean files.
Fix 4: Reset BITS and the full update cache
When partial-clearing isn’t enough.
- Elevated Terminal:
net stop wuauserv,net stop bits,net stop cryptsvc,net stop msiserver. - Rename
C:\Windows\SoftwareDistribution→SoftwareDistribution.oldandC:\Windows\System32\catroot2→catroot2.old. - Restart all four services; check for updates. Microsoft documents this reset at the Windows update support hub .
Fix 5: Update Lenovo network drivers
Stalled sustained transfers often mean driver-level network bugs.
- Get the latest Wi-Fi and Ethernet drivers from Lenovo Support for your exact model. Lenovo’s validated drivers matter here — generic Windows wireless drivers have a history of power-management bugs that stall long downloads.
- Install, restart, and retry the download.
- In Device Manager → network adapter → Properties > Power Management, uncheck Allow the computer to turn off this device to save power during the download. Also check the Advanced tab for power-saving features like “Selective suspend” and disable them temporarily — a Wi-Fi radio napping mid-download is a classic cause of the frozen-percentage symptom.
Fix 6: Limit Delivery Optimization interference
Peer-to-peer sharing occasionally wedges downloads.
- Settings > Windows Update > Advanced options > Delivery Optimization.
- Turn Allow downloads from other PCs off temporarily.
- Retry the download — pure CDN fetching is more predictable.
Fix 7: Manual download from the Update Catalog
Bypass the entire automatic pipeline.
- Go to the Microsoft Update Catalog and search KB5041585.
- Download the x64
.msu, disconnect the VPN, close Lenovo utilities, and run it. - The standalone installer doesn’t use BITS or the SoftwareDistribution cache at all.
Closing
A stuck download is a plumbing problem, not a system problem — clear the pipe (cache, BITS, network path) and the update flows. KB5041585 specifically has no known install-blocking bug; every stuck case traces to the download pipeline. Fix the pipeline once and every future KB downloads cleanly too. Keep Lenovo’s network drivers current and this particular headache stays away. And if a stalled download ever tips over into a half-installed update that won’t roll back, our undoing-changes recovery guide covers that next stage.
One preventive habit for Lenovo owners: run Lenovo’s own system update tool (Vantage or the support site) monthly for network and chipset drivers, separate from Windows Update days. Current network drivers are the single best defense against stuck downloads, and updating them proactively — rather than discovering they’re stale mid-crisis — turns this whole category of problem into something you read about instead of experience. The same principle applies to every fix in this guide: the cache reset you do calmly on a quiet afternoon beats the one you do frantically at midnight. And if this same stuck-download pattern ever appears for a different KB, you’ll recognize it instantly — the fixes are identical regardless of the update number, because the download pipeline doesn’t care which package it’s carrying. Same symptoms, same diagnosis, same fix — the KB number is just a label on an identical plumbing problem.
