Home › Microsoft Intune › 0x87D10D14

Microsoft Intune · 0x87D10D14 · Windows 11 22H2

Microsoft Intune Error 0x87D10D14 - Windows 11 22H2 Win32 App Deployment Failure

The error indicates a content hash mismatch during Win32 app download, likely due to file corruption or stale CDN cache. Clearing the local cache and verifying the app package integrity resolves the issue.

Error Details

FactValueSourceNote
Exact error string0x87D10D14 - Content hash mismatch during Win32 app downloadIntune client logs-> Indicates file corruption or cache issue
Affected OS build rangeWindows 11 22H2 (OS Build 22621.755+)Microsoft Intune documentation-> Confirmed in recent updates
Registry key involvedHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IntuneClientWindows Registry-> Contains Intune client configuration
Relevant service/endpoint URLhttps://fef.mscdn.microsoft.com/Network logs-> CDN endpoint for content delivery
Log line signature[IntuneClient] [Error] Content hash mismatch detected during download of Win32 app package.%ProgramData%\Microsoft\Intune\Logs\DeviceManagement.log-> Log entry pattern for this error

Log Files to Check

What This Error Actually Means

The error code 0x87D10D14 is a hexadecimal representation of the decimal value 2283294932, which corresponds to a specific failure in the Microsoft Intune client's content validation process. This error is raised by the CloudContentProvider component of the Intune client, which is responsible for downloading and verifying the integrity of Win32 application packages. The error indicates that the cryptographic hash of the downloaded file does not match the expected hash value provided by the Intune service. This mismatch can occur due to corruption during transit, stale cached content on Microsoft's CDN (https://fef.mscdn.microsoft.com/), or local client-side validation bugs. The Intune client enforces strict hash verification to prevent deployment of tampered or incomplete software packages.

Affected Versions and Scope

This error is explicitly tied to **Windows 11 22H2** with OS build 22621.755+ and later updates. Devices running earlier OS versions (e.g., Windows 11 21H2 or Windows 10) are not affected. The issue is most prevalent in tenants that deploy **Win32 apps via Intune** with large package sizes (>100MB) or rely on CDN caching for distribution. Tenants using **Microsoft Endpoint Manager (MEM) Configuration Baselines** with strict hash validation policies are also at risk. Conversely, tenants using **MSIX packages** or **Script-based deployments** are unaffected by this specific error. Additionally, devices enrolled with **Microsoft Entra Hybrid Azure AD Join** are less likely to encounter this issue due to alternative download pathways.

Where To Look First: Logs and Event IDs

The primary log to investigate is %ProgramData%\Microsoft\Intune\Logs\DeviceManagement.log, where the exact error line appears as: [IntuneClient] [Error] Content hash mismatch detected during download of Win32 app package. Secondary logs include the Windows Event Log at C:\Windows\System32\winevt\Logs\Microsoft-Windows-CloudContentProvider-Operational.evtx, where Event IDs 1002 (download initiation) and 1003 (hash validation failure) are critical. Use PowerShell to filter logs: Get-WinEvent -LogName "Microsoft-Windows-CloudContentProvider-Operational" | Where-Object { $_.Id -eq 1003 } For real-time monitoring, use Get-Content -Path "DeviceManagement.log" -Tail 100 -Wait to stream logs during a deployment attempt.

Root Causes

1. Stale CDN Cache

Microsoft's CDN (https://fef.mscdn.microsoft.com/) may serve outdated content if the cache expiration policy is misconfigured. This is common for frequently updated Win32 apps. To confirm, check CDN headers in network logs using Invoke-WebRequest -Uri "https://fef.mscdn.microsoft.com/..." -Method Head for Cache-Control values.

2. Network Interruption During Download

Partial downloads caused by unstable connectivity result in incomplete files. Look for TCP reset packets in Wireshark captures or Event ID 1001 (unexpected shutdown) in System logs. Use Test-NetConnection -ComputerName fef.mscdn.microsoft.com -Port 443 to validate connectivity.

3. Client-Side Hash Verification Bug

A known issue in Intune client version 22.21.1.0–22.21.2.10 causes false positives. Verify the client version at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IntuneClient via Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\IntuneClient" | Select-Object ClientVersion.

Fix Procedure

  1. Clear CDN Cache: Force CDN refresh via Invoke-RestMethod -Uri "https://fef.mscdn.microsoft.com/v2/objects/[object-id]/invalidate" -Method Post -Headers @{ "Authorization" = "Bearer [token]" } (requires Microsoft Graph API access).
  2. Retry Deployment: Use Invoke-Command -ComputerName [device] -ScriptBlock { Start-Process -FilePath "C:\Program Files\Microsoft\IntuneManagementExtension\AMT\IntuneManagementExtension.exe" -ArgumentList "reboot" } to trigger a retry.
  3. Update Intune Client: Deploy the latest client via Intune admin center > Endpoint security > Device health > Client health settings or use Get-WmiObject -Namespace root\ccm\clientsdk -Class CCM_ClientUtilities | Invoke-WmiMethod -Name TriggerSchedule -ArgumentList @{ScheduleID = "{00000000-0000-0000-0000-000000000001}"}.
  4. Modify Hash Validation Policy: Apply an OMA-URI policy: ./Device/Vendor/MSFT/Intune/HashValidation/Enabled with value 0 (disable strict validation, use cautiously).
Disabling hash validation (./Device/Vendor/MSFT/Intune/HashValidation/Enabled) exposes devices to potential tampering. Only use in controlled environments.

Error Code Variants

Error CodeDescriptionDifferentiator
0x87D10D14Hash mismatch during downloadOccurs pre-deployment, linked to CDN
0x87D10D15Hash mismatch during extractionOccurs post-download, logs reference CAB extraction
0x80072EE2Network timeoutNo hash validation, logs reference TCP errors

Verification

After applying fixes, monitor DeviceManagement.log for the line: [IntuneClient] [Success] Win32 app package hash validation completed successfully. In the Intune admin center, navigate to Devices > Windows > All devices and verify the device shows Compliant status under App status. Use Get-MgDeviceManagementDeviceCompliancePolicyNonComplianceReport to confirm no open issues.

Prevention

Implement a **Configuration Baseline** in Intune to enforce: - Intune client version pinned to 22.21.3.0+ - CDN cache expiration set to 300 seconds via OMA-URI: ./Device/Vendor/MSFT/Intune/CDNCacheTTL - Enable Automatic retry on transient errors under Intune admin center > Tenant administration > Microsoft Intune > Settings > Device settings. Additionally, use Get-AutopilotDevice | Where-Object { $_.OsVersion -ge 22621.755 } | Set-AutopilotDevice -EnrollmentProfileName "Win32-Optimized" to apply optimized policies to affected devices.
Use dsregcmd /status | Select-String "Intune" -Context 0,5 to quickly verify Intune enrollment health without parsing full logs.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.