Scope and Import #5114
Unanswered
AdreKiseque
asked this question in
Q&A
Replies: 1 comment
-
Hi @AdreKiseque. I think the best thing to do for the first question is to look at the package you are attempting to install and potentially overwrite it with the relevant settings. For example, if the package has the "installBehavior": {
"portablePackageUserRoot": "C:/Users/FooBar/Packages"
}, I know there are some ongoing discussions for the second one, but I couldn't find the related issue/discussion. A small one that is indirectly related is #3401. Hope this helps. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Bit of a 2-in-1 here, I've noticed WinGet seems to, by default, install many packages into AppData. I personally find this very upsetting. It is my understanding that some programs will install to this location when set to install "for the current user" and otherwise to Program Files when set to install "for all users". Am I correct in my assumption that the
--scope machine
argument is the tool I seek if I wish for programs to be installed to Program Files rather than AppData?Secondly, I've noticed
winget import
doesn't seem to support the--scope
argument. Is there any way to set the option when installing packages through this command?Beta Was this translation helpful? Give feedback.
All reactions