Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | 0x87D01226 | Windows Event Logs, Intune Management Portal | -> Indicates a timeout during content download |
| Affected OS build range | Windows 11 22H2 | Microsoft Intune documentation | -> Specific to this version of Windows |
| Registry key involved | HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization | Registry Editor (regedit) | -> Check Delivery Optimization settings here |
| Relevant service/endpoint URL | Background Intelligent Transfer Service (BITS) | Services.msc | -> Ensure this service is running |
| Log line signature | Win32AppContentDownloadTimeout | Windows Event Logs | -> Look for this event in the logs |
Log Files to Check
C:\Windows\System32\winevt\Logs\Microsoft-Windows-IntuneManagementAgent%4Operational.evtxC:\Windows\System32\winevt\Logs\Microsoft-Windows-DeliveryOptimization%4Operational.evtx
What This Error Actually Means
The error code0x87D01226 is a hexadecimal representation of a failure in the Microsoft Intune Management Agent (MMAgent) during the deployment of Win32 applications. Breaking down the code: 0x87D0 identifies the component as the Intune Management Agent, while 0x1226 corresponds to a specific error within the component's internal logic. This error is explicitly tied to a timeout during the content download phase of a Win32 app deployment, which relies on either the Delivery Optimization (DO) service or the Background Intelligent Transfer Service (BITS). The timeout typically occurs when the device cannot establish a stable connection to the content source, or when the download process is interrupted by network policies, misconfigured services, or resource constraints. The error is logged by the MMAgent and can be correlated with events in the Microsoft-Windows-IntuneManagementAgent%4Operational.evtx log, often accompanied by a Win32AppContentDownloadTimeout signature.
Affected Versions and Scope
This error is explicitly observed onWindows 11 22H2 (OS build 22621.x) and is not reported in newer builds such as Windows 11 23H2 or Windows 10 22H2. The issue is most prevalent in tenants where Win32 app deployments are configured to use Delivery Optimization for content distribution, particularly when the HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization registry key is misconfigured or absent. The error does not affect devices using Microsoft Endpoint Manager (MEM) co-management or those relying solely on Microsoft Store for Business for app distribution. Additionally, tenants with strict network policies that block BITS or Delivery Optimization endpoints (e.g., http://d1.delivery.mp.microsoft.com) are more likely to encounter this issue. The error is not observed in scenarios where the Win32 app is hosted on a local intranet source or when direct download from Microsoft CDN is enabled without Delivery Optimization.
Where To Look First: Logs and Event IDs
The primary log files to investigate areC:\Windows\System32\winevt\Logs\Microsoft-Windows-IntuneManagementAgent%4Operational.evtx and C:\Windows\System32\winevt\Logs\Microsoft-Windows-DeliveryOptimization%4Operational.evtx. Use PowerShell to query these logs with the Get-WinEvent cmdlet. For example:
Get-WinEvent -LogName "Microsoft-Windows-IntuneManagementAgent/Operational" | Where-Object { $_.Message -like "*Win32AppContentDownloadTimeout*" }
Event ID 10016 in the Intune Management Agent log and Event ID 102 in the Delivery Optimization log are critical for correlation. Look for log lines containing the exact string Win32AppContentDownloadTimeout and timestamps matching the deployment failure. Additionally, check the Microsoft-Windows-Background Intelligent Transfer Service/Operational log for Event ID 10001, which indicates a BITS transfer failure. Use the Get-BitsTransfer PowerShell cmdlet to inspect active or failed transfers.
Root Causes
1. Delivery Optimization Policy Misconfiguration
The registry keyHKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization may lack the DownloadMode value (DWORD) set to 3 (allow peer and Microsoft CDN). If DownloadMode is set to 0 (disabled) or 1 (peer-only), the device cannot access the required content. Verify this by running:
Get-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization" -Name "DownloadMode"
2. BITS Service Failure
The Background Intelligent Transfer Service (BITS) may be stopped, disabled, or corrupted. Check the service status with:Get-Service -Name "BITS"
If the service is not running, restart it using:
Restart-Service -Name "BITS" -Force
3. Network Policy Restrictions
Firewall or proxy rules may block access to Delivery Optimization endpoints. Test connectivity tohttp://d1.delivery.mp.microsoft.com using:
Test-NetConnection -ComputerName "d1.delivery.mp.microsoft.com" -Port 80
A failure here indicates a network policy issue.
Fix Procedure
- Correct Delivery Optimization settings via registry:
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization" -Name "DownloadMode" -Value 3 - Restart the BITS service:
Restart-Service -Name "BITS" -Force - Deploy an Intune device configuration profile with the following OMA-URI:
./Device/Vendor/MSFT/Policy/Config/Windows/WindowsUpdate/DeliveryOptimization/DownloadModeSet the value to3via Intune admin center > Devices > Configuration > Profiles > Create profile. - Clear the Intune cache:
Remove-Item -Path "C:\ProgramData\Microsoft\IntuneManagementExtension\Cache" -Recurse -Force
Warning: Modifying the registry directly can destabilize enrolled devices. Always back up the registry before making changes.
Error Code Variants
| Error Code | Description | Root Cause | Differentiation |
|---|---|---|---|
0x87D01226 |
Win32 app content download timeout | DO/BITS failure | Log line contains Win32AppContentDownloadTimeout |
0x87D01225 |
Win32 app content download failed | Corrupted download | Event ID 10017 in MMAgent logs |
0x87D01227 |
Win32 app content validation failed | Hash mismatch | Event ID 10018 in MMAgent logs |
Verification
After applying fixes, verify resolution by re-initiating the Win32 app deployment and checking theMicrosoft-Windows-IntuneManagementAgent/Operational log for Event ID 10019, which indicates a successful download. Use:
Get-WinEvent -LogName "Microsoft-Windows-IntuneManagementAgent/Operational" | Where-Object { $_.Id -eq 10019 }
In the Intune admin center, navigate to Devices > All devices and confirm the device's compliance status is updated. Additionally, validate that the DownloadMode registry value remains set to 3 and that the BITS service is running.
Tip: Use
Get-EventLog -LogName System -Newest 50 to quickly identify recent BITS or DO-related failures.
Prevention
To prevent recurrence, enforce a baseline policy in Intune that configures theDownloadMode registry key via a device configuration profile. Navigate to Intune admin center > Devices > Configuration > Profiles > Create profile and select the Registry template. Additionally, implement a network policy that allows access to Delivery Optimization endpoints and ensures the BITS service is enabled. Regularly audit device compliance using:
Get-MgDeviceManagementDeviceCompliancePolicyNonComplianceReport
Finally, enable logging for the Microsoft-Windows-IntuneManagementAgent/Admin log to proactively detect deployment issues.