starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Can't launch wt.exe elevated (from explorer UI) #8293

New Issue
Closed
opened 2026-01-31 01:25:33 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 01:25:33 +00:00
Owner
Copy Link

Originally created by @ijprest on GitHub (May 20, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.778]
Windows Terminal version (if applicable): 1.0.1401.0

Steps to reproduce

##Scenario 1:

  1. Press Win+R to launch the "Run" dialog.
  2. Type "wt" and press Ctrl+Shift+Enter.

or

##Scenario 2:

  1. Press 'Win' to open the start menu.
  2. Type "wt" and press Ctrl+Shift+Enter.

Expected behavior

In both cases, I expect an elevated instance of Windows Terminal to start.

Actual behavior

##Scenario 1:

  • Windows Terminal Launches, but it's not elevated.

##Scenario 2:

  • I get this error message-box:
[Window Title]
C:\Users\ijprest\AppData\Local\Microsoft\WindowsApps\wt.exe

[Content]
C:\Users\ijprest\AppData\Local\Microsoft\WindowsApps\wt.exe

The file cannot be accessed by the system.

[OK]
Originally created by @ijprest on GitHub (May 20, 2020). # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18362.778] Windows Terminal version (if applicable): 1.0.1401.0 ``` # Steps to reproduce ##Scenario 1: 1. Press Win+R to launch the "Run" dialog. 2. Type "wt" and press Ctrl+Shift+Enter. **or** ##Scenario 2: 1. Press 'Win' to open the start menu. 2. Type "wt" and press Ctrl+Shift+Enter. # Expected behavior In both cases, I expect an elevated instance of Windows Terminal to start. # Actual behavior ##Scenario 1: - Windows Terminal Launches, but it's not elevated. ##Scenario 2: - I get this error message-box: ```none [Window Title] C:\Users\ijprest\AppData\Local\Microsoft\WindowsApps\wt.exe [Content] C:\Users\ijprest\AppData\Local\Microsoft\WindowsApps\wt.exe The file cannot be accessed by the system. [OK] ```
claunia added the Resolution-Duplicate label 2026-01-31 01:25:33 +00:00
claunia commented 2026-01-31 01:25:34 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 21, 2020):

Agree.

Now Crtl-Shift click on the taskbar icon does NOT work either when you have to elevate with a local admin account.

Windows build number: Microsoft Windows [Version 10.0.18363.836]
Windows Terminal version (if applicable): 1.0.1401.0

See the below error screenshot I get after being prompted twice to elevate permissions:

Error

@ghost commented on GitHub (May 21, 2020): Agree. Now Crtl-Shift click on the taskbar icon does NOT work either when you have to elevate with a local admin account. ``` Windows build number: Microsoft Windows [Version 10.0.18363.836] Windows Terminal version (if applicable): 1.0.1401.0 ``` See the below error screenshot I get after being prompted twice to elevate permissions: ![Error](https://user-images.githubusercontent.com/16409467/82567629-9e5d7980-9b4b-11ea-9d91-8763dd8fb26b.png)
claunia commented 2026-01-31 01:25:34 +00:00
Author
Owner
Copy Link

@ErikPlachta commented on GitHub (Jun 4, 2020):

I have this same issue, and I am able to get it to work if I hold ctrl + shift and click the icon.

@ErikPlachta commented on GitHub (Jun 4, 2020): I have this same issue, and I am able to get it to work if I hold ctrl + shift and click the icon.
claunia commented 2026-01-31 01:25:34 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Jun 4, 2020):

Why don't you just right click it? Wouldn't that be easier? I just have it pinned to the taskbar and rightclick "Launch as Administrator" (this works from Start Menu too). I tested

##Scenario 2

and that worked for me as well (but is inconvenient way to launch for me.)

##Scenario 1

does indeed not launch an elevated Windows Terminal.

The only difference between OP and my tests is the Windows build: [Version 10.0.19041.264]

@WSLUser commented on GitHub (Jun 4, 2020): Why don't you just right click it? Wouldn't that be easier? I just have it pinned to the taskbar and rightclick "Launch as Administrator" (this works from Start Menu too). I tested > ##Scenario 2 and that worked for me as well (but is inconvenient way to launch for me.) > ##Scenario 1 does indeed not launch an elevated Windows Terminal. The only difference between OP and my tests is the Windows build: [Version 10.0.19041.264]
claunia commented 2026-01-31 01:25:34 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 16, 2020):

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

/dup #4217 #4766

@zadjii-msft commented on GitHub (Jun 16, 2020): Thanks for the bug report! This is actually already being tracked by another issue on our repo - please refer to #4217 for more discussion. /dup #4217 #4766
claunia commented 2026-01-31 01:25:34 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 16, 2020):

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 commented on GitHub (Jun 16, 2020): 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 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#8293
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?