How to Fix Intune Error 0x87D1041C: App Not Detected After Installation [Complete Runbook]

What Error 0x87D1041C Looks Like in Production

When you deploy a Win32 application through Intune, the Intune Management Extension (IME) agent runs the installer and checks your detection rule right after the setup process exits. If the rule fails, the deployment is marked as failed even if the software actually installed and works on the device.

In our test lab, we packaged Notepad++ version 8.9.8 and assigned it to Windows devices. Three distinct symptoms appear when the detection rule is misconfigured.

First, the user receives a Windows toast notification reporting that the installation failed, even while the application shortcut is sitting on their desktop:

Second, checking the Microsoft Intune admin center under Apps > Windows > select your app > Device install status shows status Failed with error code 0x87D1041C and description “The application was not detected after installation completed successfully” across targeted devices (TechEUC-1 and TechEUC-2):

Third, the Company Portal app shows confusing information. During installation, it shows the progress bar and version 8.9.8:

As soon as setup finishes and the detection check fails, Company Portal displays a red error banner saying “This app is no longer detected on your device”. But when you open Control Panel > Programs and Features on the client machine, Notepad++ 8.9.8 is clearly installed:

Root Cause Analysis: Checking IntuneManagementExtension.log

To see why Intune failed detection, open the client log file on the affected machine. You do not need to guess what went wrong because the Intune agent logs the exact check it performed.

The log file is located at:

C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log

Open this log in CMTrace or Notepad and search for the application name or [Win32App]:

Here are the exact log lines from our test endpoint:

<![LOG[[Win32App] Checked file: C:\Program Files\Notepad++\notepad++.exe, FileVersion: 8.9.8.0, Operator: Equals, Value: 8.7.7, result of applicationDetected: False]LOG]!>
<![LOG[[Win32App] completed detection manager, overall detect result: False]LOG]!>
<![LOG[[Win32App] exec manager: exit code: 0, detect result: False, hasSubStatus: False]LOG]!>
<![LOG[[Win32App] installation result is: 0x87D1041C, subStatus: 0]LOG]!>

The log reveals the exact problem:

1. The installer ran and exited with code 0 (success).
2. Intune inspected C:\Program Files\Notepad++\notepad++.exe and found file version 8.9.8.0.
3. The detection rule was configured with Operator Equals and Value 8.7.7.
4. Because 8.9.8.0 does not equal 8.7.7, Intune concluded applicationDetected: False and produced error code 0x87D1041C.

How to Fix the Detection Rule in Microsoft Intune

In our scenario, someone updated the installation package to Notepad++ version 8.9.8, but the detection rule still required version 8.7.7 with the strict “Equals” operator:

Follow these steps to fix the rule:

1. Sign in to the Microsoft Intune admin center (intune.microsoft.com).
2. Go to Apps > Windows > click your application.
3. Under Manage, select Properties.
4. Scroll to Detection rules and click Edit.
5. Select the existing detection rule to edit it.
6. Change Operator from Equals to Greater than or equal to.
7. Update Value to 8.9.8.
8. Verify that Associated with a 32-bit app on 64-bit clients is set to No for 64-bit applications.
9. Click OK, then click Review + save and save your changes.

Syncing the Client to Verify the Fix

By default, Intune client devices sync policies every 8 hours. To verify the fix immediately without waiting:

1. On the client machine (TechEUC-1), open Company Portal.
2. Click Settings (the gear icon in the bottom left).
3. Click the Sync button under Device sync status.

Alternatively, open the Windows Services console (services.msc), locate the Microsoft Intune Management Extension service, right-click it, and select Restart.

Within a minute, the agent re-runs the detection rule against notepad++.exe. Because 8.9.8.0 is greater than or equal to 8.9.8, detection returns True, and the status updates to Installed in both Company Portal and the Intune admin center.

Other Common Causes of Error 0x87D1041C

If your version numbers match but you still get error 0x87D1041C, check these three common scenarios:

1. 32-Bit vs 64-Bit Registry and Folder Redirection

The Intune Management Extension agent runs as a 32-bit process. On 64-bit Windows, Windows redirects 32-bit queries automatically:

• C:\Program Files redirects to C:\Program Files (x86).
• HKLM\SOFTWARE redirects to HKLM\SOFTWARE\WOW6432Node.

If you deploy a 64-bit app but set Associated with a 32-bit app on 64-bit clients to Yes, Intune looks in the 32-bit locations where the file or key does not exist. Use the guide below to set this toggle correctly:

2. Background Installers Exiting Before Files Finish Writing

Some software installers use a small wrapper executable that unpacks the main setup files, launches a secondary background process, and immediately closes with exit code 0. Because the main launcher closed, Intune immediately checks the detection rule before the background installer has finished copying files. Always check vendor documentation for silent switches that wait for all child processes to complete before exiting.

3. MSI Product Code Changes During Updates

When using MSI detection rules, Intune checks the unique MSI Product Code GUID. While major releases keep the same Upgrade Code, vendors often change the Product Code for minor updates. If you update the installer package but keep the older Product Code in Intune, detection fails. Check the installed application in HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall on a test machine to get the exact Product Code GUID.

Summary Troubleshooting Checklist

Need Enterprise Application Packaging Support?

Managing application packaging and detection rules across thousands of corporate endpoints requires clean standards and consistent testing. If your team is tackling complex Win32 app packaging, Intune migrations, or stubborn deployment errors, TechEUC provides specialized enterprise endpoint engineering. Reach out through our Contact Page to discuss your environment.