WinGet failing during AutoPilot OOBE

[CameronWiller]

Brief description of your issue

WinGet scripts and packages fail to deploy during OOBE setup.
Applications install perfectly when deployed after the OOBE stages have completed and are redeployed via Intune when users reach their desktop.
Same packaged applications install without issue when installed from Company Portal after OOBE.

Steps to reproduce

Package MSIX bundles as LOB or Win32 and deploy to device group.
Package WinGet Script as Win32 Application
Assign to User Group within Intune
Wipe Device and proceed with OOBE
Installation will fail for all WinGet packages and cause OOBE to fail.

Expected behavior

Applications should deploy during OOBE, as they do when on live devices and installed with Company Portal

Actual behavior

Applications fail to deploy during OOBE and cause Autopilot build failure

Environment

[winget install]
Windows 10 1909, Windows 11
Microsoft.DesktopAppInstaller Latest from Repo

Microsoft Intune / AutoPilot

[matt-lock]

This isn't a duplicate to 215 - that was specifically asking about winget availability in Intune, whereas this is asking about winget during OOBE/Autopilot.

I'm getting the same issue, as the winget package doesn't get installed until after enrolment so any apps that are being pushed out that relies on winget are failing. I've tried pushing winget out as a dependant package, which although says installs successfully still doesn't make winget available during the enrolment session.

This is a massive gap in functionality and makes winget pretty useless for me, and have used Chocolatey instead although I'd prefer to use native Microsoft software.

[denelon]

Thanks for the clarity! We have a large number of duplicates due to the complexity of the product and the various ways users intend to use the product vs. what we've targeted for supported scenarios.

[MarcoBuess]

@denelon Is this still being tracked? It seems the v1.6 client still has this behavior.