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

Running any cli app as admin opens it in Windows Console Host. #10682

Closed
rounk-ctrl opened this issue Jul 16, 2021 · 2 comments
Closed

Running any cli app as admin opens it in Windows Console Host. #10682

rounk-ctrl opened this issue Jul 16, 2021 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@rounk-ctrl
Copy link

Windows Terminal version (or Windows build number)

10.0.22000.71, 1.10.1933.0

Other Software

No response

Steps to reproduce

Set default terminal application as Windows Terminal.
Open any cli app(cmd, powershell, wsl) as admin.
See that it launches in conhost not windows terminal.

Expected Behavior

Opens the app in Windows Terminal.

Actual Behavior

Opens in Windows Console Host.
@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 16, 2021
@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 Jul 16, 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 16, 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 16, 2021
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
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 @rounk-ctrl