Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | 0x87D13B13 | IntuneManagementExtension.log | -> |
| Affected OS build range | Windows 11 23H2 | OS version | |
| Registry key involved | HKLM\SOFTWARE\Microsoft\IntuneManagementExtension\Logs | Registry Editor | -> |
| Relevant service/endpoint URL | https://graph.microsoft.com/v1.0/deviceAppManagement/mobileApps | API Endpoint | |
| Log line signature | Supersedence relationship broken because superseded app not detected or detection rule failure. | IntuneManagementExtension.log | -> |
Log Files to Check
IntuneManagementExtension\Logs\IntuneManagementExtension.logC:\Windows\System32\winevt\Logs\Microsoft-Windows-IntuneManagementExtension%4Operational.evtx
What This Error Actually Means
The error code 0x87D13B13 is raised by Microsoft Intune's Win32 app management feature when a supersedence relationship between two applications fails to establish properly. Specifically, this occurs when the superseded application cannot be detected on a device or its detection rules fail, preventing the intended replacement of an older version with a newer one. This error disrupts the seamless update process for managed software and can lead to inconsistencies in the deployment status across devices.Affected Versions and Scope
This issue is observed exclusively on Windows 11 build 23H2, affecting configurations where Win32 application supersedence policies are actively enforced. It does not impact earlier or later versions of Windows 11 or other operating systems like Windows 10. The problem can occur in any tenant configuration that uses Intune for managing software updates and version control but is particularly noticeable when strict update policies are applied.Where To Look First: Logs and Event IDs
To diagnose this issue, start by examining the following logs: -C:\Windows\System32\winevt\Logs\Microsoft-Windows-IntuneManagementExtension%4Operational.evtx
- C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log
The critical log entries will contain the exact error string: "Supersedence relationship broken because superseded app not detected or detection rule failure." Additionally, Event ID 1024 (which is part of the Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin event log) can provide context around the time and nature of the supersedence failure.
Root Causes
Detection Rule Failure
Detection rules define how Intune identifies whether a superseded application is present on a device. If these rules are incorrectly configured or if there's an issue with the detection method (e.g., file path, registry key), the supersedence process will fail.
Application Not Installed
If the superseded app was never installed on the target devices in the first place, Intune cannot establish a supersedence relationship. This often happens if deployment policies were changed or if there's an issue with the initial installation script.
Incompatible Detection Method
Sometimes, the detection method specified for the superseded application may not be compatible with the version of Windows 11 build 23H2. For instance, a detection rule that relies on a registry key present in earlier versions might fail if that key is absent or different.
Fix Procedure
To resolve this issue, follow these steps:
- Review Detection Rules: Use the
Get-IntuneWin32App -Filter "detectedBy eq 'detectionRule'" | Select-Object displayName,detectionRules cmdlet to list all Win32 apps with detection rules. Examine each rule for correctness and compatibility.
- If a detection rule is incorrect, update it via the Intune admin center > Apps > Win32 > [Your App] > Detection Rules tab.
- Check Application Installation Status: Use
Get-IntuneWin32App -Filter "isSuperseded eq 'true'" | Select-Object displayName,isInstalled to verify if the superseded application is installed on devices. If not, ensure proper installation policies are in place.
- Use
Get-WinEvent -LogName Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin -MaxEvents 50 to quickly find recent events related to Win32 app management.
- Adjust Detection Methods: If the detection method is incompatible, modify it using
Set-IntuneWin32AppDetectionRule -Id [Your Rule ID] -DetectionType [New Type].
Error Code Variants
Get-IntuneWin32App -Filter "detectedBy eq 'detectionRule'" | Select-Object displayName,detectionRules cmdlet to list all Win32 apps with detection rules. Examine each rule for correctness and compatibility.If a detection rule is incorrect, update it via the Intune admin center > Apps > Win32 > [Your App] > Detection Rules tab.
Get-IntuneWin32App -Filter "isSuperseded eq 'true'" | Select-Object displayName,isInstalled to verify if the superseded application is installed on devices. If not, ensure proper installation policies are in place.Use
Get-WinEvent -LogName Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin -MaxEvents 50 to quickly find recent events related to Win32 app management.Set-IntuneWin32AppDetectionRule -Id [Your Rule ID] -DetectionType [New Type].| Error Code | Description |
|---|---|
| 0x87D13B14 | Supersedence relationship broken due to policy conflict. |
| 0x87D13B15 | Supersedence relationship broken because of a missing dependency. |
| 0x87D13B16 | Supersedence relationship broken due to incorrect versioning. |
Verification
After applying the fixes, verify that the issue is resolved by checking for the following: - The error code 0x87D13B13 no longer appears inC:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log.
- Event ID 1024 should now indicate successful supersedence operations.
- Use the Intune admin center > Apps > Win32 to confirm that the application's status reflects correct installation and versioning.