Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | Win32 app installation failed — dependency application not installed or wrong architecture | Intune Management Activity Log | -> |
| Affected OS build range | Windows 11 22H2 (OS Build: 22621.755) | Microsoft Intune Portal | -> |
| Registry key involved | HKLM\Software\Microsoft\Windows\CurrentVersion\Appx\PackageRepository\MachineState | Windows Registry Editor | -> |
| Relevant service/endpoint URL | https://graph.microsoft.com/v1.0/deviceManagement/appConfigurations | Microsoft Graph API Documentation | -> |
| Log line signature | [Error] [AppDeployment] Failed to install application due to dependency issue. | Intune Management Activity Log | -> |
Log Files to Check
%ProgramData%\Microsoft\IntuneManagement\Logs\ApplicationDeployment.logC:\Windows\System32\LogFiles\WMI\Activity\*.blg
What This Error Actually Means
The error code
0x87D00607 is raised by the **Microsoft Intune App Deployment Agent** during Win32 application installation. This hexadecimal value translates to a specific failure condition in the Intune agent's dependency resolution logic. The error explicitly indicates that the deployment process failed because a required dependency application is either **not installed** on the target device or the **architecture mismatch** (e.g., 32-bit app attempting to install on a 64-bit OS). The root component responsible for this error is the **App Deployment Agent**, which validates dependencies before proceeding with the installation. This error is distinct from generic installation failures, as it directly ties to dependency resolution logic within the Intune agent's execution pipeline.
Affected Versions and Scope
This error is observed in **Windows 11 22H2** with the exact OS build
22621.755. It affects tenants where Win32 applications are deployed with explicit dependencies on other applications (e.g., .NET Runtime, Visual C++ Redistributable, or custom prerequisites). The issue is **not present** in Windows 11 23H2 or newer builds due to improvements in dependency resolution logic in the OS. Additionally, tenants using **App-V virtualized applications** or **MSIX packages** are unaffected, as these formats do not rely on the same dependency validation mechanism. The error is more prevalent in environments where applications are deployed via **Intune Win32 app packages** with manually defined dependencies in the Intune portal.
Where To Look First: Logs and Event IDs
The primary log to investigate is
%ProgramData%\Microsoft\IntuneManagement\Logs\ApplicationDeployment.log, which contains detailed error messages about the deployment failure. Use the following PowerShell command to filter the log:
Get-Content -Path "$env:ProgramData\Microsoft\IntuneManagement\Logs\ApplicationDeployment.log" | Select-String "Failed to install application due to dependency issue"
The exact log line signature is:
[Error] [AppDeployment] Failed to install application due to dependency issue.
Additionally, check the **Windows Event Viewer** under
Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider > Admin for **Event ID 1001** (dependency validation failure) or **Event ID 1002** (architecture mismatch). For advanced analysis, use the Windows Performance Recorder (WPR) logs at
C:\Windows\System32\LogFiles\WMI\Activity\*.blg to trace WMI activity during deployment.
Root Causes
1. Missing Dependency Application
The target device lacks a prerequisite application explicitly defined in the Intune Win32 app's deployment configuration. This is confirmed by inspecting the
MachineState registry key at
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Appx\PackageRepository\MachineState for missing entries corresponding to the dependency.
2. Architecture Mismatch
The deployed Win32 app specifies a dependency on an application with a different architecture (e.g., 32-bit dependency on a 64-bit OS). This is identifiable by checking the
Architecture field in the Intune app manifest and cross-referencing it with the installed dependency's architecture via
Get-ItemProperty -Path "HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*".
3. Corrupted Registry State
The
MachineState registry key contains invalid or outdated entries, preventing the Intune agent from correctly resolving dependencies. This is diagnosed by comparing the registry entries with the actual installed applications using
Get-WmiObject -Class Win32_Product.
Fix Procedure
- **Verify Dependency Installation**:
Use
Get-MgDeviceManagementApplicationConfiguration -Filter "id eq 'APP_CONFIGURATION_ID'" to confirm the dependency app is deployed. If missing, deploy it via Intune admin center > Apps > Win32 apps > [App Name] > Assignments.
- **Check Architecture Compatibility**:
Run
Get-ItemProperty -Path "HKLM:\Software\Microsoft\Windows\CurrentVersion\Appx\PackageRepository\MachineState" | Select-Object -ExpandProperty "Architecture" to validate the target app's architecture matches the dependency.
- **Correct Registry State**:
Manually edit
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Appx\PackageRepository\MachineState to remove invalid entries. Editing this key can break enrollment if incorrect values are modified. Always back up the registry before changes.
- **Use PowerShell to Force Re-evaluation**:
Run
Invoke-MgGraphRequest -Method POST -Uri "https://graph.microsoft.com/v1.0/deviceManagement/managedDevices/REPLACE_DEVICE_ID/refreshDevice" to trigger a policy refresh.
- **OMA-URI for Dependency Enforcement**:
Deploy a configuration profile with OMA-URI
./Device/Vendor/MSFT/Policy/Config/Windows/1.0/DependencyCheck to enforce dependency validation at login.
Error Code Variants
| Error Code | Description | Distinguishing Factor |
0x87D00607 | Dependency missing or architecture mismatch | Logs explicitly mention "dependency issue" |
0x87D00608 | License validation failure | Occurs with volume-licensed applications |
0x87D00609 | Installation blocked by policy | Linked to device compliance policies |
Verification
After applying fixes, verify success by checking
ApplicationDeployment.log for the line:
[Info] [AppDeployment] Application installed successfully with all dependencies resolved.
In the Intune admin center > Devices > Windows > All devices, confirm the device shows a "Success" status under the relevant app deployment. Additionally, run
Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" | Where-Object { $_.Id -eq 1003 } to confirm no residual errors.
Prevention
To prevent recurrence, implement a **baseline configuration policy** in Intune admin center > Device configuration > Baselines to ensure all dependency applications are pre-installed. Use PowerShell
Set-MgDeviceManagementDeviceConfigurationPolicy -Id "BASELINE_ID" -Description "Enforce dependency apps" to automate this. Additionally, enforce architecture checks during app packaging by validating the
Architecture field in the Win32 app manifest.
Use Get-WinEvent -LogName "Application" -MaxEvents 100 | Select-String "dependency" to quickly identify recurring issues.