-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Cannot remove winget source without admin rights #4562
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Open similar issues:
|
Modifying WinGet sources requires administrator on the device. IT organizations can disable the "msstore" source using Group Policy which effectively removes it from the search path. Based on what I see in the output from Can you share output requesting source or package level agreements for something from the "msstore" source? Verbose logs would also help. You can append "--verbose-logs --logs" to enable verbose logging and open the directory where the logs are contained. |
afaik my company doesn't have a policy regarding winget configured at all ![]() WinGet-2024-06-18-18-16-15.326.log
this is the problem, if i could just disable/remove the source as user (without admin) there would be no problem |
From the logs you shared:
So the source agreements are not an issue, but the package agreements are. You can accept them by passing the If you want to install from the winget source without having to add |
i didn't know there are 2 kinds of agreements in winget, but still i'm confused why do i have to agree to something when winget picks msstore source, but not when it picks winget source? when we use the analogy of the microsoft store gui, if i would click install it wouldn't prompt me to agree to something also where can i inspect the package agreement i'm supposed to agree to? in my screenshot above i only see a link to an open source license of python (why would i need to explicitly agree to that through winget, i can download it with brew or apt without any prompts) and terms of transaction, seizure warning and store license terms, none of the 3 seem to be package specific i know that i can provide the exact winget id (or even specify --id), but the point of this is not that i am unable to install it, but the usability is significantly worse, compare |
I believe in this case the agreements are the MS Store Terms of Transaction and License Terms. If you think of the GUI, you are agreeing to them when you click on Install. Since this is specific to the MS Store, you don't see it with the winget source. I don't know why the Store has those as package agreements and not source agreements, though. (Speculating: maybe a legal requirement to show the terms at the time of installation?) In the winget source some packages may have agreements in the future, but that will depend on each package publisher.
You can do just
Correct |
well on all the corporate machines Microsoft Store App is blocked (if you open it it says the app is blocked by admin), so i shouldn't download anything from there anyway this brings me back to the initial point, why is admin required to execute allowing users to choose their sources is a good thing no? i mean i could go to python website and download & install it manually as long as it doesn't require admin, in this case the source would be a website, how is it differently or more dangerous to add/remove a source in winget? it seems to me that winget imposes an artificial barrier that is unnecessary upon it's user, why not add the sources to the settings.json to be edited by user (for user scoped installs)? is there room for consideration to improve this usability wise or is this a dead end and i have to bite the bullet in the future? |
Adding a source can be dangerous because it could make it so that I don't know the argument to have removing a source require admin. @denelon ? Although in your case it wouldn't matter because you have a Group Policy set to always enable the msstore source, and that overrides manual deletion. You can see it in the |
ok now i understand, thanks for taking the time to explain
i totally missed that, what a bummer, our it department seems to be a little clueless, because it enforces that i download from msstore using winget, but then blocks the msstore app and advises us to not install store apps... anyway i will need to contact them and hope they can sort this out, i think this can be closed |
Brief description of your issue
i'm on a corporate windows machine and have no admin rights, microsoft store is blocked and i cannot/am not allowed to agree to msstore package agreement
i want to install some apps from winget, but whenever winget finds something from msstore it fails, this results in always having to use
-s winget
for search and install subcommandsthe issue is that it's currently not possible to remove a winget source such as msstore without admin rights
Steps to reproduce
Expected behavior
removing winget source for the current user should be possible without admin rights, winget sources should be per user and not system wide
Actual behavior
currently not possible without admin rights
Environment
The text was updated successfully, but these errors were encountered: