Error 0x80240034 is the update engine admitting defeat during the download phase. The payload never arrived intact — the connection broke, the partial file corrupted, or the transfer service wedged itself. Unlike install-phase errors, this one never gets as far as touching your system files, which means the fixes are lower-risk and the manual-download bypass is particularly effective.

The strategy is simple: fix the download path, clear the damaged partial files, and if the engine still will not cooperate, fetch the package yourself through the browser. Most cases resolve in the first half of the list.

Download-phase errors are the kindest failures in the update world, and 0x80240034 — the download failed — is firmly in that category. Nothing was installed, nothing was half-applied, no system files were touched; the package simply never arrived intact. That makes the troubleshooting lower-stakes than install-phase errors: you are fixing a delivery problem, not performing surgery. It also makes the ultimate fallback unusually attractive — downloading the same package through your browser from the Update Catalog bypasses the entire failing delivery machinery in one move.

Why this happens

  • Interrupted connection: Drops, sleep/wake cycles, or network changes break the download mid-transfer.
  • Corrupt partial download: A damaged fragment in the cache fails verification and the resume keeps failing.
  • Wedged BITS queue: The Background Intelligent Transfer Service holds stuck jobs that block new downloads.
  • Metered connection throttling: Windows deprioritizes or pauses large downloads on metered networks.
  • VPN or proxy interference: Tunnels and proxies can corrupt or truncate large update payloads.
  • Antivirus download scanning: Real-time inspection sometimes mangles or blocks the payload stream.
  • Insufficient disk space: The download cannot complete when the drive fills mid-transfer.
  • DNS resolution failures: If update endpoints do not resolve reliably, downloads fail intermittently.

How to fix it

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

Pay attention to whether the download fails at the same percentage every time or at random points. A consistent failure point suggests a corrupt partial file being resumed or a network issue under sustained load; random failures point to general instability. That single observation tells you whether to prioritize the cache clear or the network fixes.

Fix 1: Retry on a stable connection

Rule out the transient network blip before deeper repairs.

  1. Connect to a stable network — preferably wired, or strong Wi-Fi close to the router.
  2. Disconnect any VPN completely.
  3. Turn off the metered connection toggle if it is enabled.
  4. Click Retry in Windows Update and watch whether the download progresses further.

Fix 2: Clear the download cache

Remove the corrupt partial files so the engine starts the download fresh.

  1. Open Command Prompt as administrator.
  2. Run net stop wuauserv and net stop bits.
  3. Delete everything inside C:\Windows\SoftwareDistribution\Download.
  4. Run net start wuauserv and net start bits.
  5. Restart and retry the download.

Fix 3: Reset the BITS transfer queue

Clear the wedged jobs blocking new downloads.

  1. In an admin Command Prompt, run bitsadmin /reset /allusers.
  2. Open services.msc and restart the Background Intelligent Transfer Service.
  3. Confirm its Startup type is Manual.
  4. Retry the update download.

Fix 4: Run the Windows Update troubleshooter

The automated tool repairs common download-side faults.

  1. Open Settings, System, Troubleshoot, Other troubleshooters.
  2. Run the Windows Update troubleshooter and apply its fixes.
  3. Restart the laptop and retry the download.

Fix 5: Temporarily pause antivirus

Eliminate download-stream interference from security software.

  1. Pause real-time protection in your antivirus suite.
  2. Retry the update download while protection is paused.
  3. Re-enable protection immediately after the download completes.
  4. If this was the cause, add an exclusion for the update process or adjust the scanner’s download inspection settings.

Fix 6: Reset the full Windows Update components

Rebuild the entire download and catalog infrastructure.

  1. Stop the services: net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver.
  2. Rename the folders: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old.
  3. Restart the services with net start for each.
  4. Reboot and retry.
  5. Our 0x80070002 guide covers this reset procedure with additional context.

Fix 7: Flush DNS and check connectivity

Fix name-resolution problems behind intermittent download failures.

  1. In an admin Command Prompt, run ipconfig /flushdns.
  2. Run ipconfig /release followed by ipconfig /renew if the network seems stale.
  3. Try switching to a public DNS like 8.8.8.8 temporarily in your adapter settings.
  4. Retry the download and see if it now completes.

Fix 8: Download the update manually from the Catalog

Bypass the broken download engine entirely with a browser download.

  1. Note the KB number of the failing update.
  2. Download the .msu from the Microsoft Update Catalog.
  3. Run the standalone installer and restart when prompted.
  4. Verify the KB in update history.
  5. See how to manually install Windows updates for the full walkthrough.

If downloads fail repeatedly on one network but succeed on another — a phone hotspot is the classic test — the problem is the network path, not your laptop. Some ISPs and managed networks throttle or interfere with the sustained connections that multi-gigabyte update downloads need, and no amount of cache clearing will fix that. In that situation the manual Catalog download is not just a fallback but the rational primary method: fetch the .msu on a working connection, transfer it over, and install locally. For the timeout-flavored sibling of this error, see our 0x80072EE2 guide .

Closing

Error 0x80240034 is a delivery problem, not an installation problem — the package never arrived intact. Clear the damaged partials, unstick the transfer queue, steady the network, and the download completes. And when the engine refuses to cooperate, the Update Catalog in your browser is the reliable Plan B.

Frequently asked questions

What does error 0x80240034 mean?
It is the download-failed error: Windows Update tried to fetch the update payload and the download did not complete. The causes range from interrupted connections and corrupt partial downloads to wedged transfer queues in the Background Intelligent Transfer Service. Because it is specifically a download-phase failure, the fixes focus on the network path and the download machinery rather than the installer.
Why does the download keep failing at the same point?
Repeated failure at the same percentage usually means a corrupt partial file that the engine keeps trying to resume, or a network issue that breaks the connection under sustained load. Clearing the download cache forces a fresh start instead of resuming the damaged partial file. If the network is the issue, the failure point often varies between attempts rather than repeating exactly.
Can I download the update another way when this keeps happening?
Yes, and it is often the fastest resolution. The Microsoft Update Catalog lets you download the exact KB package through your browser as a .msu file, bypassing the Windows Update download engine entirely. Running the standalone installer then applies the update locally. This is a fully supported approach, not a hack.
Does 0x80240034 mean Microsoft's servers are down?
Rarely. Microsoft’s update infrastructure is highly redundant, and a genuine server-side outage would affect millions simultaneously and be widely reported. When only your machine fails, the problem is local: your network path, your cache, or your transfer service. Check your connection and the local download machinery before suspecting the servers.