Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | 0x80240034 (WU_E_DOWNLOAD_FAILED) | Windows Update Agent logs | -> WindowsUpdate.log |
| Affected build range | Windows 11 23H2 | Microsoft Docs | |
| Registry key involved | HKLM\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization | Group Policy Management Console | -> Delivery Optimization settings |
| Relevant service/endpoint URL | https://*.update.microsoft.com | Network Monitor | |
| Log line signature | Error: 0x80240034 - BITS job failed during download. | WindowsUpdate.etl | -> Converted logs |
Log Files to Check
C:\Windows\Logs\WindowsUpdate\WindowsUpdate.logC:\Windows\Logs\WindowsUpdate\WindowsUpdate.etl
What This Error Actually Means
The error code 0x80240034, also known as WU_E_DOWNLOAD_FAILED, is raised by the Windows Update Agent when a BITS (Background Intelligent Transfer Service) job fails to complete during the download phase of an update package. The BITS service plays a crucial role in managing background file transfers for various Microsoft services, including updates and patches. When this error occurs, it typically indicates that there was an issue with the transfer process itself, such as network interruptions or insufficient disk space on the target drive.
Affected Versions and Scope
This specific error is observed primarily in Windows 11 version 23H2, although it can also appear in other recent builds of Windows 10 and Windows 11. The scope of this issue is particularly relevant for enterprise environments where network policies or configurations might interfere with BITS operations. For instance, if Delivery Optimization (DO) is disabled or misconfigured, updates may fail due to bandwidth limitations or cache issues.
Where To Look First: Logs and Event IDs
To diagnose the root cause of 0x80240034 errors, start by examining the following logs:
C:\Windows\Logs\WindowsUpdate\WindowsUpdate.log
C:\Windows\Logs\WindowsUpdate\WindowsUpdate.etl
In the
WindowsUpdate.log, you will find entries that describe the failure of a BITS job during download. Look for lines similar to:
Error: 0x80240034 - BITS job failed during download.
Additionally, review event logs using Event Viewer or PowerShell cmdlets like
Get-WinEvent. Focus on events with IDs such as
1006 and
1007, which provide detailed information about the BITS job status.
Root Causes
There are several distinct causes for this error, each requiring a different approach to resolution:
BITS Service Throttling or Disabled Delivery Optimization
When BITS is throttled below its minimum required bandwidth (500 Kbps) due to network policies or group settings, updates may fail. Additionally, if Delivery Optimization is disabled, the system relies solely on direct connections to Microsoft servers, which can lead to download failures in high-latency environments.
Insufficient Disk Space
The SoftwareDistribution\Download folder requires at least twice the size of the update package being downloaded. If this space is insufficient, BITS jobs will fail mid-transfer due to lack of storage capacity.
Misconfigured Delivery Optimization Caches
In enterprise environments where multiple clients are configured for peer-to-peer delivery optimization, cache misconfigurations can lead to download failures. This often occurs when the DO client cache is too small or has been corrupted.
Fix Procedure
To resolve 0x80240034 errors, follow these steps:
- Check Disk Space: Ensure that there is sufficient disk space available on the system drive. The minimum requirement is twice the size of the update package.
- Verify BITS Service Status: Use PowerShell to check if the BITS service is running and not throttled below 500 Kbps.
Get-Service -Name bits
- Review Delivery Optimization Settings: Check the registry key
HKLM\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization. Ensure that DO is enabled and properly configured for your environment.
- Analyze BITS Transfer Status: Use PowerShell to list all active BITS transfers.
Get-BitsTransfer -AllUsers
Note: Be cautious when terminating or modifying BITS jobs, as this can disrupt ongoing updates and potentially break enrolled devices.