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

Trying elevated WT does not open #20056

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

Originally created by @mwpowellhtx on GitHub (Jun 9, 2023).

Windows Terminal version

1.17.11461.0

Windows build number

10.0.19041.685

Other Software

I've been opening WT elevated for quite some time and it has been working fine up until today. It was working just yesterday. Now it seems it will not open. Prompts me for the elevated, but no window is opening. Actually, it has also been prompting me unknown program when I do, not sure why that is either, may or may not be related. Having scanned some of the tech forums as well, some suggest that, this is the point of WT, that you need Administrator access to run it, so do not need to elevate it, but this is inaccurate. Some processes you still need an elevated CL in order to do anything with them sometimes, especially if you are doing anything process level, which I sometimes do. So force of habit, I just generally open it that way.

Steps to reproduce

Simply this, CTRL+SHIFT click the taskbar, or CTRL+SHIFT+WIN+(pos) depending on the position.

Expected Behavior

I expect the WT to open elevated with the first configured CL.

Actual Behavior

Apparently, nothing. Ghosted. No window whatsoever is being opened elevated.

Originally created by @mwpowellhtx on GitHub (Jun 9, 2023). ### Windows Terminal version 1.17.11461.0 ### Windows build number 10.0.19041.685 ### Other Software I've been opening WT elevated for quite some time and it has been working fine up until today. It was working just yesterday. Now it seems it will not open. Prompts me for the elevated, but no window is opening. Actually, it has also been prompting me _unknown program_ when I do, not sure why that is either, may or may not be related. Having scanned some of the tech forums as well, some suggest that, _this is the point of WT, that you need Administrator access to run it, so do not need to elevate it_, but this is inaccurate. Some processes you still need an elevated CL in order to do anything with them sometimes, especially if you are doing anything process level, which I sometimes do. So force of habit, I just generally open it that way. ### Steps to reproduce Simply this, `CTRL+SHIFT` click the taskbar, or `CTRL+SHIFT+WIN+(pos)` depending on the position. ### Expected Behavior I expect the WT to open elevated with the first configured CL. ### Actual Behavior Apparently, nothing. Ghosted. No window whatsoever is being opened elevated.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 07:02:04 +00:00
claunia commented 2026-01-31 07:02:05 +00:00
Author
Owner
Copy Link

@thomas-berg commented on GitHub (Jun 12, 2023):

I experience the same thing, I added my crash report to this issue: https://github.com/microsoft/terminal/issues/15526

@thomas-berg commented on GitHub (Jun 12, 2023): I experience the same thing, I added my crash report to this issue: https://github.com/microsoft/terminal/issues/15526
claunia commented 2026-01-31 07:02:05 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jun 14, 2023):

Hi @mwpowellhtx. Thanks for filing! We're going to mark this as a /dup of #15526. We'll revisit that one in a bit. Thanks again!

@carlos-zamora commented on GitHub (Jun 14, 2023): Hi @mwpowellhtx. Thanks for filing! We're going to mark this as a /dup of #15526. We'll revisit that one in a bit. Thanks again!
claunia commented 2026-01-31 07:02:05 +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!
claunia commented 2026-01-31 07:02:05 +00:00
Author
Owner
Copy Link

@mwpowellhtx commented on GitHub (Jun 14, 2023):

Cautiously optimistic, sounds promising. Thanks!

@mwpowellhtx commented on GitHub (Jun 14, 2023): Cautiously optimistic, sounds promising. Thanks!
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#20056
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?