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

Open administrator shell in the same Windows Terminal session #14304

Closed
YevheniiPokhvalii opened this issue Oct 29, 2022 · 3 comments
Closed

Open administrator shell in the same Windows Terminal session #14304

YevheniiPokhvalii opened this issue Oct 29, 2022 · 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

@YevheniiPokhvalii
Copy link

I don't always need to run Windows Terminal as admin since I use WSL mostly.
But when I open admin PowerShell session in Windows Terminal, first of all, it shows me a GUI "User account control" window and secondly, it opens a new Windows Terminal session.

Is it possible to implement a feature to start admin shell the way Linux does it with password prompt and without any GUI pop-ups?
is it possible to implement a feature to start admin CMD/PowerShell session in the same non-admin Windows Terminal session?
@YevheniiPokhvalii YevheniiPokhvalii added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Oct 29, 2022
@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 Oct 29, 2022
@j4james
Copy link
Collaborator

j4james commented Oct 29, 2022

If I've understood you correctly, what you're asking for is know as "mixed elevation" - you've got an unelevated Windows Terminal process from which you want to open an elevated tab. See issue #1032 for an explanation of why that's not supported.

@zadjii-msft
Copy link
Member

Yep, /dup #1032.

@zadjii-msft zadjii-msft closed this as not planned Won't fix, can't repro, duplicate, stale Oct 31, 2022
@ghost
Copy link

ghost commented Oct 31, 2022

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 Oct 31, 2022
@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 Oct 31, 2022
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
3 participants
@j4james @zadjii-msft @YevheniiPokhvalii