Skip to content
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

Winget not asking for privilege escalation for some packages #1538

Closed
FurtadoPires opened this issue Oct 1, 2021 · 2 comments · Fixed by #2126
Closed

Winget not asking for privilege escalation for some packages #1538

FurtadoPires opened this issue Oct 1, 2021 · 2 comments · Fixed by #2126
Labels
Issue-Feature This is a feature request for the Windows Package Manager client.
Milestone

Comments

@FurtadoPires
Copy link

Brief description of your issue

Some applications like Libreoffice can't be installed with windows terminal in user mod, because the terminal doesn't ask to escalate privilege during the install process (crashing with the code 1603)

If it's executed using Powershell as admin, the install process silently finishes in the background but the terminal window remains stuck with the initiating install message.

Steps to reproduce

winget upgrade LibreOffice.LibreOffice

Environment

[winget --info]
Windows: Windows.Desktop v10.0.19043.1237
Pacote: Microsoft.DesktopAppInstaller v1.16.12653.0

Registros: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

Links
-------------------------------------------------------------------------------
Política de Privacidade https://aka.ms/winget-privacy
Contrato de Licença     https://aka.ms/winget-license
Avisos de Terceiros     https://aka.ms/winget-3rdPartyNotice
Home page               https://aka.ms/winget
Termos da Windows Store https://www.microsoft.com/en-us/storedocs/terms-of-sale
Windows Package Manager version
Windows: Windows.Desktop version
Package: Microsoft.DesktopAppInstaller version


@ghost ghost added the Needs-Triage Issue need to be triaged label Oct 1, 2021
@denelon
Copy link
Contributor

denelon commented Oct 1, 2021

We have a couple of issues related to this ask.

These are prerequisites intended to address this scenario. We still have some work to do in the client for this, but the schema work has been implemented, and the support for the v1.1 manifest schema is in progress on the validation pipelines. I'll use this ask to represent the work on the client side.

@denelon denelon added Issue-Bug It either shouldn't be doing this or needs an investigation. Issue-Feature This is a feature request for the Windows Package Manager client. and removed Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage Issue need to be triaged labels Oct 1, 2021
@denelon denelon added this to the v.Next-Client milestone Oct 1, 2021
@denelon denelon modified the milestones: v.Next-Client, v1.3-Client Dec 1, 2021
@denelon
Copy link
Contributor

denelon commented Dec 1, 2021

We've added the key to the schema to indicate when a package requires or prohibits elevation. This work item will be used to track the work to provide the information to the user. It will give an error for user mode if the package requires elevation, and it will give an error for admin mode if the package prohibits elevation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature This is a feature request for the Windows Package Manager client.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants