Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | 0x87D00269: Deployment type not applicable | Intune Management Extension logs | Indicates device requirements mismatch |
| Affected OS build | Windows 11 23H2 (22000.2189+) | OS Version Check | App may require higher build or specific features |
| Registry key | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Intune\AppV | Local Registry | Stores app deployment configuration |
| Service endpoint | https://deviceenagement.microsoft.com | Intune Service | Used for policy/app deployment |
| Log line signature | Win32AppDeploymentFailed: 0x87D00269 | IMELogs.log | Correlate with deployment timestamp |
Log Files to Check
C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IMELogs.logC:\ProgramData\Microsoft\IntuneManagementExtension\Logs\Setup.log
What This Error Actually Means
The error code
0x87D00269 is raised by the **Intune Management Extension (IME)** during Win32 app deployment when the device fails to meet prerequisites defined in the app's deployment rules. This error specifically indicates that the deployment type (e.g., required architecture, OS version, or dependency) is incompatible with the target device. The component responsible for this error is the **Win32 app deployment engine** within IME, which validates device eligibility before initiating installation. The error string "Deployment type not applicable" confirms that the device does not satisfy the app's requirements, such as OS build, architecture (x86/x64), or prerequisite software. This is distinct from transient errors like network failures or authentication issues, as it is a hard validation failure.
Affected Versions and Scope
This error occurs exclusively on **Windows 11 23H2 (OS build 22000.2189 and newer)**. It does **not** affect older OS versions like Windows 11 21H2 (22000.x) or Windows 10 21H2/22H2 unless explicitly configured with incompatible app requirements. Tenants using **Win32 apps with strict OS version or architecture filters** are most likely to encounter this error. For example, apps requiring Windows 11 22H2 (22000.194) will fail on 23H2 devices if the deployment profile does not include the newer OS build. Conversely, tenants using **MSIX or PowerShell scripts** for deployment are unaffected, as these methods bypass the Win32 validation logic.
Where To Look First: Logs and Event IDs
The primary log file to inspect is
C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IMELogs.log, where the exact line
Win32AppDeploymentFailed: 0x87D00269 appears. Cross-reference this with
C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\Setup.log to identify configuration mismatches. Use the PowerShell cmdlet
Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 to check for related Event IDs. Specifically, **Event ID 1003** ("App deployment failed") and **Event ID 1004** ("Device does not meet app requirements") are associated with this error. Use
Get-IntuneWin32App -Filter "displayName eq 'AppName'" to verify app deployment rules in the Intune tenant.
Root Causes
1. OS Version Mismatch
The device's OS build (e.g., 22000.2189) does not meet the app's minimum OS requirement. For example, an app requiring Windows 11 22H2 (22000.194) will fail on 23H2 unless the deployment rule includes "22000.2189+". Verify by checking the app's **Minimum Operating System Version** in the Intune admin center (
Intune admin center > Apps > Win32 apps > [App] > Deployment settings).
2. Architecture Mismatch
The app is configured for a specific architecture (e.g., x86) but the device is x64. This is common when deploying 32-bit apps to 64-bit systems. Confirm by running
Get-CimInstance -ClassName Win32_OperatingSystem | Select OSArchitecture on the device and comparing it to the app's deployment architecture in Intune.
3. Registry Key Misconfiguration
The registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Intune\AppV may contain outdated or conflicting values that override deployment rules. For example, a custom value like
DisableWin32Validation set to
1 could bypass checks, leading to unexpected failures.
Fix Procedure
- **Update Deployment Rules in Intune**:
- Navigate to
Intune admin center > Apps > Win32 apps > [App] > Deployment settings.
- Update the **Minimum Operating System Version** to include
22000.2189 or higher.
- Set the **Architecture** to
Any architecture or match the device's architecture.
- Save changes and reassign the app to the device group.
- **Correct Registry Settings**:
- Open the registry editor and navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Intune\AppV.
- Delete or rename any custom keys like
DisableWin32Validation that bypass validation.
- Restart the
IntuneManagementExtension service with Restart-Service -Name "IntuneManagementExtension".