Win32 App Health Checker

How it works

Enter the install and uninstall commands, the return codes you have mapped, and whether a detection and requirement rule are configured. The checker applies the rules below and returns findings graded Error, Warning or Note.

What it checks

• Silent installation. Intune does not support interactive installs. Commands without a silent switch are flagged.
• serviceui.exe and similar tools. Forcing interaction with the signed-in user is unsupported and causes unpredictable results.
• PowerShell bitness. Calling powershell.exe in a command launches 32-bit PowerShell; use %SystemRoot%\Sysnative\WindowsPowerShell\v1.0\powershell.exe for 64-bit.
• Context mismatch. A user-context app writing to Program Files or HKLM cannot succeed; those need system context.
• Return codes. Every app needs a success mapping; MSI installers usually need a reboot mapping for 3010.
• Detection. Without a detection rule the app reports as failed (0x87D1041C) even when it installed, because Intune re-runs detection after installation.

Supported scenarios

• Reviewing a Win32 app before you create or migrate it in Intune.
• Diagnosing an app that installs but reports failure.
• Sanity-checking commands produced by packaging automation.

Common problems

• Installers often use non-standard success codes; add explicit mappings rather than assuming 0.
• The installer process has a 60-minute timeout — long-running scripts can be reported as failed.
• PowerShell install scripts are limited to 50 KB.
• Robust detection rules are the single most common fix for "installed but not detected" errors.

Related

Guide: Win32 apps · Guide: Intune app troubleshooting · Detection Rule Linter · All tools