Winget Needs Full Enterprise Support—SYSTEM Context, Intune Integration, and Machine-Wide Deployment

Relevant area(s)

WinGet CLI

Description of the new feature / enhancement

Dear Microsoft,

As an enterprise administrator, I’ve been working to integrate Winget into our app deployment workflows using Intune. While Winget shows great promise, its current design creates unnecessary friction for enterprise use:

Winget runs in user context by default, making it incompatible with SYSTEM-level deployment scenarios—especially via Intune.

The App Installer MSIX packaging restricts machine-wide availability and complicates access for SYSTEM processes.

There is no native support in Intune for Winget manifests, updates, or bulk deployments.

Admins are forced to use workarounds—resolving paths manually, scripting elevation logic, and testing edge cases—just to deploy standard apps.

This is a significant gap. Winget should be a first-class citizen in enterprise environments, with:

A machine-wide installer that registers Winget for SYSTEM use.

Intune-native integration for Winget manifests and update automation.

Clear documentation and support for enterprise deployment scenarios.

We shouldn’t have to reverse-engineer consumer tools to meet enterprise needs. Please prioritize making Winget fully enterprise-ready. The demand is real, and the potential is huge.

Sincerely, IT Administrator

Proposed technical implementation details

No response

Start with the WinGet CLI area and investigate the stated SYSTEM-context limitations, App Installer MSIX packaging, and Intune integration needs. Done would require a defined approach for machine-wide registration, Intune support, and enterprise deployment documentation; the issue provides no files or tests to begin from.