Put Microsoft Store apps in Windows self-service with winget
Blog post from Fleet
Fleet can provide Microsoft Store applications as self-service Windows software, but its scripts run under the SYSTEM account while Store apps and winget’s msstore source require a logged-in user context. Although installation and removal use simple winget commands identified by a Store ID, running them through a temporary scheduled task owned by the console user allows winget to resolve correctly and install the app in that user’s profile. Because scheduled-task completion does not reliably convey winget’s result, installations should be verified with Get-AppxPackage -AllUsers rather than uninstall registry keys, which do not track MSIX Store packages. For genuinely machine-wide deployment, administrators can download and provision MSIX packages with Add-AppxProvisionedPackage, but this requires licensing permissions and hosted package files. Fleet’s script-only packages, uninstall and post-install scripts, labels, and GitOps configuration can package this workflow into auditable self-service tiles, while a generator can create the repeated scripts and YAML from a Store ID, display name, and MSIX package name.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.