Intune Win32 app reports install failure due to a detection rule problem

Symptoms

• Intune admin center shows the Win32 app install as failed for one or more devices
• Local investigation shows the installer executable actually ran and completed on the device

Environment / applicability

Windows Intune Management Extension

Intune — lifecycle: current

Diagnosis

1. Review app troubleshooting details in the Intune admin center: Open the app's "Troubleshoot + support" pane in the Microsoft Intune admin center to see when the app was created, modified, targeted, and delivered to the device.

   Expected: Confirms targeting/delivery occurred and narrows whether the failure is at install or detection time.

2. Collect and review client-side logs: On the device, use the "Collect logs" option from the app's Installation details pane, or review C:\ProgramData\Microsoft\IntuneManagementExtension\Logs directly - specifically AppWorkload.log (app check-ins, install, applicability and detection logging) and AppActionProcessor.log (detection and applicability checks).

   Expected: Identifies whether the installer itself failed, or whether it succeeded but the detection method did not match.

   Warning: Use CMTrace.exe to view these log files.

3. Check the detection rule logic against the real installed state: Compare the detection rule (file version, registry value, or script) against what is actually present on the device after install.

   Expected: Identifies a mismatch, such as an expected file version string that does not match the installed file's real version.

   Warning: Detection scripts run in the SYSTEM context, so user-specific environment variables are not meaningful inside them.

Root cause

Intune determines success or failure of a Win32 app install by running the configured detection rule/method after the installer exits; if the detection rule's logic (file version, registry value, or custom script) does not correctly match the real installed state - for example due to a mismatched expected file version - Intune reports a failure even though installation itself succeeded.

Resolution

1. Verify the real file version with PowerShell: Run: $FileVersion = [System.Diagnostics.FileVersionInfo]::GetVersionInfo("<path to binary file>").FileVersion ; $FileVersion = $FileVersion.Trim() -- then compare $FileVersion to the version configured in the detection rule.

   Expected: Confirms the exact real file-version string to use in the detection rule.

2. Correct the detection rule: Update the app's detection rule in the Intune admin center to match the confirmed real installed state (correct file version, registry path/value, or script logic).

   Expected: Future detection evaluations correctly identify the app as installed.

Verification

1. Trigger a policy sync on an affected device and confirm the app now reports as successfully installed in the Intune admin center.

Rollback

Diagnosis is read-only (log review and detection-rule inspection); correcting a detection rule in the Intune admin center only changes future evaluation and can be reverted by editing the app again.

Commands

[System.Diagnostics.FileVersionInfo]::GetVersionInfo("<path to binary file>").FileVersion

Risk

Risk level: Medium · Requires admin: Yes

References

• Troubleshoot Win32 Apps in Microsoft Intune — Microsoft

Record metadata

ID

fx-intune-0001

Created

2026-08-17T00:00:00Z

Updated

2026-08-17T00:00:00Z

Freshness

current