starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

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

New Issue
Closed
opened 2026-01-31 07:02:58 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 07:02:58 +00:00
Owner
Copy Link

Originally created by @fuchanghao on GitHub (Jun 14, 2023).

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.

Originally created by @fuchanghao on GitHub (Jun 14, 2023). ### 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.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 07:02:58 +00:00
claunia commented 2026-01-31 07:02:59 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 14, 2023):

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 commented on GitHub (Jun 14, 2023): 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
claunia commented 2026-01-31 07:02:59 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Jun 14, 2023):

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[bot] commented on GitHub (Jun 14, 2023): 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!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20083
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?