Known issue: Windows Autopilot device preparation with Win32 apps and managed installer policy

There is a known issue with Windows Autopilot device preparation. Deployment issues occur when the Managed Installer policy is enabled and you try to install a Win32 app during device preparation.

Managed installer Commonly used in organizations to allow only trusted applications to be installed. Intune’s managed installer policies are configured at the tenant level, so they affect all Win32 apps deployed within your organization. Windows Autopilot device preparation currently does not have a feature to ensure that a managed installer policy is provisioned prior to application delivery. This can cause deployments using Win32 apps selected in the Windows Autopilot device readiness policy to fail during the app installation phase.

How to solve

To resolve this issue, simply remove the Win32 app from all Windows Autopilot device readiness policies. Managed installer policies and dependent apps are installed after the user accesses the desktop.

solve

We are currently rolling out changes with Intune’s October (2410) service release. This change allows all Win32 and Microsoft Store apps (new) to be skipped and continue to be deployed via WinGet selected in the device readiness policy, even if Win32 apps are configured. Desktop. However, managed installer policies and dependent apps are installed after the user accesses the desktop.

After making this change, you will see selected Win32 and Microsoft Store apps reported as “Skipped” in the Windows Autopilot Device Readiness Deployment report.

This is a temporary change until a fix is ​​ready to ensure that the Managed Installer policy is available before delivering applications while preparing Windows Autopilot devices.

We will continue to update this post as new information becomes available. If you have questions or comments for the Intune team, please reply to this post or contact @IntuneSuppTeam.