Deploying Win32 apps through Intune can sometimes throw unexpected errors that leave administrators puzzled. One common issue is error 0x87D300C9, which typically indicates that the installer failed to run silently or timed out during execution. In this guide, we’ll break down the root causes of this error, show you how to analyze logs, and walk through practical fixes—so you can get your apps deployed smoothly without wasted cycles.
Issue:
Intune Win32 app deployment failed with error code 0x87D300C9.
Error Code: 0x87D300C9
Error Description: The unmonitored process is in progress; it may timeout.
Intune – Win32 App – Error 0x87D300C9
Cause for Intune 0x87D300C9 Error
Error code 0x87D300C9 occurs when Intune detects that a process is still running after it has stopped monitoring the installation. This typically happens when the installer or script becomes stuck during execution.
For PowerShell scripts, the issue often arises when an unexpected message box appears, causing the script to hang indefinitely until manually closed
For applications, common causes include a corrupt installer, incorrect command‑line arguments, or missing silent install switches.
Step-by-Step Guide to Investigate Intune 0x87D300C9 Error
Validate command-line switches
Validate that the command‑line switches are correct, and then perform a manual installation using the same switches to confirm the application runs silently without any pop‑up messages.
Manually Install Application
Try installing the application manually with the same source file to verify that the process completes without hanging. If the problem appears only on certain devices, perform the manual installation on one of the affected machines to isolate the issue. Failures may stem from a corrupt source file or missing prerequisites such as the .NET Framework or other dependencies.
Check for Message Boxes in Scripts
A PowerShell script may hang indefinitely if it displays a message box during execution.
Fix: Remove or suppress any interactive elements, so the script runs in unattended mode.
Why it happens: Message boxes require user interaction, which prevents the script from completing silently.
How to verify: Run the script manually and ensure that no message boxes or prompts appear while it executes.
Check IntuneManagementExtension Log
The IntuneManagementExtension.log is the primary log file for troubleshooting Win32 app deployments in Intune.
Tip: Use a log viewer such as CMTrace to make the entries easier to read and quickly identify error codes or failure points.
Purpose: It records every step Intune takes during deployment—what actions were attempted, which ones succeeded, and where failures occurred.
Why it matters: Reviewing this log helps you pinpoint the exact cause of deployment issues, whether it’s a timeout, detection rule mismatch, or installer error.
Real World Example
To better understand why the deployment failed in this case, we analyzed the IntuneManagementExtension.log file.
Outcome: As shown in the second screenshot, the Win32 installation was aborted once the timeout was reached.
Root cause: The command‑line switch used was incorrect.
What happened: The Microsoft installer responded by displaying a usage prompt. Because the installation was running under the system account, the prompt was invisible to the user and required manual interaction to close.
Result: With no way to dismiss the prompt, the installer process remained stuck until Intune’s monitoring timed out after 60 minutes.
Figure: IntuneManagementExtension.log
We attempted to install Microsoft Visio Viewer 2016 using the same command, but the /qs switch was incorrect. As a result, the Microsoft Installer displayed a message box that required user interaction to close. Because the deployment was running under the system context, the prompt was invisible to the user. With no way to dismiss it, the installation process became stuck and eventually failed with error 0x87D300C9.
Related Posts
- Deploy Win32 App Using Intune Enterprise App Catalog
- Understanding Win32 App Detection Rules
- Understanding Win32 App Requirements Rule
- Upgrade / Replace Win32 Apps with Supersedence Relationship
- Win32 App Deployment with Dependencies
- Win32 Apps vs LOB Apps
- Win32 App Deployment failed with error code 0x80070643
- Win32 App Deployment Failed with Error 0x87D1041C
- Win32 App Deployment failed with error 0x87D300C9
- Win32 App failed with error code 0x80070653
- Deploy Google Chrome for Enterprise with Intune Win32 App
- How to Prepare Win32 App Installation source for Microsoft Intune
- SCCM Device Collection Equivalents in Microsoft Intune for App Deployment
- Deploy Microsoft SQL Server Management Studio 19.02 through Intune
- Organizing Laptop and Desktop in Intune Using Filters
Subscribe to Techuisitive Newsletter
Be the first to know about our new blog posts. Get our newsletters directly in your inbox and stay up to date about Modern Desktop Management technologies & news.