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 doesn't work with elevation #11564

Closed
hez2010 opened this issue Oct 21, 2021 · 2 comments
Closed

Default terminal doesn't work with elevation #11564

hez2010 opened this issue Oct 21, 2021 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@hez2010
Copy link

hez2010 commented Oct 21, 2021 •
edited
Loading

Windows Terminal version (or Windows build number)

Windows Terminal: 1.11.2921.0
Windows: 10.0.22483.1000

Other Software

No response

Steps to reproduce

  1. Set Windows Terminal as default conhost
  2. Run a batch script file with administrator

Expected Behavior

The batch script will be executed with Windows Terminal

Actual Behavior

The batch script was executed with cmd
@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 21, 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 Oct 21, 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 Oct 21, 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 Oct 21, 2021
@gerardog gerardog mentioned this issue Nov 9, 2021
Closed
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
@hez2010 @zadjii-msft