Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | 0x87D00215 - Detection rule failed for application | Application Deployment Evaluation.log | Triggered during evaluation |
| Affected OS build | Windows 11 23H2 (22000.2189+) | OS Version | Build-specific detection rule issue |
| Registry key | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall | Detection Rule Configuration | Missing/unexpected registry entry |
| OMA-URI | ./Device/Vendor/MSFT/ConfigMgr/Client/Actions/ApplicationDeployment | Intune/SCCM Client Agent | Deployment action endpoint |
| Log line signature | Failed to evaluate detection rule for AppID: <GUID> | Application Deployment Evaluation.log | Correlate with error timestamp |
Log Files to Check
C:\Program Files\Microsoft Configuration Manager\Logs\Application Deployment Evaluation.logC:\Program Files\Microsoft Configuration Manager\Logs\Client ID Manager.log
What This Error Actually Means
The error code0x87D00215 is a hexadecimal representation of a failure in the **Application Deployment Evaluation** component of Microsoft Configuration Manager (SCCM). This error specifically indicates that the **detection rule** configured for an application could not validate the application's presence on the target device. The detection rule is a mechanism used by SCCM to determine whether an application is already installed, compliant, or requires remediation. When this rule fails, the application does not appear in the Software Center, and the deployment status remains unresolved. The error is raised by the **Application Deployment Agent**, which evaluates detection rules during the Application Deployment Evaluation phase. The root cause typically lies in misconfigured detection logic, missing registry entries, or application installation artifacts that do not align with the detection rule's criteria.
---
Affected Versions and Scope
This error affects **Windows 11 23H2 (OS build 22000.2189 and later)** deployments where SCCM or Intune-managed applications rely on registry-based detection rules. It is commonly observed in environments using **Microsoft Endpoint Manager (MEM)** hybrid configurations, where SCCM coexists with Intune via the Microsoft Graph API. The issue does **not** occur in standalone Intune deployments unless the detection rule explicitly references theHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall registry hive. Older OS builds (e.g., Windows 10 21H2) are less likely to exhibit this error due to differences in registry virtualization and application compatibility layers.
---
Where To Look First: Logs and Event IDs
The primary log to analyze isC:\Program Files\Microsoft Configuration Manager\Logs\Application Deployment Evaluation.log. Search for the exact line:
Failed to evaluate detection rule for AppID: <GUID>
This line confirms the detection rule failure. Cross-reference with C:\Program Files\Microsoft Configuration Manager\Logs\Client ID Manager.log to verify device enrollment status and client health.
Event IDs to monitor in the **Application** log:
- **Event ID 1001**: "Application deployment evaluation failed due to missing detection rule artifacts."
- **Event ID 1002**: "Registry key not found during detection rule evaluation."
Use PowerShell to parse logs:
Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" | Where-Object { $_.Message -match "0x87D00215" }
---
Root Causes
1. Incorrect Registry Key in Detection Rule
The detection rule may reference a registry key that does not exist (e.g.,HKEY_CURRENT_USER instead of HKEY_LOCAL_MACHINE). Verify the key path in the SCCM console under **Application > Deployment Types > Detection Rules**.
2. Missing Uninstall String in Registry
If the application installer does not write anUninstallString value to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, the detection rule fails. Use Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall" to inspect entries.
3. Application Not Installed or Corrupted
A failed installation or incomplete uninstallation can leave inconsistent state data. Check theInstallation log for the application (e.g., C:\Windows\Temp\<AppGUID>.log) for errors.
---
Fix Procedure
- **Verify Detection Rule Configuration**
Open the SCCM console, navigate to **Assets and Compliance > Applications**, select the affected app, and review the detection rule under **Deployment Types**. Ensure the registry key path matches
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall. - **Manually Validate Registry Entries**
Run
Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\<AppGUID>"to confirm the presence ofDisplayNameandUninstallString. - **Re-deploy the Application**
Use
Update-CMDistributionPoint -ApplicationName "<ApplicationName>"to refresh distribution points. Then trigger evaluation via OMA-URI:./Device/Vendor/MSFT/ConfigMgr/Client/Actions/ApplicationDeploymentusing theInvoke-CMClientActioncmdlet. - **Force Client Evaluation**
Execute
Start-CMClientEvaluation -Action ApplicationDeploymenton the affected device to re-evaluate detection rules.
Avoid modifying registry keys directly on enrolled devices without a backup. Incorrect changes can break enrollment and trigger
---
0x800704C4 errors in Intune.
Error Code Variants
| Error Code | Description | Distinguishing Factor |
|---|---|---|
0x87D00215 | Detection rule failed | Registry key or value missing |
0x87D00216 | Detection rule evaluation timeout | Long-running scripts or network delays |
0x87D00214 | Detection rule returned invalid data | Script output does not match expected format |
Verification
After applying fixes, checkApplication Deployment Evaluation.log for the line:
Successfully evaluated detection rule for AppID: <GUID>
In the SCCM console, navigate to **Monitoring > Deployments** and confirm the application status changes to **Success**. For Intune-managed devices, verify in the **Intune admin center > Apps > All apps** that the app appears in the device's installed list.
Use
---
dsregcmd /status to quickly validate device enrollment status before troubleshooting deeper issues.
Prevention
To prevent recurrence, enforce the following policies: 1. **Baseline Detection Rule Templates**: Use SCCM's built-in templates for registry-based detection rules to ensure consistency. 2. **Automated Testing**: Integrate PowerShell scripts likeTest-CMDetectionRule -ApplicationName "<App>" into CI/CD pipelines for application packaging.
3. **Intune Compliance Policies**: Create a policy under **Intune admin center > Devices > Configuration profiles** to audit registry keys in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall.
For hybrid environments, ensure the **Microsoft Graph API** permissions under **Entra ID > API Permissions** include DeviceManagementApps.ReadWrite.All to synchronize detection rule states between SCCM and Intune.