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.

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

Set the Windows Terminal as the “Default terminal applications" not work with administrator privileges. #15546

Closed
fuchanghao opened this issue Jun 14, 2023 · 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

@fuchanghao
Copy link

Windows Terminal version

1.17.11461.0

Windows build number

10.0.19044.3086

Other Software

No response

Steps to reproduce

log in windows 10 as normal user account.

set the Windows Terminal as the “Default terminal applications"

Test1:

create a simple "test.cmd"

cd /d c:\
pause

right click "test.cmd" and choose: "Run as administrator".

Test2:

double-click a cmd file which has “administrator elevation request” codes.

Test3:

log in as system build-in "Administrator" account and do the Test1 and Test2 again.

Test4:

1.log in as system build-in "Administrator" account.
2.open "Group Policy" and enable "User Account Control: Admin Approval Mode for the Built-in Administrator account" : https://learn.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/user-account-control-admin-approval-mode-for-the-built-in-administrator-account
3.Do the Test1 and Test2 again.

Expected Behavior

When I right click "test.cmd" and choose: "Run as administrator" or run a cmd file which has “administrator elevation request” codes.

After the UAC pop-up, It will open an "Administrator: Command Prompt" Tab on Windows Terminal to run the codes.

Actual Behavior

For Test1 and Test2:

It opens a conhost.exe and run the codes.

For Test3

It opens an "Administrator: Command Prompt" Tab on Windows Terminal to run the codes.

For Test4:

It opens a conhost.exe and run the codes again.

I don't know why the same “Default terminal applications" setting cause different results.

@fuchanghao fuchanghao added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 14, 2023
@zadjii-msft
Copy link
Member

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #10276 for more discussion.

/dup #10276

@zadjii-msft zadjii-msft closed this as not planned Won't fix, can't repro, duplicate, stale Jun 14, 2023
@microsoft-github-policy-service
Copy link
Contributor

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!

@microsoft-github-policy-service microsoft-github-policy-service bot 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 labels Jun 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

No branches or pull requests

2 participants