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

Admin shortcuts do not open in Terminal Preview #14043

New Issue
Closed
opened 2026-01-31 03:59:14 +00:00 by claunia · 10 comments
claunia commented 2026-01-31 03:59:14 +00:00
Owner
Copy Link

Originally created by @obrobrio2000 on GitHub (May 29, 2021).

Note

: 📌 Pinned comment: https://github.com/microsoft/terminal/issues/10276#issuecomment-852215012

Windows Terminal version (or Windows build number)

10.0.21390.1, 1.9.1445.0

Other Software

No response

Steps to reproduce

  1. Set WT Preview as the default terminal application following the steps described here;
  2. Launch CMD/PS as administrator.

Expected Behavior

Elevated CMD/PS should respect the default terminal choice just like when non-elevated.

Actual Behavior

CMD/PS open in Terminal only if launched with standard privileges. When launched as administrator they still open in Console Host.
Feedback Hub link: https://aka.ms/AAcrn4y

Originally created by @obrobrio2000 on GitHub (May 29, 2021). <hr> > **Note**: 📌 Pinned comment: **https://github.com/microsoft/terminal/issues/10276#issuecomment-852215012** <hr> ### Windows Terminal version (or Windows build number) 10.0.21390.1, 1.9.1445.0 ### Other Software _No response_ ### Steps to reproduce 1) Set WT Preview as the default terminal application following the steps described [here](https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-9-release/); 2) Launch CMD/PS as administrator. ### Expected Behavior Elevated CMD/PS should respect the default terminal choice just like when non-elevated. ### Actual Behavior CMD/PS open in Terminal only if launched with standard privileges. When launched as administrator they still open in Console Host. Feedback Hub link: https://aka.ms/AAcrn4y
claunia commented 2026-01-31 03:59:16 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 1, 2021):

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.

This is tracked internally at MSFT:39500755. There's a decent amount of platform work that will be needed for this.

@DHowett commented on GitHub (Jun 1, 2021): 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. This is tracked internally at MSFT:39500755. There's a decent amount of platform work that will be needed for this.
claunia commented 2026-01-31 03:59:16 +00:00
Author
Owner
Copy Link

@xparadoxical commented on GitHub (Mar 29, 2023):

just bumped my head into gerardog/gsudo#117 and, by extension, this. 😔

@xparadoxical commented on GitHub (Mar 29, 2023): just bumped my head into gerardog/gsudo#117 and, by extension, this. 😔
claunia commented 2026-01-31 03:59:17 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 28, 2023):

As a 2023 status update: This still doesn't seem to be supported by the platform. We're not sure when the COM team will be able to fix this.

edit to include some search phrases: defterm elevated admin COM handoff defapp

@zadjii-msft commented on GitHub (Aug 28, 2023): As a 2023 status update: This still doesn't seem to be supported by the platform. We're not sure when the COM team will be able to fix this. edit to include some search phrases: defterm elevated admin COM handoff defapp
claunia commented 2026-01-31 03:59:17 +00:00
Author
Owner
Copy Link

@stdin82 commented on GitHub (Dec 3, 2023):

As a 2023 status update: This still doesn't seem to be supported by the platform. We're not sure when the COM team will be able to fix this.

I don't think this should be implemented (fixed) before providing a way to detect if the current cmd or powershell is running within Terminal
e.g. when a batch script or powershell script is launched from explorer, WT_SESSION/WT_PROFILE are not set
currently, "Run as administrator" is the only reliable way to avoid Terminal, which is good (well, unless UAC is disabled, then all opens in Terminal)

@stdin82 commented on GitHub (Dec 3, 2023): > As a 2023 status update: This still doesn't seem to be supported by the platform. We're not sure when the COM team will be able to fix this. I don't think this should be implemented (fixed) before providing a way to detect if the current cmd or powershell is running within Terminal e.g. when a batch script or powershell script is launched from explorer, WT_SESSION/WT_PROFILE are not set currently, "Run as administrator" is the only reliable way to avoid Terminal, which is good (well, unless UAC is disabled, then all opens in Terminal)
claunia commented 2026-01-31 03:59:17 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Dec 4, 2023):

the only reliable way to avoid Terminal,

We're going to fix this in the Windows platform eventually, at which point it will not be reliable at all.
There are much more reliable methods, which are officially supported.

  1. Launch conhost directly.
  2. In any of the three settings pages available for this, set the "Default Terminal" application back to "Windows Console Host". This will persist across upgrades, and is in fact the intended way to "avoid" Terminal.
@DHowett commented on GitHub (Dec 4, 2023): > the only reliable way to avoid Terminal, We're going to fix this in the Windows platform eventually, at which point it will not be reliable at all. There are much more reliable methods, which are officially supported. 1. Launch `conhost` directly. 2. In any of the three settings pages available for this, set the "Default Terminal" application back to "Windows Console Host". This will persist across upgrades, and is in fact the intended way to "avoid" Terminal.
claunia commented 2026-01-31 03:59:17 +00:00
Author
Owner
Copy Link

@Echostorm44 commented on GitHub (Aug 5, 2024):

A year later, any update on this? Still an issue in VS2022 and Windows 11.

@Echostorm44 commented on GitHub (Aug 5, 2024): A year later, any update on this? Still an issue in VS2022 and Windows 11.
claunia commented 2026-01-31 03:59:17 +00:00
Author
Owner
Copy Link

@michalsteyn commented on GitHub (Aug 23, 2024):

This issue has now been open for over 3 years. Shocking this is taking soo long. For Dev's running VS 2022 as Admin, this is really a pain.

@michalsteyn commented on GitHub (Aug 23, 2024): This issue has now been open for over 3 years. Shocking this is taking soo long. For Dev's running VS 2022 as Admin, this is really a pain.
claunia commented 2026-01-31 03:59:17 +00:00
Author
Owner
Copy Link

@ayanamist commented on GitHub (Sep 14, 2024):

I see some workarounds (in chinese), maybe help:
https://t.me/yscschan/7010
https://t.me/yscschan/7014?single

@ayanamist commented on GitHub (Sep 14, 2024): I see some workarounds (in chinese), maybe help: https://t.me/yscschan/7010 https://t.me/yscschan/7014?single
claunia commented 2026-01-31 03:59:17 +00:00
Author
Owner
Copy Link

@PogromistDev commented on GitHub (Nov 10, 2024):

Visual studio developer command prompt runs in terminal only if you already run terminal as administrator and then executed "Developer Command Prompt for VS 2022" .lnk file or just passed its command directly
%comspec% /k "C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\Tools\VsDevCmd.bat" -arch=amd64

@PogromistDev commented on GitHub (Nov 10, 2024): Visual studio developer command prompt runs in terminal only if you already run terminal as administrator and then executed "Developer Command Prompt for VS 2022" .lnk file or just passed its command directly `%comspec% /k "C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\Tools\VsDevCmd.bat" -arch=amd64`
claunia commented 2026-01-31 03:59:18 +00:00
Author
Owner
Copy Link

@Dovias commented on GitHub (Apr 18, 2025):

I see some workarounds (in chinese), maybe help: https://t.me/yscschan/7010 https://t.me/yscschan/7014?single

For anyone wondering how to make this work for now until this gets fixed, you can follow my guide (which is based on the yscshan's findings) which explains how to make Windows Terminal to open when executing PowerShell or Command Prompt executable as an administrator:
https://gist.github.com/Dovias/75338df14f3fbab19b72eefb7fb9b884

https://github.com/user-attachments/assets/ae4a8ee9-eff4-4846-a42e-898191cf179a

@Dovias commented on GitHub (Apr 18, 2025): > I see some workarounds (in chinese), maybe help: https://t.me/yscschan/7010 https://t.me/yscschan/7014?single For anyone wondering how to make this work for now until this gets fixed, you can follow my guide (which is based on the yscshan's findings) which explains how to make Windows Terminal to open when executing PowerShell or Command Prompt executable as an administrator: https://gist.github.com/Dovias/75338df14f3fbab19b72eefb7fb9b884 https://github.com/user-attachments/assets/ae4a8ee9-eff4-4846-a42e-898191cf179a
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 Area-DefApp Culprit-Centennial Issue-Bug Priority-1 Product-Terminal Tracking-External
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#14043
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?