Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | 0x87D13B72 - Win32 app assignment conflict | Azure Portal - Device Health Overview logs | -> Indicates conflicting assignment intents |
| Affected OS build range | Windows 11 23H2 | Microsoft Intune documentation | -> Confirmed in this specific build |
| Registry key involved | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IntuneManagementExtension\Device\Windows\AssignedApps | Local device registry | -> Contains conflicting app assignments |
| Relevant service/endpoint URL | https://graph.microsoft.com/v1.0/deviceManagement/assignedApps | Microsoft Graph API documentation | -> Use to list assigned apps and policies |
| Log line signature | Win32AppAssignmentConflictDetected | Event Viewer - App Management logs | -> Log entry indicating the conflict |
Log Files to Check
C:\Windows\System32\winevt\Logs\Microsoft-IntuneManagementExtension-AppManagement.evtxC:\ProgramData\Microsoft\IntuneManagementExtension\Logs\DeviceHealth.log
What This Error Actually Means
The error code
0x87D13B72 indicates a Win32 application assignment conflict within Microsoft Intune. Specifically, this error occurs when multiple assignment intents (e.g., required vs. available vs. uninstall) for the same Win32 application are conflicting on a managed device. This results in an undefined installation state, causing instability or failure in app management operations. The error is raised by the
Intune Management Extension (IME), which handles device and application management tasks.
Affected Versions and Scope
This issue affects devices running **Windows 11 23H2** exclusively, as documented by Microsoft Intune. It does not impact earlier versions of Windows 10 or Windows 11. The problem arises in environments where multiple Win32 applications with overlapping assignment policies are deployed through Intune. Tenants using Azure AD with hybrid configurations (on-premises and cloud) may experience this issue more frequently due to synchronization delays.
Where To Look First: Logs and Event IDs
To diagnose this error, examine the following logs:
C:\Windows\System32\winevt\Logs\Microsoft-IntuneManagementExtension-AppManagement.evtx
and
C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\DeviceHealth.log
Search for the log line signature:
Win32AppAssignmentConflictDetected
Relevant Event IDs to look for:
-
Event ID 1005: Indicates a conflict between assignment intents.
-
Event ID 1006: Logs the specific conflicting application and its conflicting policies.
Use PowerShell to extract relevant logs:
Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 | Where-Object { $_.Id -eq 1005 }
Root Causes
1. Conflicting Assignment Policies
This occurs when multiple Intune policies assign the same Win32 application with conflicting intents (e.g., one policy requires installation while another marks it as available or specifies uninstallation). This creates ambiguity in the device's management state.
2. Duplicate Application Assignments
If an application is assigned to a device through multiple groups or policies, conflicts arise due to overlapping directives. For example, assigning the same app via both user and device scopes can cause this issue.
3. Inconsistent Uninstall Policies
Conflicts may occur if one policy requires installation while another mandates uninstallation of the same application. This creates a paradoxical state where Intune cannot determine the correct action.
4. Corrupted Intune Management Extension State
In some cases, the local registry or cache maintained by IME becomes corrupted, leading to incorrect assignment states being reported. This can happen due to improper shutdowns or system crashes during app management operations.
Fix Procedure
- Identify Conflicting Policies:
Navigate to the Intune admin center and review all policies affecting the problematic application:
Intune admin center > Apps > All apps > [Your Win32 App] > Assignments
Use PowerShell to retrieve conflicting assignment intents:
Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'"
- Resolve Policy Conflicts:
Modify or remove conflicting policies. Ensure that each application has a single, consistent assignment intent across all applicable groups.
- Inspect the Registry:
Check for conflicting entries in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IntuneManagementExtension\Device\Windows\AssignedApps
Use PowerShell to query the registry:
Get-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\IntuneManagementExtension\Device\Windows\AssignedApps
- Clear IME Cache:
If conflicts persist, reset the Intune Management Extension by clearing its cache. Use the following PowerShell cmdlet:
Invoke-MgGraphRequest -Method POST -Uri "https://graph.microsoft.com/v1.0/deviceManagement/managedDevices/{deviceId}/wipe"
- Re-enroll the Device:
As a last resort, re-enroll the device in Intune to rebuild its management state. This can be done via:
Intune admin center > Devices > All devices > [Device Name] > Re-enroll
Warning: Resetting IME or re-enrolling a device will temporarily disrupt other managed configurations. Ensure all critical policies are backed up before proceeding.
- Monitor Post-Fix State:
Verify that the conflict has been resolved by checking the DeviceHealth.log file:
Get-Content -Path C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\DeviceHealth.log | Select-String -Pattern "Win32AppAssignmentConflictDetected"
Error Code Variants
| Error Code | Description |
| 0x87D13B72 | Win32 app assignment conflict (this error) |
| 0x87D13B73 | Win32 app installation failed due to missing dependencies |
| 0x87D13B74 | Win32 app uninstallation conflict |
Verification
After applying fixes, verify success by:
1. Checking DeviceHealth.log for absence of the error signature:
Get-Content -Path C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\DeviceHealth.log | Select-String -Pattern "Win32AppAssignmentConflictDetected"
2. Ensuring all conflicting policies are resolved in the Intune admin center.
3. Confirming that the application's installation state is consistent across devices via:
Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'"
Prevention
To avoid recurrence:
1. Implement strict policy naming conventions to prevent accidental duplication.
2. Use PowerShell scripts to automate conflict detection:
Invoke-MgGraphRequest -Method GET -Uri "https://graph.microsoft.com/v1.0/deviceManagement/assignedApps"
3. Regularly audit application assignments via the Intune admin center and ensure that each app has a single, unambiguous assignment intent.
Tip: Use dsregcmd /status to quickly verify device enrollment status before making changes.
By following this guide, you can effectively diagnose, resolve, and prevent the
0x87D13B72 error in Microsoft Intune.