[Package Issue]: Spotify.Spotify Supports Machine-Scope Installation (But WinGet Doesn't Realize) #210448
Open
2 tasks done
Labels
Issue-Bug
It either shouldn't be doing this or needs an investigation.
Needs-Triage
This work item needs to be triaged by a member of the core team.
Please confirm these before moving forward
Category of the issue
Installation issue.
Brief description of your issue
I just recently found out that Spotify, a package notorious (I guess?) for not working out of elevated sessions, actually supports machine-scope installation, which does work when run as administrator. However, WinGet not only doesn't recognize this with the
--scope
parameter, but also prevents one from manually using it with--override
due to theelevationProhibited
flag on the package.Spotify will normally refuse to install from an administrator context (for some reason), but if the wizard is called with the arguments
/extract "C:\Program Files\Spotify"
, it will work.Steps to reproduce
Open an elevated shell
winget install Spotify.Spotify
(See that it fails—"The installer cannot be run from an administrator context.")
winget install Spotify.Spotify --scope machine
(See that it fails—"No applicable installer found; see logs for more details.")
winget install Spotify.Spotify --override '/extract "C:\Program Files"'
(See that it fails—"The installer cannot be run from an administrator context.")
winget download Spotify.Spotify
&<Path to downloaded installer> /extract "C:\Program Files\Spotify
(See that it works from the elevated shell)
Actual behavior
WinGet does not recognize a valid package with the
--scope machine
flag, nor does it allow users to manually use the arguments for admin-friendly machine-scope installation, preëmptively blocking the wizard on the belief it cannot be run from an administrator context.Expected behavior
WinGet should recognize the machine-scope installation option and also not block users from doing it manually.
Environment
Screenshots and Logs
No response
The text was updated successfully, but these errors were encountered: