Application was not Detected Intune Error 0x87D1041C

This error is generally caused by an Incorrect detection rule specified during the creation of the Win32 application deployment from Intune. As you’re aware, the detection rule’s purpose is to identify the presence of the application. If the detection rule isn’t configured accurately, it may fail to detect the application, despite it being installed correctly.

Despite successful deployment via Intune, you may encounter error code 0x87D1041C in the Intune admin center. As an example, I deployed an app called ‘Notepad++’ which was deployed successfully, but I observed this error when checking its deployment status on Intune.

Notepad++ app deployment screenshot
Notepad++ app deployment screenshot

The below screenshot shows that the Application Status has failed and Status Details provide further Information about the Error code.

Error code 0x87D1041C
Error code 0x87D1041C

How to Fix Error code 0x87D1041C

As we already know the most common reason for this error is “Intune is not able to Detect the application” using the configured Detection rule in Win32 App deployment. Therefore, the only way to fix it is to check the Detection rule configured for the App and make sure it’s correct.

1. Example of a Misconfigured rule

Below is an example of a misconfigured rule for an application Notepad ++. The Detection rule which is shown in the below screenshot was unable to detect the presence of Notepad ++ after deployment. Therefore even though the app was installed successfully, it was reported as failed.

Example of a Misconfigured rule
Example of a Misconfigured rule

2. Update Detection Rule

To fix this error, we’ve made an update to the Win32 App deployment’s detection rule. We are now using file-based detection to verify the existence of ‘Notepad++.exe’ under ‘C:\Program Files\Notepad++.’ If the file ‘Notepad++.exe’ is found, it will confirm the successful installation of the application, preventing unnecessary re-deployment.

It’s important to clarify that we previously used a Registry-based detection logic, and we’ve now shifted to a File-based detection logic. This change doesn’t necessarily indicate that File-based detection is superior to Registry-based detection; it primarily serves to highlight the issue with the existing detection logic, which was failing to identify the application.

Regardless of the Detection Rule type chosen, the key question to consider is, “Can it accurately detect the presence of the deployed application?

The screenshot below displays the revised Detection logic for our Notepad++ application. We hope the solution discussed in this blog post will assist you in identifying the issue on your end and resolving the error.

Update Detection Rule
Update Detection Rule

More Information

If you’d like to delve deeper into this error, you can explore the subsequent sections of this blog post, which offer further insights into the issue.

applicationDetected: False

Although error code 0x87D1041C provides a clear indication of the issue’s cause, you can gain further insights by examining the IntuneManagementExtension.log file on one of the target devices, where you may find an “applicationDetected: False” error.

applicationDetected: False
applicationDetected: False

Here’s an excerpt from the Intune Management Extension log file related to this app deployment. From the log file, it’s evident that the Detection logic is unable to identify the application, leading to the application deployment status reporting failure.

[Win32App][DetectionActionHandler] Handler invoked for 1 app detections. IntuneManagementExtension 07/07/2023 09:33:53 5 (0x0005) [Win32App][DetectionActionHandler] Detection running for policy with id: 19de19a9-71a2-462a-942f-86aaec859ea1. IntuneManagementExtension 07/07/2023 09:33:53 5 (0x0005) [Win32App] ProcessDetectionRules starts IntuneManagementExtension 07/07/2023 09:33:53 5 (0x0005) [Win32App] ProcessDetectionRules Parsing InstallEx… IntuneManagementExtension 07/07/2023 09:33:53 5 (0x0005) [Win32App] DetectionType 0 IntuneManagementExtension 07/07/2023 09:33:53 5 (0x0005) [Win32App] Start detectionManager SideCarRegistryDetectionManager IntuneManagementExtension 07/07/2023 09:33:53 5 (0x0005) [Win32App] To check Exist, Path: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Notepad++\”C:\Program Files\Notepad++\uninstall.exe, valueName: applicationDetected: False IntuneManagementExtension 07/07/2023 09:33:53 5 (0x0005) [Win32App] Checked reg path: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Notepad++\”C:\Program Files\Notepad++\uninstall.exe, name: , operator: 0, type: 1, value: , result of applicationDetected: False IntuneManagementExtension 07/07/2023 09:33:53 5 (0x0005) [Win32App] detectionManager SideCarRegistryDetectionManager got applicationDetectedByCurrentRule: False as system IntuneManagementExtension 07/07/2023 09:33:53 5 (0x0005) [Win32App] Completed detectionManager SideCarRegistryDetectionManager, applicationDetectedByCurrentRule: False IntuneManagementExtension 07/07/2023 09:33:53 5 (0x0005) [Win32App][DetectionActionHandler] Detection for policy with id: 19de19a9-71a2-462a-942f-86aaec859ea1 resulted in action status: Success and detection state: NotDetected. IntuneManagementExtension 07/07/2023 09:33:53 5 (0x0005)

Excerpt from IntuneManagementExtension.log

To access the Intune Management Extension log file, follow these steps:

  1. Navigate to C:\ProgramData\Microsoft\IntuneManagementExtension\Logs your computer.
  2. Look for the most recent version of the IntuneManagementExtension.log file.
  3. The recommended tool for viewing this log file is CMTrace.


As demonstrated in this blog post, resolving the error code 0x87D1041C, which stems from misconfigured detection logic in Win32 app deployments, can be a straightforward process. There are several types of detection logic available, including MSI, File, and Registry. Regardless of the chosen detection logic type, the critical factor is its ability to accurately detect the application. Properly configured detection logic is key to a successful deployment.


Leave a Comment