Home › Microsoft Intune › 0x87D1FDE7

Microsoft Intune · 0x87D1FDE7 · Windows 11 23H2

Intune Win32 app install fails with 0x87D1FDE7 on Windows 11 23H2

The installation exceeds timeout due to missing silent switch or mid-install reboot; fix by reviewing logs, updating detection rule and extending time limit.

Error Details

FactValueSourceNote
Exact error stringINSTALL_ERROR_TIMEOUT (0x87D1FDE7)Intune Management Extension log file
Affected OS build rangeWindows 11 23H2
Registry key involvedHKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{ProductCode}Detection rule configuration-> for correct detection
Relevant service/endpoint URLhttps://graph.microsoft.com/v1.0/deviceManagement/intents/{appId}/logs
Log line signature[AppID] - Installation failed with error code 0x87D1FDE7IntuneManagementExtension.log

Log Files to Check

What This Error Actually Means

The error code 0x87D1FDE7, which translates to INSTALL_ERROR_TIMEOUT within Microsoft Intune's context, is raised when the Windows Management Framework (WMF) fails to detect a successful installation of an application due to exceeding the maximum detection timeout. The Intune Management Extension component is responsible for monitoring and reporting this error during app deployment processes on managed devices. This specific error occurs because the installation process did not complete within the expected timeframe, which typically is set at 60 minutes by default. This can be caused by various factors such as missing silent switches in the installer command, unexpected reboots required mid-installation, or incorrect detection rules that fail to confirm a successful install.

Affected Versions and Scope

This error primarily affects devices running Windows 11 build 23H2. It is observed across different tenant configurations where Win32 application deployments are managed through Microsoft Intune. The issue does not typically affect older versions of Windows or other operating systems, such as macOS or Linux, which may use alternative management tools and have distinct error codes for similar issues.

Where To Look First: Logs and Event IDs

To diagnose this problem effectively, you should first consult the following log files: The Intune Management Extension log file is crucial as it contains detailed information about the installation process, including error codes and timestamps. Look for lines that match the pattern [AppID] - Installation failed with error code 0x87D1FDE7. Additionally, you can use Event Viewer to search for specific event IDs related to Intune management:

Root Causes

There are several distinct causes that can lead to this error. Each cause has unique characteristics and diagnostic steps.

Missing Silent Switch in Installer Command

If the installer command lacks necessary silent switches, such as /quiet /norestart, it may display UI elements which prevent Intune from detecting a successful installation within the timeout period. To identify this issue, review the install command used for the Win32 app deployment and ensure that all required parameters are included.

Reboot Required During Installation

If an installer requires a reboot mid-installation, it can cause the detection rule to fail due to the extended installation time. This often results in the error code 0x87D1FDE7 being logged by Intune Management Extension. To diagnose this issue, check for any messages indicating that a reboot is required within the setupapi.dev.log file.

Incorrect Detection Rule Configuration

An incorrectly configured detection rule can lead to false negatives where the installation appears incomplete even though it has been successful. This might happen if the detection script returns incorrect exit codes or checks for non-existent registry keys or files. Review the detection rules in Intune and ensure they accurately reflect the state of a successfully installed application.

Fix Procedure

To resolve this issue, follow these steps:
  1. Review the install command to ensure it includes /quiet /norestart. Modify the command if necessary.

  2. Modify the detection rule in Intune admin center > Apps > Win32 apps. Ensure that the detection method checks for a registry key at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{ProductCode} or verifies file versions.
  3. Extend the installation time limit in Intune admin center > Apps > Win32 apps. Increase the timeout to 120 minutes if the application legitimately requires a longer deployment period.

    To verify the current configuration, use PowerShell:

    (Get-MgDeviceAppManagementWin32LobApp -Filter "id eq '{appId}'").InstallTimeLimit

    Update the time limit using:

    $app = Get-MgDeviceAppManagementWin32LobApp -Filter "id eq '{appId}'"
    $app.InstallTimeLimit = New-TimeSpan -Minutes 120
    Set-MgDeviceAppManagementWin32LobApp -Id $app.Id -BodyParameter $app
  4. Monitor the Intune Management Extension log for successful installation events. Use PowerShell to check:

    $log = Get-Content "C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log"
    $log | Select-String -Pattern "[AppID] - Installation succeeded with exit code 0"
  5. Use the following OMA-URI to configure device settings that may impact installation times: ./Device/Vendor/MSFT/Setup/InstallTimeout.

Error Code Variants

Error CodeDescriptionDistinguishing Features
0x87D1FDE6 (INSTALL_ERROR_INSTALLER_FAILURE)The installer failed to complete the installation.This error occurs when there is a failure in the installer itself, not due to time constraints. Check for specific errors or messages from the installer.
0x87D1FDE5 (INSTALL_ERROR_DETECTION_FAILURE)The detection rule failed to confirm installation success.This error is related to incorrect configuration of detection rules rather than a timeout issue. Ensure that detection scripts return correct exit codes and check for the presence of expected registry keys or files.

Verification

After applying the fixes, verify that the installation process completes successfully within the extended time limit. Check the Intune Management Extension log file for successful installation events with an exit code of 0 and no timeout errors. You can also use PowerShell to query the status of managed devices:
$device = Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'"
$apps = $device | Get-MgDeviceAppManagementWin32LobAppInstallStatus
$apps | Where-Object { $_.InstallationState -eq 1 }
This command will list all installed Win32 apps and their current installation state, confirming that the deployment was successful.

Prevention

To prevent recurrence of this issue, implement a baseline policy for all Win32 app deployments: Regularly review and update these settings based on feedback from end-users or IT support teams. This proactive approach will help maintain a smooth and reliable application deployment process across your organization's managed devices.

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.