Share via

Intune App Deployment Troubleshooting

Edenfield, Cole 0 Reputation points
2026-05-20T15:36:49.6266667+00:00

Hello,

I have deployed a Win32 app through Intune. It is a simple app (Chrome), using an MSI installer. I have about 45 devices that have successfully installed the app and 36 that have errored out with this error "Fatal error during installation (0x80070643)".

What is the best way to figure out why this install is failing on specific devices as opposed to successfully installing on others? The logs do not seem to have much on this issue.

Microsoft Security | Intune | Application management

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-05-20T15:37:04.56+00:00

    Use Intune’s built‑in troubleshooting plus client‑side logs to narrow down why those specific devices fail.

    1. Get per‑device failure details in Intune
      1. In the Microsoft Intune admin center, go to Troubleshoot + support.
      2. Select the affected user (Select user), then select the failing device.
      3. Open Managed apps, select the Chrome Win32 app with Installation Status = Failed.
      4. Review the Installation details and error code text for that device. This view confirms targeting, assignment intent, and basic error info for each device.
      If the app is assigned as required and failing only on some devices, compare:
      • Assignment/intent (required vs available vs uninstall vs excluded)
      • OS version and SKU of working vs failing devices (for example, S‑mode doesn’t support MSI installs)
    2. Collect diagnostics from failing devices
      1. From the same Installation details pane for the failing app, select Collect diagnostics.
      2. Specify relevant log paths and file types (for example, C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\*.log, C:\Windows\Temp\*.log). Supported file types include .log, .txt, .dmp, .cab, .zip, .xml, .evtx, .evtl.
      3. Wait ~15–20 minutes, then select Download diagnostics.
      4. Compare diagnostics from a working device vs a failing device to see what differs (return codes from msiexec, missing prerequisites, access issues, etc.).
    3. Review Intune Management Extension logs on a failing client On a failing device, check:
      • C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log – overall agent activity, policy processing, and reporting.
      • AppWorkload.log – app check‑ins, install attempts, detection and applicability.
      • AppActionProcessor.log – detection and applicability checks.
      Use CMTrace (CMTrace.exe) to open these logs and look for the Chrome app name or the specific deployment ID around the time of the failure. This usually reveals:
      • The exact msiexec command line Intune ran
      • The MSI return code and any transform/parameter issues
      • Whether detection rules evaluated as expected
    4. Validate the installer and command line in system context Since 0x80070643 is a generic MSI “fatal error” code, confirm that the same MSI and command line work locally in the system context:
      • On a failing device, run the Chrome MSI with the same silent switches used in Intune, but in system context (for example, using a tool like PSExec as described in the application error reference).
      • If it fails locally in system context, the issue is with the MSI, parameters, or local environment (permissions, prerequisites, existing Chrome install, etc.), not Intune.
    5. Check environment differences between working and failing devices Based on logs and local tests, compare:
      • Existing Chrome versions or different install paths that might conflict with the MSI
      • Disk space and AV behavior (ensure AV exclusions for Intune Management Extension content and C:\Windows\IMECache as documented)
      • OS version and SKU (ensure all are on supported Windows versions and not in S‑mode)
    6. If needed, open a support ticket with diagnostics If the cause is still unclear, use the collected diagnostics from failing devices when opening a support ticket. The Win32 app diagnostics are specifically designed to accompany support cases for installation failures.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.