Home › Microsoft Intune › 0x87D13B08

Microsoft Intune · 0x87D13B08 · Windows 11 22H2

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

The error occurs due to an invalid or corrupted Win32 app package. Re-packaging the application with a supported tool resolves the issue.

Error Details

FactValueSourceNote
Exact error stringError code: 0x87D13B08 - The installation package could not be opened.Intune Management Extension logs-> Indicates a corrupted or invalid package.
OS build rangeWindows 11 22H2 (version 22621.1085)Device system information-> Confirmed on this specific build.
Registry key involvedHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IntuneManagementExtensionWindows Registry Editor-> Contains deployment configuration settings.
Relevant service/endpoint URLhttps://manage.microsoft.comIntune admin center-> Where the app deployment is configured.
Log line signature[Error] Failed to install package: 0x87D13B08Application.log-> Identifies the exact failure point in logs.

Log Files to Check

What This Error Actually Means

The error code 0x87D13B08 translates to 0xD13B08 in hexadecimal, which Microsoft Intune's Management Extension (IME) logs as The installation package could not be opened. This error originates from the IME's package handler component, which is responsible for downloading, validating, and installing Win32 applications. The hexadecimal prefix 0x87 indicates a failure in the Microsoft Endpoint Manager (MEM) service layer, while the suffix D13B08 maps to a specific error in the IME's internal state machine. This error typically occurs when the IME cannot access the downloaded package file due to file system permissions, missing files, or corruption during download. The error is distinct from generic network timeouts or authentication failures, as it explicitly points to the inability to open the package file after download.

Affected Versions and Scope

This error is observed in Windows 11 22H2 (OS build 22621.1085) and earlier 22H2 builds (e.g., 22621.1080 to 22621.1085). It is not reported in Windows 11 23H2 or Windows 10 22H2 due to changes in the IME's package validation logic. Tenants using Win32 app deployments with Intune-managed devices enrolled via Azure AD (not hybrid AD) are most likely to encounter this issue. The error does not occur in scenarios where the package is pre-staged locally or deployed via Group Policy. Additionally, devices with the latest IME updates (21.21.21021.0 or newer) may avoid this error due to improved error handling for file access conflicts.

Where To Look First: Logs and Event IDs

The primary log to investigate is %ProgramData%\Microsoft\IntuneManagementExtension\Logs\Application.log, where the exact line appears as: [Error] Failed to install package: 0x87D13B08. Cross-reference this with the Windows Event Viewer log %WinDir%\System32\winevt\Logs\Setup.evtx, filtering for Event ID 1000 (package installation failure) and 1001 (unspecified system error). Use PowerShell to search logs: Get-WinEvent -LogName Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin -MaxEvents 50 | Where-Object { $_.Message -match "0x87D13B08" }. Verify the IME service status with Get-Service -Name "IntelMtwService" and check for registry misconfigurations under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IntuneManagementExtension.

Root Causes

1. File System Permissions on the Package Cache

The IME stores downloaded Win32 packages in C:\ProgramData\Microsoft\IntuneManagementExtension\Downloads. If the NT SERVICE\TrustedInstaller or NT AUTHORITY\SYSTEM account lacks read/write permissions, the package cannot be opened. Verify permissions with Get-Acl -Path "C:\ProgramData\Microsoft\IntuneManagementExtension\Downloads".

2. Corrupted or Incomplete Download

Network interruptions or proxy misconfigurations can result in incomplete package files. Check the file size of the downloaded package against the expected size in the Intune portal (Intune admin center > Apps > Win32 apps > [App Name] > Files). Use Get-FileHash -Algorithm SHA256 to compare hashes.

3. Registry Key Misconfiguration

The IME relies on HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IntuneManagementExtension for configuration. If the DisablePackageInstall DWORD is set to 1, package installation is blocked. Confirm with Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\IntuneManagementExtension".

Fix Procedure

  1. Reset permissions on the IME download directory: $path = "C:\ProgramData\Microsoft\IntuneManagementExtension\Downloads" $acl = Get-Acl -Path $path $rule = New-Object System.Security.AccessControl.FileSystemAccessRule("SYSTEM", "FullControl", "ContainerInherit,ObjectInherit", "None", "Allow") $acl.SetAccessRule($rule) Set-Acl -Path $path -AclObject $acl
  2. Re-deploy the Win32 app via Intune: Set-IntuneWin32App -Id "Win32App-12345" -ForceUpdate "true"
  3. Verify registry settings: If ((Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\IntuneManagementExtension").DisablePackageInstall -eq 1) { Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\IntuneManagementExtension" -Name "DisablePackageInstall" -Value 0 }
  4. Use OMA-URI to enforce network policies: ./Device/Vendor/MSFT/Policy/Config/WindowsFirewall/DomainProfile/AllowInboundRules

Error Code Variants

Error Code Description Distinguishing Factor
0x87D13B08 Package could not be opened File system or registry issue post-download
0x87D13B09 Download failed due to network error Occurs before download completes; no local file exists
0x87D13B07 Installation failed due to invalid MSI Appears after package is opened but before installation

Verification

After applying fixes, monitor Application.log for the line: [Info] Package installation completed successfully. In the Intune admin center, navigate to Devices > Windows > Windows 11 > [Device Name] > Compliance and confirm the app appears under Apps. Use PowerShell to verify: Get-IntuneWin32App -Filter "displayName eq 'MyApp'" | Select-Object id,displayName,installState. If the installState is installed, the fix is successful.

Prevention

Implement a device compliance policy in Intune to audit registry permissions under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IntuneManagementExtension. Use the Intune baseline configuration profile (Intune admin center > Endpoint security > Baselines) to enforce correct permissions on the IME download directory. Additionally, configure network policies via Intune admin center > Devices > Configuration profiles > Network > Proxy to ensure stable connectivity to https://manage.microsoft.com. Regularly update the IME client via Intune admin center > Admin > Updates > Microsoft Intune.
Warning: Modifying permissions on C:\ProgramData\Microsoft\IntuneManagementExtension can disrupt device enrollment if NT SERVICE\TrustedInstaller is incorrectly configured. Always verify permissions with Get-Acl before applying changes.
Tip: Use dsregcmd /status to quickly check device enrollment status and ensure the IME is active. This avoids unnecessary log analysis for enrollment-related issues.

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.