Intune Deployment Guide
Troubleshoot Win32 app deployment failures
Overview
Win32 app troubleshooting works best when you follow the deployment flow instead of changing random settings. Start with assignment and eligibility, then move to content, command execution, detection, return codes, and logs.
This guide gives a practical troubleshooting sequence for common Intune Win32 app failures.
Troubleshoot by stage
A failed status is the result, not the root cause. Determine which stage failed: targeting, requirements, download, install command, detection, restart, or reporting.
Use logs, not assumptions
The Intune Management Extension logs usually show the device-side reason for Win32 app failures.
How the flow works
Intune UI examples
These compact mockups show the Intune settings that matter for this topic.
Practical reference
| Area | What to check |
|---|---|
| Not visible | Check assignment type, user/device group, Company Portal sync |
| Not installing | Check requirements, sync, and IME processing |
| Failed | Check command, return code, and installer logs |
| Installed but failed | Check detection rule |
Quick checklist
- Use a pilot device where you can access logs.
- Match Intune status with timestamps in IME logs.
- Change one variable at a time.
Troubleshooting checks
| Issue | What to check |
|---|---|
| Waiting for install status | Check IME logs and device check-in. |
| Failed after command | Review exit code and installer-specific logs. |
| Installed but still failed | Fix detection rules. |

Leave a feedback
Include versions, steps, and any error text if you have them.