Intune Deployment Guide
System vs User context in Intune
Overview
Install behavior controls the context used to run the app command. In Intune Win32 apps, System and User context can behave very differently.
The key point: User context does not automatically mean the app installs only for that user. It means the command runs under the user context. The installer still decides where it installs.
System context
System context is common for device-wide installations because it can write to Program Files, HKLM, services, and machine-level locations.
User context
User context is useful when the installer or script depends on the signed-in user profile, HKCU, or user-specific paths.
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 |
|---|---|
| System | Device-wide apps, services, Program Files, HKLM |
| User | Per-user apps, HKCU, user profile paths |
| Detection | Must match where the app actually installs |
| Testing | Run in matching context before deployment |
Quick checklist
- Use System for most device-wide Win32 apps.
- Use User only when the installer requires user profile context.
- Match detection rules to the actual install location.
Troubleshooting checks
| Issue | What to check |
|---|---|
| Works manually but fails in Intune | Test under System context when Install behavior is System. |
| Detection fails | Check whether the app installed under HKLM or HKCU. |
| Per-user app not found | Confirm the user is signed in and assignment targets the right user group. |

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