Intune Deployment Guide
Common reasons apps fail in Intune
Overview
Most Intune Win32 app failures are caused by a small set of recurring issues: targeting, requirements, silent switches, context, detection, return codes, restart behavior, or client-side processing.
This guide summarizes the most common causes and what to check first.
Common causes
Failures are often configuration-related rather than cloud-side. The app may be assigned correctly but blocked by requirements, a bad command, incorrect context, or failed detection.
How to narrow it down
Start from the user-visible symptom, then map it back to the app lifecycle stage.
How the flow works
01SymptomWhat user/admin sees
02StageWhere in lifecycle
03EvidenceLogs and status
04FixChange the right setting
Intune UI examples
These compact mockups show the Intune settings that matter for this topic.
Assignment / Company Portal
Available assignment + user group
Sync Company Portal
Command / context
Silent switch and System/User behavior
Review return code
Detection
File/MSI/Registry rule
Update detection rule
IME retry schedule
Logs and retry timing
Wait or reassign for test
Practical reference
| Area | What to check |
|---|---|
| App not visible | Assignment type, group membership, Company Portal sync |
| App stuck installing | Pending reboot, another installer running, long timeout |
| Failed quickly | Wrong command, missing silent switch, missing files |
| Success but failed status | Detection rule does not match installed state |
Quick checklist
- Identify the symptom first.
- Map the symptom to assignment, requirements, command, detection, or logs.
- Use IME logs before changing multiple settings.
Troubleshooting checks
| Issue | What to check |
|---|---|
| Repeated install attempts | Detection may remain false. |
| Only user apps fail | Check user context and profile dependency. |
| Device apps fail during setup | Check System context, ESP timing, and IME logs. |

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