An Intune Win32 app can appear installed while its detection result says otherwise. Before rebuilding the package, make the disagreement explicit.
This is documentation-based guidance, prepared with AI assistance. It is not a claim of testing in your environment. I run EndpointCraft; the free resource linked below is ours. No Microsoft affiliation.
Keep three observations separate
Start a small record for one pilot device:
| Observation | What to record |
|---|---|
| Installer outcome | Result, timestamp and intended execution context |
| Installed state | Expected app/version and artifact actually present |
| Detection outcome | Exact rule, context and result |
The point is to give the next test a clear question. If the expected artifact is absent, investigate installation. If it is present but the rule misses it, inspect detection and context. Do not treat a status label as proof of the expected installed version.
Check the rule's contract
For custom Win32 detection, Microsoft's documentation specifies a zero exit code and STDOUT output for a detected result. STDERR output can cause a not-installed result. Also check process architecture and the relevant file/registry view.
Read the official detection-rule requirements for the current behavior. Requirement scripts, detection scripts and remediation scripts serve different purposes; avoid transferring exit-code assumptions between them.
Test the missing-app case too
A rule that always reports installed can conceal a failed deployment. Keep a small matrix: clean install, already installed, uninstall and upgrade when in scope. Record what you changed, the observed result and the evidence needed for the next decision.
Use a pilot and preserve your original evidence. Do not post raw customer logs, tenant identifiers, device names or credentials in public questions. A sanitized statement of expected versus observed state is a better starting point.
A free working record
EndpointCraft's standalone Win32 preflight checklist and blank evidence sheet are ungated downloads. No email signup is required. They do not install software or guarantee a rollout result, and they are not excerpts from the paid toolkit.
What evidence do you wish came with every package handoff?
Top comments (0)