Open IngwiePhoenix opened 1 year ago
@IngwiePhoenix WinGet does work when running in both "user" and "administrator" context. The challenge is really associated with the installers themselves. We've added "requiresElevation" and "prohbitsElevation" as keys that can be added to manifests to help with packages that do not work in those scopes, but we also have challenges when dealing with packages that want to be installed either for a single user or for a machine wide install.
We will take a look at this in the future to see if there is something we can do better here.
Gotcha. Attempting to consolidate what was effectively a "wild west of installation methods" into a package manager truely sounds challenging. Thank you for all the work!
Just wanted to say you can do this now with sudo for Windows - available to Windows Insiders.
I'm running it now:
sudo winget upgrade --all
Running like a champ with zero UAC faff! PRICELESS! :)
Description of the new feature / enhancement
I reinstalled my PC's Windows 10 as part of my annual PC and digital cleaning. This time around, I exported my winget packages and stored it alongside my Windows 10 installer, allowing me to, immediately after getting into the desktop, re-install all my 96 packages.
My first attempt was to run
winget import pkgs.json
, but was surprised to read that winget does not like running from within an admin shell. So I had to sift through an astounding amount of UAC prompts, which certainly sucked.This is why I would like to request a feature to winget to allow importing - or even upgrading - from an elevated shell to avoid UAC spam.
Thanks!
Proposed technical implementation details
No response