The download starts, climbs to some percentage — 8%, 46%, 99% — and then nothing. Hours pass. Your HP laptop’s internet works fine for everything else, but Windows Update sits frozen at the same number like a progress bar in a museum. Restarting sometimes kicks it forward a few percent before it freezes again at a new number. This is the stuck-download pattern, and on HP laptops it usually involves the standard corrupted-cache causes plus HP’s own update tooling getting in the way.
Windows does not download updates the way your browser downloads a file. The Background Intelligent Transfer Service fetches the package in chunks, verifies each one, and is designed to pause and resume across reboots and network changes. That design is normally a strength — it is why updates survive lid closes — but it has a failure mode: when a chunk is corrupt, the service resumes from the damaged data instead of discarding it, and every subsequent attempt stalls at the same point. The progress bar is not lying about the percentage; it is accurately reporting that the same broken chunk keeps failing verification.
This guide walks the full recovery in order: confirm the stall, remove HP-specific interference, repair the download pipeline, and — if all else fails — install the update by hand.
Why this happens
- Corrupted partial download. A damaged cached chunk makes every resume attempt stall at the same point.
- HP Support Assistant contention. HP’s tool downloading drivers simultaneously can conflict with Windows Update’s transfers.
- Metered connection throttling. Windows limits large downloads on connections it considers metered.
- VPN, proxy, or network filtering. Middleboxes breaking the connection to Microsoft’s update servers.
- Low disk space. Insufficient staging room silently halts the download.
- BITS service failure. The Background Intelligent Transfer Service wedged or misconfigured.
- Outdated HP network driver. The wireless or Ethernet driver mishandling sustained large transfers.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Verify the stall properly
Make sure you are fixing a real problem.
- Note the exact percentage in Settings > Windows Update, wait one hour, and check again. Zero movement confirms the stall.
- Verify your internet works normally for other tasks — streaming, browsing, speed test.
- Check free space on C: in Settings > System > Storage; you need several gigabytes free for the download to stage.
Fix 2: Quiet HP Support Assistant
Remove the HP-specific contention.
- Open HP Support Assistant and pause automatic updates and scheduled tune-ups.
- If it is mid-download of its own updates, let those finish or cancel them — do not run both updaters at once.
- Retry Windows Update with HP’s tool silent. If the download starts moving, contention was the cause.
Fix 3: Pause, restart, and resume
Force a clean download state.
- In Settings > Windows Update, click Pause updates for one week.
- Restart the laptop (a real restart, not Fast Startup shutdown).
- Resume updates and click Check for updates. The download restarts from zero instead of resuming the poisoned partial file.
Fix 4: Restart BITS and clear the download cache
Fix the transfer machinery directly. The Background Intelligent Transfer Service is the component that actually moves update bits, and when it wedges — or when the cache it writes to is corrupted — no amount of clicking Retry helps because every attempt reuses the same broken state. Stopping the services, deleting the poisoned partial downloads, and restarting fresh addresses both halves of the problem at once.
- Open an elevated Command Prompt and run:
net stop wuauserv net stop bits rd /s /q C:\Windows\SoftwareDistribution\Download net start wuauserv net start bits - Check for updates. The download starts fresh with a clean cache and a restarted transfer service.
- The same procedure with full detail is in our guide to resetting stuck update downloads .
Fix 5: Check metered settings, VPN, and the network driver
Clear the network-side blockers.
- Turn off Metered connection for your network in Settings > Network & internet.
- Disconnect any VPN completely and retry.
- Update the wireless/Ethernet driver from HP’s support site for your exact model — an outdated HP network driver can stall sustained large downloads specifically.
Fix 6: Install the update manually from the Catalog
Bypass the broken download pipeline.
- Note the KB number of the stuck update from Update history.
- Download it from the Microsoft Update Catalog
and run the
.msu. - This is the same update delivered by a different route. See how to install a KB manually from the Catalog for the full walkthrough.
Fix 7: Repair the update engine for the long term
Stop this from recurring.
- Run the Windows Update troubleshooter: Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run.
- Run
DISM /Online /Cleanup-Image /RestoreHealthandsfc /scannowfrom an elevated prompt to repair any servicing damage. - Keep HP’s drivers current via HP Support Assistant on your own schedule — separate from Windows Update runs. Microsoft’s Windows Update support hub documents the official download troubleshooting path.
Closing
A stuck download on an HP laptop is a pipeline problem with an HP accent: corrupted partial downloads and transfer service issues underneath, HP Support Assistant contention on top. Quiet HP’s tools, clear the cache, restart the transfer services, and the download almost always resumes properly. And when it does not, the Catalog manual install gets the same update onto the machine by a route the broken pipeline cannot block. Going forward, avoid running HP Support Assistant’s updates and Windows Update at the same time — sequencing them instead of stacking them prevents the contention behind most HP-specific stalls. A clean, one-updater-at-a-time routine is the simplest long-term prevention. Diagnose by phase, fix in order, and even the most stubborn download eventually finishes.
