ESP Fails: Another Installation Is in Progress (LOB + Win32)

An Autopilot device sits in the device setup phase of the Enrollment Status Page, a required Win32 app reports Another installation is in progress, please try again later, and ESP fails.

Look at what else the ESP is tracking. If the required app list has a line-of-business (LOB) MSI app next to Win32 apps, Microsoft documents this exact failure in the Enrollment Status Page article:

Both LOB (MSI) and Win32 installers use TrustedInstaller, which doesn’t allow simultaneous installations. If the OMA DM agent starts an MSI installation, the Intune Management Extension plugin starts a Win32 app installation by using the same TrustedInstaller. In this situation, Win32 app installation fails and returns an Another installation is in progress, please try again later error message. In this situation, ESP fails.

So the problem is two install paths sharing one installer service. LOB MSI apps are installed by the OMA DM agent, Win32 apps by the Intune Management Extension (IME), and when their installs overlap during ESP, the Win32 app is the one that fails.

I haven’t reproduced this on a live tenant for this article. Everything below comes from Microsoft Learn, linked inline.

Fix: one app type for everything ESP tracks

Microsoft’s guidance is short: “don’t mix LOB and Win32 apps when using Windows Autopilot.” The Win32 app management article says the same and recommends the Win32 app type exclusively, “particularly when you have a multiple-file Win32 app installer.”

1. In the ESP profile, list the apps under Block device use until these required apps are installed if they are assigned to the user/device. If the profile uses Block device use until all apps and profiles are installed, list every required app assigned to the device.
2. For each required app, check its type in the Intune admin center under Apps. Note every app that’s a line-of-business (MSI) app.
3. Repackage each of those MSIs as a Win32 app (.intunewin) and assign it in place of the LOB app. Don’t leave both versions assigned to the same devices.
4. Test on a clean run, with a wiped or newly reset device, not the half-provisioned one that already failed.

The ESP article also lists which app types the device setup phase tracks: per-machine LOB MSI apps, LOB store apps with device install context, Win32 apps and WinGet apps. Check every app assigned to the device in device context, not only the apps you picked as blocking.

The other way out: Autopilot device preparation

If you can’t drop the LOB apps, Microsoft points to Windows Autopilot device preparation. It doesn’t use ESP, and the ESP article states it “supports mixing of LOB and Win32 apps.” The Win32 article confirms that mixing is supported during device preparation. Moving a deployment to device preparation is a bigger change than repackaging a few MSIs, so weigh it against the size of your app list.

Confirm it on the device

The ESP troubleshooting guide shows where ESP records app state, under:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Autopilot\EnrollmentStatusTracking

• ESPTrackingInfo\Diagnostics\ExpectedMSIAppPackages has a subkey for each LOB (MSI) app ESP tracked. If MSI apps are listed here next to failed Win32 apps, you’re mixing types.
• Device\Setup\Apps\Tracking\Sidecar\Win32App_{AppID} holds InstallationState for each device-context Win32 app. A value of 4 means Error, and the guide says ESP stops installing applications when any app reaches it. It also says to check the Intune Management Extension log for the cause.

For reading the IME logs, see reading AppWorkload.log and the IME logs. If the failure happens outside Autopilot, the related article is Win32 MSI error 1618.

Get the Deployment Doctor

Kit 1 founding presale is open: $39 (regular $49). The Autopilot + Device Prep Deployment Doctor checks your tenant, read-only, for the config that breaks ESP and Device Preparation, including LOB and Win32 apps mixed in the same ESP. You pay now and get the files by Tuesday, December 1, 2026, sooner if they’re ready. Full refund any time before delivery, then 14 days after delivery. The founding price runs until Friday, December 4, 11:59 PM MT.

Want to look first? The free, read-only beta scripts are on GitHub: autopilot-deployment-doctor-beta. Its README says they haven’t been run against a live tenant.

FAQ

Why does a Win32 app fail with Another installation is in progress during ESP?

Microsoft says LOB (MSI) and Win32 installers both use TrustedInstaller, which doesn’t allow simultaneous installations. When an MSI from the OMA DM agent is installing, the Win32 app from the IME fails with that message and ESP fails.

Can I mix LOB and Win32 apps in Windows Autopilot?

Not with ESP. Microsoft says don’t mix LOB and Win32 apps when using Windows Autopilot. Windows Autopilot device preparation doesn’t use ESP and supports mixing them.

Where do I see ESP app install state on the device?

Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Autopilot\EnrollmentStatusTracking. An InstallationState of 4 on a Win32 app means Error.

Sources

All retrieved 2026-10-23.

• Set up the Enrollment Status Page, Microsoft Learn: the TrustedInstaller conflict, the error text, the tracked app types, and device preparation as the alternative.
• Win32 app management in Microsoft Intune, Microsoft Learn: use the Win32 app type exclusively; mixing is supported in device preparation.
• Troubleshoot the Enrollment Status Page, Microsoft Learn: the EnrollmentStatusTracking registry keys and InstallationState values.
• Windows Autopilot device preparation overview, Microsoft Learn.