Home › Microsoft Configuration Manager › 0x87D00324

Microsoft Configuration Manager · 0x87D00324 · Windows 11 23H2

Microsoft Configuration Manager Error 0x87D00324 on Windows 11 23H2 - Application Detection Failure

The root cause is a detection rule mismatch where the application's installation does not meet the defined criteria. The fix involves updating the detection rule to accurately reflect the installed application's properties.

Error Details

FactValueSourceNote
Exact error stringApplication not detected after installation completed — detection rule mismatchConfiguration Manager logs (SMSCore.log)-> Indicates the application installation failed validation.
Affected OS build rangeWindows 11 23H2Microsoft Configuration Manager documentation-> Confirmed on this specific OS version.
Registry key involvedHKLM\Software\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStoreConfiguration Manager logs (SMSCore.log)-> Detection rule may reference incorrect registry path.
Relevant service/endpoint URLhttps://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/hierarchy/log-filesMicrosoft Learn documentation-> Reference for log file analysis.
Log line signatureDetection rule mismatch detected for application [AppID]Configuration Manager logs (SMSCore.log)-> Identifies the specific application causing the issue.

Log Files to Check

What This Error Actually Means

The error code 0x87D00324 translates to a decimal value of 228171172 and is raised by the **Application Deployment** component in Microsoft Configuration Manager (SCCM). This error indicates a **detection rule mismatch** after an application installation completes. Specifically, the system installed the application, but the detection method configured in the SCCM application package (e.g., registry key, file, or Windows Installer product code) does not match the actual state of the installed application. This mismatch triggers a failure in the deployment status, marking the application as "not installed" despite the installation process completing. The root issue lies in the detection logic defined in the SCCM application’s deployment type. For example, if the detection rule checks for a registry key under HKLM\Software\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore to confirm installation, but the application writes its presence elsewhere (e.g., HKCU), the mismatch occurs. This error is distinct from installation failures and focuses solely on post-installation validation.

Affected Versions and Scope

This error is explicitly observed on **Windows 11 23H2** (OS build 22621.x or 22623.x). It affects SCCM clients running **version 2210 or later**, particularly when deploying applications that rely on **Appx package detection** or registry-based detection rules. The issue is **not reproducible** on Windows 10 or Windows 11 22H2 due to differences in how Appx package metadata is stored in the registry. Tenants using **Appx-based applications** (e.g., MSIX, UWP apps) or applications that modify the AppxAllUserStore registry hive are at higher risk. The problem is also more likely when detection rules are manually configured without validating against the actual installation behavior on 23H2.

Where To Look First: Logs and Event IDs

The primary log to investigate is C:\Program Files (x86)\Microsoft Configuration Manager\Logs\SMSCore.log. Search for the exact line: Detection rule mismatch detected for application [AppID] This line confirms the detection rule mismatch and includes the application’s unique identifier. Secondary logs include AppEnforce.log, which details the enforcement of application policies. Use Get-WinEvent to filter relevant events: Get-WinEvent -LogName "Microsoft-SMS-Operations" -MaxEvents 50 | Where-Object { $_.Id -eq 10016 -or $_.Id -eq 10017 } Event IDs **10016** (application installation started) and **10017** (installation completed) provide timestamps to correlate with the detection failure.

Root Causes

1. Incorrect Detection Method Configuration

The detection rule may reference a registry key, file, or product code that does not align with the application’s actual installation artifacts. For example, an Appx app might register under AppxAllUserStore, but the detection rule checks HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall.

2. Appx Package Metadata Changes in 23H2

Windows 11 23H2 modifies how Appx package metadata is stored. If the detection rule relies on legacy registry keys (e.g., HKLM\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\PackageRepository), it may fail to detect the application.

3. Permission Restrictions on AppxAllUserStore

The AppxAllUserStore registry key may have restricted permissions, preventing SCCM from reading its contents. This is common in multi-tenant environments or when using group policies that enforce strict registry access controls.

How to Differentiate Causes

- **Registry Key Mismatch**: Use Get-ItemProperty -Path "HKLM:\Software\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore" to verify if the expected Appx package is listed. - **Appx Metadata Changes**: Compare registry entries between 22H2 and 23H2 using Compare-Object in PowerShell. - **Permission Issues**: Run Get-Acl -Path "HKLM:\Software\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore" to check permissions.

Fix Procedure

  1. **Update Detection Rule**: In the SCCM console, navigate to Software Library > Applications > [AppID] > Deployment Types. Edit the detection method to match the actual installation artifacts. For Appx apps, ensure the detection rule checks AppxAllUserStore.
  2. **Verify Registry Permissions**:
    Warning: Modifying permissions on system registry keys can break enrolled devices. Test in a lab environment first.
    Use Set-Acl to grant SCCM service account read access: Set-Acl -Path "HKLM:\Software\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore" -AclObject $acl
  3. **Use PowerShell to Validate Detection**: Get-CMDetectionMethod -ApplicationName "AppDisplayName" | Select-Object DetectionMethod, DetectionScript If the detection script is outdated, update it using Set-CMDetectionMethod.
  4. **Redeploy Application**: Force re-evaluation with: Invoke-CMApplicationDeployment -ApplicationName "AppDisplayName" -CollectionName "All Systems"

Error Code Variants

Error Code Description Distinguishing Factor
0x87D00324 Detection rule mismatch Post-installation validation fails due to mismatched detection logic
0x87D00325 Installation failure Installation process itself fails (e.g., script errors, missing dependencies)
0x87D00326 Uninstallation failure Detected during uninstallation, not installation

Verification

After applying fixes, monitor SMSCore.log for the line: Application detected successfully using detection method [MethodID] In the Intune admin center, navigate to Devices > Windows > Apps > [AppDisplayName] to confirm deployment status shows "Success." Additionally, run: Get-CMApplicationDeploymentStatus -ApplicationName "AppDisplayName" A Status value of Success confirms resolution.

Prevention

To prevent recurrence: 1. **Enforce Detection Rule Validation**: Use a baseline policy to audit detection methods against actual installation artifacts. Example: New-CMBaseline -Name "AppDetectionValidation" -RuleScript "Test-DetectionRule.ps1" 2. **Standardize Detection Logic**: For Appx apps, always reference AppxAllUserStore in detection rules. 3. **Automate Testing**: Integrate PowerShell scripts into your CI/CD pipeline to validate detection rules before deployment:
Tip: Use Invoke-Command to remotely test detection scripts on 23H2 devices without manual login.
Example: Invoke-Command -ComputerName "TestDevice" -ScriptBlock { Get-ItemProperty -Path "HKLM:\Software\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore" } By addressing detection logic proactively and aligning it with OS-specific behaviors, administrators can avoid this error in future deployments.

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.