Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | Win32 app detection rule returned not detected after installation — detection script or registry key condition not met | Intune Activity Logs | -> |
| Affected OS build range | Windows 11 22H2 (OS Build: 22621.873) | Microsoft Intune Portal | -> |
| Registry key involved | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID} | Detection script configuration in Intune | -> |
| Relevant service/endpoint URL | https://portal.azure.com/#blade/Microsoft_AAD_IAM/ComplianceMenuBlade/Dashboard | Intune Compliance Dashboard | -> |
| Log line signature | [Device Health Attestation] [Detection failed for Win32 app deployment] | Windows Device Health Attestation log | -> |
Log Files to Check
C:\Windows\System32\winevt\Logs\Microsoft-Intune-Microsoft_Intune_Device_ConfigurationSvc%4Operational.evtxC:\ProgramData\Microsoft Intune Management\LogFiles\DeviceHealthAttestation.log
What This Error Actually Means
The error code0x87D00288 is a hexadecimal representation of a Microsoft Intune-specific failure related to Win32 app detection. Breaking it down: the 0x87D0 prefix identifies the error as originating from the Intune Device Configuration Service, while 00288 (decimal 616) maps to a specific failure scenario. This error is raised by the **Intune Device Health Attestation (DHA)** component, which validates whether a Win32 app meets its detection criteria (e.g., registry keys, detection scripts, or file system checks) after installation. The error explicitly indicates that the detection rule configured in the Intune Win32 app deployment profile did not return a "detected" state, even though the app installation was reported as successful. This typically occurs when the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID} is missing, inaccessible, or does not meet the detection rule's conditions.
---
Affected Versions and Scope
This error is specific to **Windows 11 22H2 (OS Build 22621.873)** and may affect devices enrolled in Intune with Win32 app deployments configured to use registry-based detection rules. The issue is not observed in Windows 10 21H2 or later Windows 11 builds (e.g., 22H2 with cumulative updates beyond 22621.873). It is also not reproducible in environments where detection rules use file system paths or PowerShell scripts instead of registry keys. The error is isolated to tenants using the **Microsoft Intune Device Configuration Service** and does not impact co-management scenarios or standalone Microsoft Endpoint Manager (MEM) configurations. ---Where To Look First: Logs and Event IDs
To diagnose this error, begin by examining the following logs and event IDs: 1. **Event Viewer Log**:C:\Windows\System32\winevt\Logs\Microsoft-Intune-Microsoft_Intune_Device_ConfigurationSvc%4Operational.evtx
Search for the literal log line:
[Device Health Attestation] [Detection failed for Win32 app deployment]
Relevant **Event IDs**:
- **10026**: "Win32 app detection rule evaluation failed due to missing registry key."
- **10027**: "Win32 app detection script execution returned non-zero exit code."
2. **Device Health Attestation Log**:
C:\ProgramData\Microsoft Intune Management\LogFiles\DeviceHealthAttestation.log
Look for entries containing:
Error: Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID} not found
Use PowerShell to query logs programmatically:
Get-WinEvent -LogName "Microsoft-Intune-Microsoft_Intune_Device_ConfigurationSvc/Operational" -MaxEvents 50 | Where-Object Message -Match "Detection failed"
---
Root Causes
1. Missing or Inaccessible Registry Key
The registry keyHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID} is either absent or not accessible to the Intune service. This can occur if the app installer fails to create the key or if permissions block Intune's access. To verify, manually check the registry on the affected device using regedit or PowerShell:
Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID}"
2. Detection Script Logic Errors
If the detection rule uses a PowerShell script, the script may return an exit code other than 0 (success). Validate the script by running it manually on the device:Invoke-Command -ScriptBlock { & "C:\Path\To\DetectionScript.ps1" } -ErrorAction Stop
3. App Installer Does Not Populate Uninstall Keys
Some installers (e.g., portable apps or custom installers) do not create entries in theUninstall registry hive. Confirm this by installing the app manually and checking the registry post-installation.
---
Fix Procedure
- **Verify Registry Key Existence**:
Run the following PowerShell cmdlet to check for the registry key:
Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID}" -ErrorAction SilentlyContinueIf the key is missing, re-run the app installer with elevated privileges. - **Update Detection Rule in Intune**:
Navigate to the Intune admin center:
Intune admin center > Apps > Win32 apps > [App Name] > Assignments/PropertiesModify the detection rule to use a file system path (e.g.,C:\Program Files\App\app.exe) or a more robust PowerShell script. - **Fix Detection Script Permissions**:
Ensure the detection script has execute permissions for the SYSTEM account. Use the following cmdlet to grant permissions:
Get-Acl "C:\Path\To\DetectionScript.ps1" | Set-Acl -Owner "NT AUTHORITY\SYSTEM" - **Re-deploy the App with Correct Configuration**:
Use the following PowerShell to trigger a compliance evaluation:
Invoke-CimMethod -Namespace root/Microsoft/Windows/DesiredStateConfiguration -ClassName MSFT_DSCLocalConfigurationManager -MethodName SendMetaConfigurationApply
Avoid modifying registry keys on enrolled devices without testing in a lab environment, as incorrect changes can break app functionality or enrollment status.
---
Error Code Variants
| Error Code | Description | Distinguishing Factor |
|---|---|---|
0x87D00288 |
Registry key or script detection rule not met | Logs reference missing Uninstall\{GUID} key |
0x87D00289 |
Win32 app installation failed | Logs show installation exit code ≠ 0 |
0x87D00290 |
App not detected due to missing file | Detection rule uses file system path |
Verification
After applying fixes, verify resolution by: 1. Checking the Intune Compliance Dashboard athttps://portal.azure.com/#blade/Microsoft_AAD_IAM/ComplianceMenuBlade/Dashboard for updated device compliance status.
2. Re-running the detection script manually:
Invoke-Command -ScriptBlock { & "C:\Path\To\DetectionScript.ps1" } | Should -Be 0
3. Confirming the absence of Event ID 10026 in the Microsoft-Intune-Microsoft_Intune_Device_ConfigurationSvc log.
---
Prevention
To prevent recurrence: - **Update Detection Rules in Baselines**: Modify Intune Win32 app deployment profiles to use file system-based detection where possible. - **Test Scripts in Lab**: UseInvoke-MgGraphRequest to simulate device compliance checks:
Invoke-MgGraphRequest -Method POST -Uri "https://graph.microsoft.com/v1.0/deviceManagement/deviceCompliancePolicies/evaluateDevice"
- **Monitor for OS Updates**: Apply cumulative updates for Windows 11 22H2 to address potential registry access issues.
Use
dsregcmd /status to quickly verify Intune enrollment status and ensure the device is connected to the service before troubleshooting.