-
Notifications
You must be signed in to change notification settings - Fork 904
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
Cancel installation when not elevated #3582
Comments
That would be a user decision. This is why the message, and the prompt, are there. |
A user decision on this step only creates unnecessary problems. |
Which problems does it create?
There are instances where Chocolatey CLI can be and are used without running in an elevated session. If there was an option, then users would have to turn it off and on again, if they were using it. Or we would need to implement options that you could add to the command line to switch it off for that one run. This is a lot of extra work for very little extra gain by a small handful of users. Software should not always make guesses at what the user intended to do. If you are using any open-source tool, you need to ensure you are using it in the correct context.
I disagree. |
Checklist
Is Your Feature Request Related To A Problem? Please describe.
Using Sudo to elevate command shell.
I'm using gsudo for a while to elevate the command shell, also with 24H2 windows has its own sudo feature.
Chocolatey usualy just get a error message and installs the software anyways.
FM: "Chocolatey detected you are not running from an elevated command shell"
This message is in a very unobtrusive color and does not need to be confirmed individually.
Describe The Solution. Why is it needed?
An Option to configure how to handle this situation.
There are two Option that would be viable.
Additional Context
No response
Related Issues
No response
The text was updated successfully, but these errors were encountered: