Skip to main content
Win32 Appsdecimal -2016345060

Fix Intune Error 0x87D1041C: Intune did not find the app after install: the detection rule no longer matches, usually because the app was uninstalled or updated itself.

Open the log below first. It is the quickest way to confirm which of the causes applies before you change anything.

AppWorkload.log

Folder: C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\

Also check: IntuneManagementExtension.log

Root causes

  • The app deployed successfully and was then uninstalled by the user or another tool. A required app is reinstalled at the next check-in.
  • A self-updating app changed its version, so a rule pinned to the old version or MSI product code no longer matches.
  • The detection rule was wrong from the start: the wrong path, registry view or product code.
  • The identity in the package does not match what the device reports for the installed app.

Step-by-step remediation

  1. Open AppWorkload.log on the device and search for the app ID. Note whether detection ran after a successful install or after a later evaluation.
  2. Check whether the app is actually installed. If it is gone, find out what removed it before changing the deployment.
  3. If it is installed, compare the detection rule with the installed version, path and registry values, and correct the rule.
  4. For self-updating apps use a "greater than or equal" version rule or a file-exists rule, not an exact product code.
  5. Sync the device from Company Portal or Settings > Accounts > Access work or school > Info > Sync, then confirm the status clears in the Intune admin center.

For the full diagnosis around this error, read Win32 app stuck at waiting or pending.

Stop it happening on the next package

Most Win32 failures are decided by the detection rule and the install command, so fix them at the source before the app is assigned again.

Other Win32 Apps errors with their own runbooks.

Search all 21 error codes