A cumulative update that stalls at the download stage is one of the more frustrating Windows Update failures, because nothing seems to be happening and the progress bar offers no clue why. On Lenovo laptops, KB download errors have a few brand-specific wrinkles on top of the usual causes, so it helps to work through them in a structured order rather than hammering the “Retry” button all evening.

The download phase depends on the Background Intelligent Transfer Service, the Windows Update service, and a healthy SoftwareDistribution cache. If any of those are tangled, the update can sit at 0 percent or flip between “Downloading” and “Retrying” indefinitely. The fixes below start with the least disruptive options and move toward manual installation, which is the reliable fallback when the automatic pipeline simply will not cooperate.

Why this happens

  • Corrupt SoftwareDistribution cache: Partially downloaded files for KB5062553 sit in the cache and keep failing integrity checks, so every retry re-downloads garbage.
  • Lenovo Vantage or ImController conflicts: Lenovo’s background utilities occasionally lock files or change power plans mid-download, interrupting the transfer.
  • Metered connection flag: Windows pauses or throttles update downloads on a connection marked as metered, and the UI does not always make that obvious.
  • Third-party antivirus filtering: Real-time scanners can quarantine or slow update payloads, especially on machines with strict download inspection rules.
  • Unstable network or VPN: Drops, captive portals, and aggressive VPN tunnels corrupt large cumulative update downloads before they finish.
  • Low disk space: Cumulative updates need several gigabytes of scratch space; when the drive is nearly full, the download phase can fail silently.
  • Outdated BIOS or chipset drivers: Older firmware on some Lenovo models mishandles the power-state changes the updater requests, freezing the download.
  • DNS or proxy misconfiguration: If the machine cannot reliably reach Microsoft’s update endpoints, the download never completes and eventually times out.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Run the Windows Update troubleshooter

The built-in troubleshooter resets the most common download-side problems automatically and is the fastest first step.

  1. Open Settings and go to System, then Troubleshoot.
  2. Select Other troubleshooters.
  3. Find Windows Update and click Run.
  4. Let the tool finish, apply any suggested fixes, then restart the laptop and retry the update.

Fix 2: Check for a metered connection

Windows will not pull a multi-gigabyte cumulative update over a connection it believes is metered.

  1. Open Settings and go to Network & internet, then Wi-Fi or Ethernet.
  2. Open the properties of your active connection.
  3. Turn off the Metered connection toggle if it is enabled.
  4. Return to Windows Update and click Check for updates again.

Fix 3: Clear the SoftwareDistribution cache

Wiping the download cache forces Windows Update to fetch a fresh, uncorrupted copy of the KB5062553 payload.

  1. Open Command Prompt as administrator.
  2. Run net stop wuauserv and then net stop bits to pause the update services.
  3. Open File Explorer and navigate to C:\Windows\SoftwareDistribution\Download.
  4. Delete everything inside the Download folder, not the folder itself.
  5. Back in Command Prompt, run net start wuauserv and net start bits.
  6. Restart the laptop and retry the update from Settings.

Fix 4: Update Lenovo drivers and BIOS

Bringing Lenovo-specific software current removes one of the most common brand-level blocks.

  1. Open Lenovo Vantage and check for system updates, including BIOS and chipset drivers.
  2. Install any pending Lenovo updates and restart when prompted.
  3. If you prefer, grab drivers directly from the official Lenovo support portal instead.
  4. After the drivers are current, retry KB5062553 from Windows Update.

Fix 5: Temporarily disable third-party antivirus

Overzealous download scanning is a classic cause of download-stage failures.

  1. Open your antivirus suite and disable real-time protection temporarily.
  2. Keep Windows Security running so the machine is not fully unprotected.
  3. Retry the KB5062553 download while protection is paused.
  4. Re-enable your antivirus immediately after the download succeeds, whether or not the install finishes.

Fix 6: Reset the Windows Update components

When the cache clear alone is not enough, resetting the full component stack repairs the download engine itself.

  1. Open Command Prompt as administrator.
  2. Stop the services: net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver.
  3. Rename the cache folders: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old.
  4. Restart the services: net start wuauserv, net start cryptSvc, net start bits, net start msiserver.
  5. Restart the laptop and check for updates again.

Fix 7: Install KB5062553 manually from the Update Catalog

If automatic delivery keeps failing, side-step it entirely with a manual install — the same update, just delivered as a local file.

  1. Visit the Microsoft Update Catalog and search for KB5062553.
  2. Download the .msu that matches your system, usually the x64 version for a Lenovo laptop.
  3. Double-click the downloaded file and follow the standalone installer prompts.
  4. Restart when asked, then confirm the KB appears in your update history.
  5. If the manual route interests you generally, see our guide on manually installing Windows updates on Windows 11 .
  6. If the failure code points to missing files rather than downloads, our 0x80070002 repair guide covers that sibling error.

Fix 8: Free disk space and check the drive

A starved drive can silently kill large downloads, so confirm there is room before your final retry.

  1. Open Settings, then System, then Storage, and check free space on C:.
  2. Use Storage Sense or Disk Cleanup to remove temporary files and old Windows installations.
  3. Aim for at least 20 GB of free space before a cumulative update.
  4. Open an admin Command Prompt and run chkdsk C: /f if you suspect file system errors, then restart and retry.

Closing

KB download failures look stubborn, but they almost always trace back to a corrupt cache, a network quirk, or an interfering utility — all of which are fixable with the sequence above. If the automatic path still refuses after these steps, the manual install from the Update Catalog is a fully supported way to get KB5062553 onto the machine, and pausing updates for a week remains a safe fallback while Microsoft addresses any server-side issues.

Frequently asked questions

Why does KB5062553 fail to download only on my Lenovo laptop?
Lenovo laptops often run extra background software such as Lenovo Vantage, ImController, and third-party power profiles that can interfere with Windows Update’s download engine. Outdated BIOS or chipset drivers can also stall a cumulative update. Most cases are fixable with the same general Windows Update repairs, plus a quick pass through Lenovo’s own support tools.
Is it safe to install KB5062553 manually with the .msu file?
Yes, as long as you download the package from Microsoft’s official Update Catalog and pick the correct edition for your system, x64 in most cases. Manual installation runs the exact same update through a local file instead of the Windows Update download service. It is a supported recovery method, not a hack, and it usually succeeds when automatic downloads keep failing.
Should I update my BIOS before retrying KB5062553?
A BIOS update is not required for every cumulative update, but Lenovo systems with older firmware sometimes stall mid-download because power and thermal management conflict with the installer. If your BIOS is more than a year old, updating it through Lenovo Vantage or the Lenovo support site is a sensible precaution that often removes the underlying block.
What if KB5062553 keeps failing even after a manual install attempt?
If both automatic and manual installation fail, the problem is usually deeper: a corrupted component store, a nearly full system reserved partition, or an incompatible driver. Run DISM and SFC repairs, check free disk space, and review the Windows Update log for the exact error code. Pausing updates for a week can also let Microsoft reissue a fixed package.