microsoft / microsoft/winget-cli

WinGet failing during AutoPilot OOBE

Open
#2,445 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Bug
Dominant language
C++
Stars
26.4k
Forks
1.8k
Avg merge
1d 11h
Merged PRs (30d)
15

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names no repository file, test, or code entry point. Start by reproducing the WinGet package failure during Windows 10 or 11 AutoPilot OOBE using the listed Intune assignment steps, then compare it with deployment after OOBE and Company Portal installation. Done means the cause is identified and WinGet packages deploy successfully during OOBE without causing the AutoPilot build to fail.

Written by the indexing model from the issue text.

Assessment

Domain
devops, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.