How to fix this - Windows 10.0.26200.8117 – Failed The application was not detected after installation completed successfully (0x87D1041C)

Question

How to fix this - Windows 10.0.26200.8117 – Failed The application was not detected after installation completed successfully (0x87D1041C)

Hemanth Reddy Chinthamreddy 0

Hello everyone,

I am trying to deploy the UltraViewer application using Intune, but the installation is failing.

The error shown is: Windows 10.0.26200.8117 – Failed The application was not detected after installation completed successfully (0x87D1041C)

From my understanding, the app seems to install, but Intune is unable to detect it afterward.

Since UltraViewer does not provide an MSI, I converted the EXE into an .intunewin package and deployed it as a Win32 app. I used silent install/uninstall commands as shown in the attached screenshot.

Could the issue be related to the silent command I used? Or is it more likely a detection rule issue?

Kindly review and advise:

Should I modify the install/uninstall commands?
What could be the probable cause for this detection failure?

Thanks in advance for your help!

Pauline Mbabu 1,840 Reputation points Microsoft Employee

2026-04-17T13:49:51.6333333+00:00

Hello @Hemanth Reddy ,
Error 0x87D1041C means Intune believes the UltraViewer installer completed successfully but fails during the post install detection phase, which almost always indicates a detection rule problem rather than an issue with the silent install or uninstall commands themselves. With EXE based Win32 apps, Intune has no built in way to confirm installation, so it relies entirely on the detection logic you configure, and if that logic points to an incorrect file path, wrong architecture, missing registry key, or an EXE that installs per user instead of per machine, Intune will report this exact error even though the app is actually installed. For UltraViewer in particular, the most common cause is using an unreliable or incorrect detection rule, as the installer typically places UltraViewer_Desktop.exe under Program Files or Program Files (x86) and does not always create a predictable uninstall registry key. Your install and uninstall commands are usually fine as long as the silent install truly completes without user interaction; instead, you should focus on switching to a robust file based detection rule or a simple PowerShell detection script that explicitly checks for the UltraViewer executable and exits with code 0 when found. Microsoft documents this detection behavior for Win32 apps here https://learn.microsoft.com/en-us/intune/app-management/deployment/troubleshoot-win32
Pauline Mbabu 1,840 Reputation points Microsoft Employee

2026-06-04T15:48:49.1366667+00:00

Hello @Hemanth Reddy Chinthamreddy ,
This is a follow-up on the response above. If it helped answer your question, kindly mark it as Accepted Answer.

If you need more help, please share additional details in the comments.

Thanks!

1 answer

Your answer

Pauline Mbabu 1,840 Reputation points Microsoft Employee

2026-04-17T13:49:51.6333333+00:00

Hello @Hemanth Reddy ,
Error 0x87D1041C means Intune believes the UltraViewer installer completed successfully but fails during the post install detection phase, which almost always indicates a detection rule problem rather than an issue with the silent install or uninstall commands themselves. With EXE based Win32 apps, Intune has no built in way to confirm installation, so it relies entirely on the detection logic you configure, and if that logic points to an incorrect file path, wrong architecture, missing registry key, or an EXE that installs per user instead of per machine, Intune will report this exact error even though the app is actually installed. For UltraViewer in particular, the most common cause is using an unreliable or incorrect detection rule, as the installer typically places UltraViewer_Desktop.exe under Program Files or Program Files (x86) and does not always create a predictable uninstall registry key. Your install and uninstall commands are usually fine as long as the silent install truly completes without user interaction; instead, you should focus on switching to a robust file based detection rule or a simple PowerShell detection script that explicitly checks for the UltraViewer executable and exits with code 0 when found. Microsoft documents this detection behavior for Win32 apps here https://learn.microsoft.com/en-us/intune/app-management/deployment/troubleshoot-win32
Pauline Mbabu 1,840 Reputation points Microsoft Employee

2026-06-04T15:48:49.1366667+00:00

Hello @Hemanth Reddy Chinthamreddy ,
This is a follow-up on the response above. If it helped answer your question, kindly mark it as Accepted Answer.

If you need more help, please share additional details in the comments.

Thanks!

Answer 1

Error 0x87D1041C means Intune considers the installation successful, but the app isn’t detected afterward. This almost always points to a detection rule or detection-script problem, not the silent install command itself.

For this scenario (UltraViewer as a Win32 app):

Validate that the app really installs
- On a test device, run the same silent install command used in Intune.
- Confirm UltraViewer appears under Settings > Apps > Installed apps and that it launches correctly.
- If it doesn’t install, fix the install command first; Intune can’t detect what isn’t there.
Fix the detection rules
- If using built-in detection (file/registry):
  - Identify a reliable marker that exists only when UltraViewer is installed (for example, its EXE path under C:\Program Files or C:\Program Files (x86) or a specific registry key/value the installer creates).
  - Configure Intune detection to look for that exact file or registry key.
- If using a custom detection script:
  - Ensure the script follows Intune’s rules:
    - Exit code 0 = app detected.
    - Exit code non‑zero = app not detected.
    - STDOUT must contain data when the app is detected.
    - STDERR must be empty; any data written to STDERR makes Intune treat the app as not installed, even with exit code 0.
  - Encode the script as UTF‑8 BOM as recommended.
From the detection behavior:
- If the script exits with non‑zero, Intune reports not installed.
- If the script exits 0 but writes anything to STDERR, Intune reports not installed.
- If the script exits 0 and writes something (anything) to STDOUT and nothing to STDERR, Intune reports installed.
Re-check status in Intune
- After adjusting detection, redeploy or sync the device.
- In the Intune admin center, go to Apps > All apps, select the UltraViewer Win32 app, and review Device install status to confirm the detection state.
If still failing, collect diagnostics
- Use Collect diagnostics on the app’s Installation details pane to gather logs from the device and review for detection script errors or path/registry mismatches.

In summary, the most probable cause is a misconfigured detection rule or detection script (exit code/STDOUT/STDERR behavior), not the silent install command, assuming the app installs and runs correctly when tested manually.

References: