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.

Sign up for GitHub

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

Jump to bottom

Add option to launch every Terminal session as administrator #10791

Closed
timonsku opened this issue Jul 25, 2021 · 3 comments
Closed

Add option to launch every Terminal session as administrator #10791

timonsku opened this issue Jul 25, 2021 · 3 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@timonsku
Copy link

Description of the new feature/enhancement

Motivation:
Most of the time I want my terminal to be elevated/run as administrator. I close and open the app many times a day, so always needing to go through the shortcut first is cumbersome. Also I can not do that if I want to open a terminal window via the right click menu in Explorer which is what I do most of the time so I always need to have an elevated session and a non-elevated session running which becomes really annoying and hard to keep track off.

Solution:
I want a setting that forces every Terminal window to be run as administrator, no matter how or where I start it from.

Proposed technical implementation details (optional)

Afaik an app can request to be launched as admin if it can't function without elevated rights. I'm not sure if that behaviour is part of the Win32 API or somehow baked into a binary but if it is switchable then I would love to have that as an option in the Terminal settings.
@timonsku timonsku added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jul 25, 2021
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jul 25, 2021
@zadjii-msft
Copy link
Member

You'll probably be wanting #632, with a spec in progress at #8455 and a draft PR over in #8514.

/dup #632

@ghost
Copy link

ghost commented Jul 26, 2021

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Jul 26, 2021
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jul 26, 2021
@timonsku
Copy link
Author

ah thanks! I searched but didn't find that one

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@timonsku @zadjii-msft