Kaleb Luedtke

@quan1232004 - Are you still experiencing this issue with the [latest release](https://github.com/microsoft/winget-cli/releases/latest) of the cli?

Looking at the code, I see this comment: ``` // TODO: There was a bug in InstallService where admin user is incorrectly identified as not admin, // causing false access...

> We could add another YAML key to indicate that the scope arguments either aren't properly supported This probably wouldn't even need a new key. It would just need `Scope`...

> > I think for cases where it depends on whether it runs as admin or not, we could set elevationRequirement=elevationProhibited for user scope and elevationRequirement=requiresElevation for machine scope; >...

> > I dont think that works in this case. Git.git doesn’t depend on elevation status. If an administrator is running the installer - even in a non-elevated context -...

> While in this case, declaring scope as unsupported is sort of hiding the issue. I hadn't considered it that way. That's a good way of looking at it. There...

Does it do the same thing with `winget list -e --id 'Microsoft.PowerShell'` ?

87 is the exit code that's being received from the logitech installer. WinGet is just passing it through. In order to show a success, WinGet expects the exit code `0`...

@denelon - I was correct in my assumption that this wasn't a winget-specific issue, as it was affecting any MSIX installs and any store installs. I'm not sure if you...

I don't have any way to see the actual data of the application that is installed, but WinGet is a bit particular in the data itself. Specifically, because winget uses...