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

Default terminal settings are not respected when running command line apps as admin. #12726

Closed
dongle-the-gadget opened this issue Mar 20, 2022 · 2 comments
Closed

Default terminal settings are not respected when running command line apps as admin. #12726

dongle-the-gadget opened this issue Mar 20, 2022 · 2 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@dongle-the-gadget
Copy link

Windows Terminal version

1.13.10395.0

Windows build number

10.0.22579.1

Other Software

No response

Steps to reproduce

Run either "cmd.exe", "powershell.exe", "pwsh.exe", "wsl.exe", or any command line apps as an administrator.
Or in 22579, right click Start button (Win + X) and choose Windows PowerShell (Admin).

Expected Behavior

Running command line apps as administrator respects the user's default terminal application choices.

Actual Behavior

The legacy conhost always appears, even if the user chooses Windows Terminal to be their default terminal application.
@dongle-the-gadget dongle-the-gadget added the Issue-Bug It either shouldn't be doing this or needs an investigation. label Mar 20, 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 Mar 20, 2022
@zadjii-msft
Copy link
Member

Unfortunately, this is by design right now. Due to a limitation in the app platform it is impossible for Terminal to be "discovered" as the handler when the application that needs a terminal is running elevated.

/dup #10276

@ghost
Copy link

ghost commented Mar 21, 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 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 Mar 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. 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
@zadjii-msft @dongle-the-gadget