Stuck Deploying Win32 Apps with Windows Autopilot? Here’s a Temporary Fix

Having trouble setting up new devices with Windows Autopilot and Win32 apps? You’re not alone. There’s a known issue that can cause deployment failures when using a managed installer policy alongside Win32 apps during device preparation.

Why is this happening?

Organizations often use managed installer policies in Intune to control which applications can be installed on devices. This policy applies at the tenant level, affecting all Win32 apps deployed through Intune. Unfortunately, Windows Autopilot device preparation can’t guarantee the managed installer policy is delivered before the apps themselves. This mismatch can lead to deployment failures during the app installation phase.

Don’t worry, there’s a workaround!

Here’s a temporary solution to keep your deployments running smoothly:

1. Remove Win32 apps from your Windows Autopilot device preparation policies.
2. The managed installer policy and dependent apps will then install after the user reaches the desktop.

What’s next?

Microsoft is working on a permanent fix that ensures the managed installer policy is delivered before applications during device preparation. In the meantime, a change is rolling out with Intune’s October (2410) service release. This change allows deployments to proceed even with Win32 apps configured by:

Skipping all Win32 and Microsoft Store apps (New) via WinGet selection in the device preparation policy.
Continuing to the desktop.

Important Note:

After this change, the Windows Autopilot device preparation deployment report will show the skipped Win32 and Microsoft Store apps as “Skipped.”

We’ll keep you updated as a permanent solution becomes available. For further questions or comments, you can reach out to the Intune team through the provided contact information.

Sources: Undercode Ai & Community, Techcommunity.microsoft.com, Wikipedia, Internet Archive, Robotics Revolution
Image Source: OpenAI, Undercode AI DI v2