Win32 Appshex 0x652
Fix Intune Error 1618: Another installation was already running, so Windows Installer refused to start a second one (ERROR_INSTALL_ALREADY_RUNNING).
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: AppEnforce.log (ConfigMgr) · Application event log (MsiInstaller)
Root causes
- Windows Update, an Office or Microsoft 365 Apps update, or another app deployment holds the global msiexec mutex.
- A hung msiexec.exe from an earlier failed install is still running.
- Several MSI-based Win32 apps targeted the same device and started at the same moment during enrollment or ESP.
- Another management tool or user-run installer is installing while Intune tries to install.
Step-by-step remediation
- List the running installers: Get-Process msiexec | Select-Object Id, StartTime. Note which one has been running for a long time.
- If it is the earlier failed install and nothing is progressing, stop that process, then retry the app.
- Otherwise let the other install finish. Intune treats 1618 as retry by default, so a short wait normally clears it.
- If it recurs at enrollment, use app dependencies or reduce the number of required MSI apps installing in parallel.
- Confirm the retry succeeds in the log and the detection rule passes.
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.
Related Error Codes in This Category
Other Win32 Apps errors with their own runbooks.
- 0x87D00324The installer exited 0, but the detection rule evaluated false after it ran, so the app is reported as failed.
- 0x87D1041CIntune did not find the app after install: the detection rule no longer matches, usually because the app was uninstalled or updated itself.
- 1603Windows Installer hit a fatal error during the install (ERROR_INSTALL_FAILURE); the MSI log shows the step that failed.
- 3010The install worked but needs a restart to finish (ERROR_SUCCESS_REBOOT_REQUIRED); it is a soft reboot, not a failure.