Home › Microsoft Intune › 0x87D01011

Microsoft Intune · 0x87D01011 · Microsoft Intune Win32 App

Intune Win32 App Error 0x87D01011: Dependency Not Installed

Error 0x87D01011 occurs when a prerequisite app fails or is missing. Fix by resolving the dependency's install error or verifying its detection rules.

Error Details

FactValueSourceNote
Exact Error Code0x87D01011Intune Admin Center / IME LogSYNCML_DM_TRANSIENT_PROCESSING_ERROR
Error DescriptionThe required Win32 app dependency is not installedIME Log ContextIndicates blocked installation due to missing prereq
Primary Log FileC:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.logFile SystemSearch for 'dependency not found' or error code
Secondary Log SourceWindows Application Event Log (MsiInstaller)Event ViewerShows specific failure of the prerequisite MSI package
Affected ComponentIntune Management Extension (IME)Service ArchitectureHandles Win32 app dependency resolution

Log Files to Check

What This Error Actually Means

The error code 0x87D01011, technically classified as SYNCML_DM_TRANSIENT_PROCESSING_ERROR, is a specific failure state within the Microsoft Intune Management Extension (IME) architecture. It does not indicate a corruption of the application payload itself, nor does it signify a network connectivity issue between the device and the Intune service. Instead, this code explicitly denotes that the dependency resolution logic has failed. When you configure a Win32 app in Intune with a dependency relationship (e.g., "App B requires App A"), the IME engine evaluates the presence of the prerequisite before attempting to install the dependent application. If the prerequisite is missing, fails its detection rule, or is currently in a failed state, the IME halts the installation of the dependent app and returns 0x87D01011. This is a protective mechanism designed to prevent partial installations that would likely result in broken software functionality. The component raising this error is the IntuneManagementExtension.exe process, which acts as the local agent for policy and app enforcement on Windows 10/11 devices.

Affected Versions and Scope

This error is strictly scoped to Win32 applications (MSI or EXE wrappers) deployed via Microsoft Intune. It does not affect Microsoft Store apps, Line-of-Business (LOB) apps, or Office 365 Click-to-Run deployments managed through other channels. The issue manifests on any Windows 10 or Windows 11 build that supports the modern management stack, provided the device is enrolled in Azure AD (Entra ID) and has a healthy Intune Management Extension service. It is most prevalent in environments utilizing complex dependency chains, such as deploying a specific version of Adobe Acrobat Reader which depends on a custom .NET Framework patch or a specific Visual C++ Redistributable. The error is not tenant-specific but is configuration-specific; it occurs regardless of the Windows build version (e.g., 21H2, 22H2, 23H2) as long as the dependency logic is invoked. It is critical to note that this error will not appear if you are using "Supersedence" rules instead of "Dependencies," as those are handled by a different evaluation engine within the IME.

Where To Look First: Logs and Event IDs

To diagnose 0x87D01011, you must inspect the local logs on the failing endpoint. The primary source of truth is the Intune Management Extension log file located at C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log. You should search this file for the literal string 0x87D01011 or the phrase dependency not found. The log entry will typically precede the error code with a message indicating which specific App ID failed the dependency check. For example, you might see: AppInstallHandler::ProcessDependencyFailure - Dependency app [AppID] is not installed.

Secondary diagnostic data resides in the Windows Event Log. Specifically, look at Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider > Admin. While this log does not always contain the hex code directly, it records the execution attempts of the prerequisite app. Look for Event ID 819, which indicates a policy processing start, and Event ID 12003, which often correlates with application installation failures. Additionally, if the dependency is an MSI package, check the Application log for Event ID 1033 from the source MsiInstaller, which will detail why the prerequisite itself failed to install or detect.

Root Causes

Prerequisite Detection Rule Misconfiguration

The most common cause is that the prerequisite app is actually installed, but its detection rule in Intune is incorrect. If the IME cannot verify the presence of the dependency via file path, registry key, or MSI product code, it assumes the app is missing. This results in 0x87D01011 for any app depending on it. You can distinguish this by manually checking if the prerequisite software is running on the device despite the error.

Assignment Scope Mismatch

The dependency app may not be assigned to the same group as the dependent app, or the user/device is not a member of the security group containing the prerequisite. Intune does not automatically install dependencies if they are not explicitly assigned to the target device. This is distinct from a download failure; it is a policy visibility issue.

Circular or Broken Dependency Chains

If App A depends on App B, and App B depends on App A, the IME will enter a deadlock state and eventually return transient errors. Alternatively, if the dependency app itself has a fatal installation error (e.g., exit code 1603), it will never reach a "Success" state, causing all downstream dependent apps to fail with 0x87D01011.

Fix Procedure

  1. Identify the Failed Dependency: Open C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log. Search for 0x87D01011. Note the AppId or DisplayName of the prerequisite listed in the error context.
  2. Verify Prerequisite Status: Navigate to Intune admin center > Apps > All apps. Select the identified dependency app. Go to Device install status and filter by the failing device. If the status is "Error," you must fix the prerequisite first.
  3. Test Detection Rule Manually: If the prerequisite shows as "Not Installed" but is present on the device, your detection rule is wrong. Use PowerShell to verify the rule. For example, if checking a registry key: Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion" -Name "ProductName" Ensure the value matches exactly what is configured in Intune.
  4. Force Re-evaluation: Once the prerequisite is fixed or confirmed installed, force the IME to re-check dependencies. You can trigger a sync via the portal: Intune admin center > Devices > All devices > Select Device > Synchronize. Alternatively, use PowerShell on the device to restart the service: Restart-Service -Name "IntuneManagementExtension" -Force
  5. Validate Assignment: Ensure the dependency app is assigned to the same group as the dependent app. Use Graph API to verify group membership if uncertain: Invoke-MgGraphRequest -Method GET -Uri "https://graph.microsoft.com/v1.0/groups/{groupId}/members"
Warning: Do not delete and recreate the dependency relationship in Intune while the app is in a "Pending" or "Installing" state on the device. This can corrupt the IME's internal state database, requiring a full re-enrollment of the device to resolve. Always wait for the status to settle to "Error" or "Success" before modifying dependency configurations.

Error Code Variants

Error Code Description Distinguishing Factor
0x87D01011 Dependency Not Installed Specifically fails because a prerequisite is missing or undetected. The app itself may be valid.
0x87D01026 App Install Failed The application payload itself failed to install (e.g., exit code != 0). No dependency issue involved.
0x87D00FFF General IME Error A generic failure often related to service crashes or policy parsing errors, not specific to dependencies.

Verification

To prove the fix worked, monitor the IntuneManagementExtension.log file again. You should see a new entry indicating that the dependency check passed: AppInstallHandler::ProcessDependencySuccess - Dependency app [AppID] is installed. Subsequently, the dependent app should transition from "Error" to "Installing" and finally to "Success." In the Intune Admin Center, under Apps > All apps > [Dependent App] > Device install status, the device status should update to "Success" within 1-2 hours. You can also verify via PowerShell by checking the installed applications list: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*App Name*"} (Note: Use CIM or registry queries for better performance in production, but WMI is acceptable for quick verification).

Prevention

To prevent recurrence, implement strict detection rule testing before deploying dependencies. Always use the "Test Detection Rule" feature in the Intune portal during app creation. Additionally, consider using Supersedence instead of dependencies where possible, as supersedence is more robust against version mismatches. For complex environments, deploy a baseline configuration that ensures common prerequisites (like .NET Frameworks) are installed via Group Policy or Configuration Profiles before deploying dependent Win32 apps. Finally, regularly audit your app assignments to ensure no orphaned dependencies exist. You can use the following OMA-URI to force a more aggressive sync cycle if needed, though this is generally not recommended for production: ./Device/Vendor/MSFT/Management/ForceSync

Pro Tip: Use the dsregcmd /status command on the device to verify that the device is properly joined to Entra ID and that the Intune management channel is active. If the "Mdm enrollment state" shows as disconnected, dependency checks will fail regardless of app configuration.

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.