# WinGet does not work for multiple users across the org — retained record

> Retained reddit record from reddit:sysadmin.

Canonical: https://highsignal.app/data/records/5bb2131337e5de74

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:sysadmin)  published 2026-09-28 12:37 ingested 2026-09-29 02:42

[original source ↗](https://www.reddit.com/r/sysadmin/comments/1wsdgab/winget_does_not_work_for_multiple_users_across/)

## retained text



```
We deploy apps from Company Portal, and recently-ish we started deploying some (or rather, one as of right now) of them through WinGet. However, this has recently failed on a number of clients, without any clear explanation as to why. We're up to 6 clients or so, but we expect this to increase, as more people report problems.

The installer itself uses a PS Script to get the Git application. The exact line being run is this (varies by system architecture, naturally):

`Start-Process -Filepath "winget.exe" -ArgumentList "install --id Git.Git -e --source winget --silent --accept-source-agreements --architecture x64 --scope user" -NoNewWindow -Wait` 

In most cases, the app deploys as it should, but for some users the install fails, all with the same error:

`0x8a15000f: Data required by the source is missing`

We've looked through log files, and the usual problem seems to be that the winget instance cannot find the DesktopAppInstaller package, and throws an error. This happens both manually and with the Company Portal script.

So, we've tested... most things people recommend, really:

* Reset the sources with `winget source reset`
* Attempted to reinstall the DesktopAppInstaller bundle with `Get-AppxBundle Microsoft.DesktopAppInstaller* | Remove-AppxBundle` followed by a reinstall with `Install-AppxBundle`
* Tried `Repair-WingetPackageManager` to repair the WinGet instance (which from my knowledge does the same as reinstalling the AppxBundle)

The one thing that seems to work is running WinGet from an elevated PS terminal, which seems to be able to connect to WinGet as normal. However, getting WinGet to work in a admin context, and installing to system rather than user, seems to be finicky with Intune, and we'd probably push an MSI installer before trying that.

Worth noting: We recently pushed an configuration policy that only allows Microsoft Store apps to be installed on the system. Though, this seems largely unrelated to WinGet as a whole. The policy was pushed in May and we did not have any problems before last week. We've also tested with a couple users affected by the policy, and WinGet works on clients, so this isn't a policy issue.

Anyone here who's touched upon the same problems, and managed to fix them? Did you solve it, or were the end users forced to reinstall? We'd prefer to find a fix, preferrably something we could push through Intune, so that we can continue deploying WinGet apps (makes version control a bit simpler...), but as noted, we can also push this as an MSI in the meantime. We'd rather not reinstall clients over something like this, given that IT and some devs are the only ones using WinGet.
```



document fetched 2026-09-29 00:37 · canonical https://reddit.com/r/sysadmin/comments/1wsdgab/winget_does_not_work_for_multiple_users_across
