Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | 0x87D300D9 - Content download hash mismatch between CDN and expected package | Windows Event Logs, Intune Management Extension logs | -> Indicates a critical deployment failure |
| Affected OS build range | Windows 11 22H2 (OS Build 22621.755 and above) | Microsoft Intune documentation, Windows Update History | -> Issue observed in specific builds of Windows 11 |
| Registry key involved | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IntuneManagementExtension | Windows Registry Editor (Regedit) | -> Contains Intune client configuration settings |
| Relevant service/endpoint URL | https://fef.mscdn.microsoft.com/ | Network trace logs, Fiddler captures | -> CDN endpoint used for content delivery |
| Log line signature | [IntuneManagementExtension] [ContentDownload] [Error] Hash mismatch detected during content download. | %ProgramData%\Microsoft\IntuneManagementExtension\Logs\* | -> Signature in Intune Management Extension logs |
Log Files to Check
%ProgramData%\Microsoft\IntuneManagementExtension\Logs\ContentDownload.log%LocalAppData%\Packages\Microsoft.Intune.ControlPanel_cw5n1h2txyewy\AC\INetCache\Application Cache\LogFiles\Deployment.log
What This Error Actually Means
The error code
0x87D300D9 indicates a "Content download hash mismatch between CDN and expected package." This error is raised by the Microsoft Intune Management Extension component, specifically during the Win32 app deployment process. The Intune Management Extension (IME) is responsible for managing device configuration and application deployment in Windows 11 environments. When this error occurs, it means that the IME detected a discrepancy between the expected hash value of an application package and the actual hash value of the content downloaded from the Microsoft CDN (
https://fef.mscdn.microsoft.com/). This mismatch prevents the deployment from completing successfully.
Affected Versions and Scope
This error is specific to Windows 11 22H2 with OS builds starting at
22621.755 and above. It does not affect earlier versions of Windows 11 or other operating systems. The issue arises in tenant environments where Win32 applications are deployed via Microsoft Intune, particularly when those applications are hosted on the Microsoft CDN. Tenants using alternative content delivery mechanisms (e.g., private CDNs) may not encounter this error unless their infrastructure mirrors the affected Microsoft CDN behavior.
Where To Look First: Logs and Event IDs
To diagnose this issue, examine the following log files:
-
%ProgramData%\Microsoft\IntuneManagementExtension\Logs\ContentDownload.log
-
%LocalAppData%\Packages\Microsoft.Intune.ControlPanel_cw5n1h2txyewy\AC\INetCache\Application Cache\LogFiles\Deployment.log
Search for the exact log line:
[IntuneManagementExtension] [ContentDownload] [Error] Hash mismatch detected during content download.
Additionally, check the Windows Event Logs for related events. The relevant Event IDs are:
-
1002: Intune Management Extension - Content Download Failed
-
5003: Intune Management Extension - Package Validation Failed
Use the following PowerShell cmdlet to retrieve these events:
Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 | Where-Object { $_.Id -eq 1002 -or $_.Id -eq 5003 }
Root Causes
Corrupted Package on the Microsoft CDN
The most common cause is a corrupted or incomplete package hosted on the Microsoft CDN. This results in the downloaded content having a different hash than expected by Intune.
Network Interference or Proxies
Network devices (e.g., firewalls, proxies) may alter or cache content incorrectly, leading to hash mismatches. This is especially common in environments with strict Content Security Policies (CSPs).
Local Device Cache Corruption
The local device's cache of the Intune Management Extension may become corrupted, causing validation failures even if the CDN-delivered package is correct.
Fix Procedure
- Verify Package Integrity:
Use the following PowerShell cmdlet to check the integrity of the affected Win32 package in the Intune admin center:
Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'"
- Re-upload the Package:
If corruption is confirmed, re-upload the package to Intune. Navigate to:
Intune admin center > Apps > All apps > [Your App] > Upload new version
- Clear Local Cache:
On the affected device, clear the local cache by deleting contents from:
%LocalAppData%\Packages\Microsoft.Intune.ControlPanel_cw5n1h2txyewy\AC\INetCache\Application Cache\Cache
Warning: Clearing this cache will reset all locally cached Intune content. Devices may experience temporary performance impacts.
- Force Package Validation:
Use the following OMA-URI to force validation of the affected package:
./Device/Vendor/MSFT/Intune/Update/PackageValidation
Apply this setting via Group Policy or PowerShell:
Invoke-MgGraphRequest -Method POST -Uri "https://graph.microsoft.com/v1.0/deviceManagement/deviceConfigurations/[deviceConfigurationId]/assign"
- Inspect Network Configuration:
Use Fiddler or similar tools to inspect traffic to
https://fef.mscdn.microsoft.com/. Look for signs of content alteration or incomplete downloads.
Error Code Variants
| Error Code | Description | Distinguishing Factor |
| 0x87D300D9 | Hash mismatch between CDN and expected package | Specific to Intune Management Extension content validation |
| 0x87D300DA | Package download failed due to network issues | Mentions network errors in logs, not hash mismatches |
| 0x87D300DB | Invalid package format detected | Highlights package formatting issues rather than content mismatch |
Verification
After applying fixes, verify success by checking:
- The log files for
[IntuneManagementExtension] [ContentDownload] [Info] Content download completed successfully.
- Device status in the Intune admin center under
Devices > All devices > [Device Name], ensuring no pending errors.
Use this PowerShell cmdlet to confirm successful deployment:
Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'" | Select-Object deviceName, lastSyncDateTime
Prevention
Implement the following measures to prevent recurrence:
1. Regularly validate package integrity using
Get-MgDeviceManagement_managedDeviceDeploymentStatus.
2. Monitor network performance and ensure proper configuration of proxies/firewalls.
3. Apply the following OMA-URI setting to enforce strict package validation:
./Device/Vendor/MSFT/Intune/Update/PackageValidation
4. Schedule routine cache maintenance on devices using:
dsregcmd /status | Select-String "Cache"
Followed by manual cache clearing as needed.
By following these steps, you can resolve the
0x87D300D9 error and implement measures to prevent future occurrences.