Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

5.1.5. Monitoring and Troubleshooting App Installs

💡 First Principle: Intune never sees an install happen; it sees what the device reports afterward — and a Win32 app's report is only as true as its detection rule. Troubleshooting therefore works from the outside in: confirm the assignment and intent Intune resolved, then the device's report, then the agent's own logs on the device. Most "failed" installs turn out to be a targeting conflict or a detection mismatch, not a broken installer.

Start with reports. Apps > Monitor > App Install Status lists apps with install and failure totals. Inside an app, Device install status and User install status break those down per device and per user. For a single device, Devices > All devices > device > Managed Apps shows every app with its Resolved intent (such as Required install, Required uninstall or Available) and installation status, and lets you collect diagnostics for Win32 apps. The Troubleshoot + support blade walks the same path from a user's point of view: select the user, the device, Managed Apps, then a failed app.

Then check intent. "Resolved intent" matters because users and devices are usually in several groups. A single group can't carry two intents for one app, so conflicts come from overlapping memberships, and Intune resolves them with fixed rules:

Group typesConflicting intentsResult
User + userRequired + AvailableRequired and Available
User + userRequired + UninstallRequired
User + userAvailable + UninstallUninstall
User + deviceUser Uninstall + Device RequiredRequired
User + deviceUser Required + Device UninstallRequired
User + deviceUser Available + Device UninstallAvailable
Device + deviceRequired + UninstallRequired
Device + deviceAvailable + UninstallUninstall

The pattern: Required beats Uninstall, and Uninstall beats Available — except User Available against Device Uninstall, which resolves to Available. Intent is evaluated before assignment filters, so a filter can't rescue a conflict.

Then check the device. Win32 apps, Store apps, scripts and remediations are handled by the Intune Management Extension, whose logs sit in C:\ProgramData\Microsoft\IntuneManagementExtension\Logs and read best in CMTrace. IntuneManagementExtension.log is the main log; AppWorkload.log covers Win32 app deployment; AppActionProcessor.log covers detection and applicability checks; AgentExecutor.log covers PowerShell script runs. To force the agent to check in now, use Company Portal Settings > Sync (which triggers both an MDM and an IME check-in) or restart the IntuneManagementExtension service. The IME doesn't run on Windows in S mode or Windows Home, and on co-managed devices the Apps workload must be set to Pilot Intune or Intune.

Read the error code. A few are worth recognizing:

  • 0x87D1041C — "not detected after installation completed successfully". The installer worked but detection didn't find it: the user removed the app, the detection rule doesn't match, or a self-updating app changed its version outside Intune.
  • 0x80073CFB — the Windows package is already installed and reinstallation is blocked; increment the version and re-sign.
  • 0x87d13b7f (iOS) — the app needs an app configuration policy that isn't targeted to the same groups.
  • 0x87d13b7e (iOS) — no VPP licenses remaining.

Know the self-healing rules. If a required app isn't detected, Intune offers it again within about 24 hours, and a user who uninstalls a required app gets it back on that schedule. Win32 apps installed as Available aren't reinstalled if the user removes them. In the Windows Company Portal, users can restart an install whose progress hasn't changed in two hours. And Win32 apps installed by Intune aren't uninstalled automatically when the device unenrolls.

When a user-targeted app never shows up at all, Microsoft's checklist is: is the intent Available and the device type supported; for Windows BYOD, has the user added a work account; has the user hit the Entra Maximum devices per user limit; and for an iOS automated device enrollment device, does it show "Enrolled by User"?

⚠️ Exam Trap: A user in a group assigned Uninstall and another group assigned Required keeps the app — Required wins. If the goal is removal, take the user out of the Required group (or remove that assignment), not add another Uninstall assignment.

Reflection Question: The report shows a Win32 app as Failed with 0x87D1041C on 60 laptops, yet users say the app opens fine. What does the code tell you, and which part of the app's configuration would you change first?

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned