-
Notifications
You must be signed in to change notification settings - Fork 5k
Validation is running manifests with elevationProhibited in an elevated context #72224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
We should fix this bug and leave the key in the manifest so the user experience works correctly. Unless I'm interpreting this incorrectly. |
You're understanding correctly (it was kind of hard to explain, sorry). I don't want to remove the key, but if this fix is super complicated I wondered if we should remove it temporarily since Spotify is currently entirely borked. |
Or perhaps someone can manually validate and merge spotify |
Which PR is spotify? |
I think the error I get is related to this issue:
(I use WingetUI, which is an UI for winget; never used winget alone; but I don't think that matters). |
@jedieaston - has this been resolved? See https://github.com/microsoft/winget-pkgs/pull/150294/files |
Close with reason: Resolved; Ref: #204908 |
As of winget 1.3, winget now supports a
ElevationRequirement
key for installers, which can tell the client to error out if a user tries to run an installer that will fail when ran as an administrator (microsoft/winget-cli#2126).The validation service doesn't seem to respect this, and is running installers in an elevated context that have
ElevationRequirement: elevationProhibited
set. Here's an example using Spotify (#72166):InstallationClient log:
winget install
log:This is currently blocking Spotify from being updated, so if this is going to be a painful fix I can remove the
ElevationRequirement
key until it's resolved.The text was updated successfully, but these errors were encountered: