Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | Win32 app not applicable for device - platform filter or requirement rule mismatch | Intune Management Extension logs | Error code 0x87D30068 |
| Affected OS build | Windows 11 23H2 (Build 22000+) | Device OS version | Confirmed on 23H2 |
| Registry key | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Intune\PlatformFilter | Local registry | Stores device filter rules |
| OMA-URI | ./Device/Vendor/MSFT/Intune/Win32App/DeploymentRules | Intune device configuration profile | Defines app eligibility |
| Service endpoint | https://devicemanagement.microsoft.com | Intune service | Policy evaluation endpoint |
Log Files to Check
%windir%\System32\LogFiles\Intune\IntuneManagementExtension.logEvent Viewer: Applications and Services Logs\Microsoft\IntuneManagementExtension\Operational
What This Error Actually Means
The error code
0x87D30068 is raised by the **Intune Management Extension (IME)** during Win32 app deployment when the device fails to meet the platform filter or requirement rule conditions defined in the Intune policy. This hexadecimal code translates to a decimal value of **2281684584**, though the exact decimal is rarely used in troubleshooting. The error explicitly indicates that the Win32 app deployment is being skipped because the device does not satisfy the criteria specified in the **platform filter** (e.g., OS version, architecture) or **requirement rules** (e.g., registry keys, group membership). The IME evaluates these rules during policy enforcement and logs this error when the device is excluded from the deployment scope.
Affected Versions and Scope
This error occurs on **Windows 11 23H2 (Build 22000+)** devices where a Win32 app deployment policy includes platform filters or requirement rules that exclude the device. It is not observed on devices running older OS builds (e.g., Windows 10 21H2) unless explicitly configured with conflicting rules. The issue is specific to tenants using **Intune Win32 app deployment policies** with **custom platform filters** or **device configuration profiles** that leverage requirement rules. It does **not** affect devices enrolled in co-management or hybrid Azure AD scenarios unless the same filters are applied.
Where To Look First: Logs and Event IDs
The primary log to investigate is
%windir%\System32\LogFiles\Intune\IntuneManagementExtension.log. Search for the exact line:
Win32 app not applicable for device - platform filter or requirement rule mismatch.
In **Event Viewer**, navigate to
Applications and Services Logs\Microsoft\IntuneManagementExtension\Operational and filter for **Event IDs 1001** (deployment failure) and **1003** (policy evaluation mismatch). For example:
- **Event ID 1001**: "Deployment of [App Name] failed due to rule mismatch."
- **Event ID 1003**: "Device excluded from policy [Policy Name] because [Rule Name] evaluated to false."
Use PowerShell to parse logs:
Get-WinEvent -LogName "Microsoft-IntuneManagementExtension/Operational" | Where-Message { $_ -match "0x87D30068" }.
Root Causes
1. Platform Filter Mismatch
The Win32 app’s deployment policy includes a platform filter (e.g., "Windows 10 21H2") that excludes **Windows 11 23H2**. To confirm, check the app’s deployment rules in the Intune portal:
Intune admin center > Apps > Win32 apps > [App Name] > Assignments > Platform filters.
2. Requirement Rule Exclusion
A device configuration profile with requirement rules (e.g., registry key checks) excludes the device. For example, a rule might require
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Intune\PlatformFilter to have a specific value. Verify in:
Intune admin center > Devices > Configuration profiles > [Profile Name] > Requirements.
3. Registry Key Misconfiguration
The registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Intune\PlatformFilter contains incorrect or missing values that conflict with the app’s deployment rules. Use
Get-ItemProperty in PowerShell to inspect its contents.
Fix Procedure
- **Update Platform Filters**:
In the Intune portal, navigate to
Intune admin center > Apps > Win32 apps > [App Name] > Assignments. Expand **Platform filters** and ensure **Windows 11 23H2** is included. Save changes.
- **Adjust Requirement Rules**:
For device configuration profiles, go to
Intune admin center > Devices > Configuration profiles > [Profile Name] > Requirements. Remove or modify rules that exclude Windows 11 23H2 (e.g., OS version checks).
- **Correct Registry Key Values**:
Use PowerShell to set the correct registry key:
Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Intune\PlatformFilter" -Name "OSVersion" -Value "22000".
Editing registry keys can break enrollment if incorrect. Always test in a lab environment first.
- **Force Policy Refresh**:
Run
Invoke-CimMethod -Namespace root/Microsoft/Windows/DesiredStateConfiguration -ClassName MSFT_DSCLocalConfigurationManager -MethodName SendMetaConfigurationApply -Arguments @{ConfigurationModeFrequencyMins = 4} to trigger a policy refresh.
Error Code Variants
| Error Code | Component | Scenario | Distinguishing Factor |
0x87D30068 | Intune Management Extension | Platform filter/requirement rule mismatch | Logged when device is excluded by policy rules. |
0x87D30067 | Intune Agent | App not applicable due to user filter | Occurs when user-based assignment filters exclude the device. |
0x87D30069 | Win32 App Installer | Installation failure due to missing dependencies | Logged when the app fails to install after passing filters. |
Verification
After applying fixes, verify resolution by:
1. Checking
IntuneManagementExtension.log for the line:
Win32 app [App Name] is applicable for device - platform filter/requirement rule matched.
2. Confirming in the Intune portal under
Intune admin center > Apps > Win32 apps > [App Name] > Devices that the device appears in the "Success" state.
3. Using PowerShell to query deployment status:
Get-IntuneWin32AppDeploymentStatus -AppId "12345-67890".
Prevention
To prevent recurrence:
- **Implement Baseline Policies**: Create a device configuration profile with OMA-URI
./Device/Vendor/MSFT/Intune/Win32App/DeploymentRules to enforce consistent platform filters across all Win32 apps.
- **Audit with PowerShell**: Use
Get-IntuneWin32App | ForEach-Object { Get-IntuneWin32AppAssignment -AppId $_.Id } to audit platform filters in bulk.
- **Test in Staging**: Deploy policies to a test group in
Intune admin center > Groups > [Staging Group] > Assignments before rolling out to production.
Use Get-IntuneDeviceConfigurationPolicy | Where-Object { $_.requirementRules } to quickly identify profiles with requirement rules that may need updates.