Join our Newsletter — 33% off our NHI Course

Could SYSTEM-context winget fail on Microsoft Store apps?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: Microsoft Store app installs fail under SYSTEM because Store packages are per-user, according to Fleet. Windows rollout logic has to match the app’s scope and use MSIX-native verification instead of legacy registry checks.

Editorial analysis by NHI Mgmt Group, based on content published by Fleet: “Put Microsoft Store apps in Windows self-service with winget”.

Key questions

Q: What should security and IT teams do first when winget cannot install a Store app?

A: First confirm whether the app is meant to be installed per user or provisioned machine-wide.

Q: What are the signs that a Windows Store app deployment is using the wrong verification method?

A: A common sign is that the installer appears to run successfully, but the app does not show up in the registry-based uninstall view.

Q: Why do Microsoft Store app installs fail when run from endpoint management tools?

A: They fail because the Microsoft Store app model is user-scoped, while many endpoint tools execute scripts as SYSTEM or another device-level context.

Practitioner guidance

  • Define the installation scope before packaging Store apps Classify each app as per-user or machine-wide before writing the deployment script, because the install mechanism changes completely between winget in a user session and Appx provisioning as SYSTEM.
  • Move winget execution into the logged-on user session Use a short-lived scheduled task owned by the console user so winget runs where the Microsoft Store accepts it, rather than trying to force SYSTEM-context installation.
  • Validate installs with Get-AppxPackage Treat the MSIX package list as the source of truth and use Get-AppxPackage -AllUsers to confirm that the package exists after the task completes.

Bottom line: Microsoft Store apps expose a control gap between device-level automation and user-scoped installation, and that gap is why SYSTEM-context winget runs fail.

Glossary terms: Per-user application deployment, MSIX, User session execution, Machine-wide provisioning

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

Context-bound deployment is the real control issue: this pattern shows that endpoint automation fails when the installer’s trust boundary does not match the package’s scope. The article is not really about winget syntax; it is about execution context, entitlement scope, and verification domain. For device teams, the lesson is that packaging success depends on aligning task context with application model, not on forcing a universal install path.

A few things that frame the scale:

  • Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.

A question worth separating out:

Q: When should teams use per-user installation instead of machine-wide provisioning for Store apps?

A: Use per-user installation when the app is meant to appear in self-service for a logged-on user and can be installed in that user’s session. Use machine-wide provisioning only when the app must be present on the device image for all users and you are prepared to handle the extra licensing and package-hosting overhead.

👉 Read our full editorial: Windows Store app deployment fails under SYSTEM context


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.