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

Provide option to add "Open in Windows Terminal (Admin)" to Explorer context menu #13569

New Issue
Open
opened 2026-01-31 03:46:07 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 03:46:07 +00:00
Owner
Copy Link

Originally created by @TheAndyMac on GitHub (Apr 20, 2021).

Description of the new feature/enhancement

As well as having the option to Open in Windows Terminal as a right-click in Explorer (which should be configurable as discussed in #9902 and #6113 ) it would be really helpful to have a configurable option to ALSO have an "Open in Windows Terminal (Admin)" option to quickly open up Windows Terminal with Admin rights to be able to access those commands which need it.

Proposed technical implementation details (optional)

Add an option in the configuration to enable/disable an "Open in Windows Terminal (Admin)" context menu option.

Originally created by @TheAndyMac on GitHub (Apr 20, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> As well as having the option to Open in Windows Terminal as a right-click in Explorer (which should be configurable as discussed in #9902 and #6113 ) it would be really helpful to have a configurable option to ALSO have an "Open in Windows Terminal (Admin)" option to quickly open up Windows Terminal with Admin rights to be able to access those commands which need it. # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. --> Add an option in the configuration to enable/disable an "Open in Windows Terminal (Admin)" context menu option.
claunia added the Area-SettingsIssue-TaskProduct-TerminalArea-ShellExtension labels 2026-01-31 03:46:07 +00:00
claunia commented 2026-01-31 03:46:08 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 20, 2021):

Yea, we'll make sure to include this in the configuration options. This is technically different than #6111 so I'll leave it open

@zadjii-msft commented on GitHub (Apr 20, 2021): Yea, we'll make sure to include this in the configuration options. This is technically different than #6111 so I'll leave it open
claunia commented 2026-01-31 03:46:08 +00:00
Author
Owner
Copy Link

@Dhyfer1 commented on GitHub (Feb 8, 2023):

It has been 19 months since the creation of this issue and I also need Windows Terminal to be able to run as admin from the context menu. Why is there still no progress on this? or this isn't a priority for the developers behind Windows Terminal?

@Dhyfer1 commented on GitHub (Feb 8, 2023): It has been 19 months since the creation of this issue and I also need Windows Terminal to be able to run as admin from the context menu. Why is there still no progress on this? or this isn't a priority for the developers behind Windows Terminal?
claunia commented 2026-01-31 03:46:08 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 8, 2023):

Indeed, this isn't an immediate priority for us. You'll note that across the repo, there are plenty of older issues, with more upvotes, which are currently a higher priority for us.

If you'd like to help, we'd be happy to help point you in the right direction! This is unfortunately kinda a tricky problem, because we need to solve two problems:

  • We need to add support for the shell context menu code to load our settings model. I don't know if we can do that easily currently.
  • We need to find a way to add settings to configure what our context menu settings should be. What shape do we want these settings to be? contextMenu.showElevatedEntry & contextMenu.showProfilePicker? contextMenu.showElevatedProfilePicker? We need some sort of design for that.
  • Putting nested entries in the menu is non-trivial, https://github.com/microsoft/terminal/issues/6111#issuecomment-1252946834 has some notes. At least I'm not enough of a shell32 guru to know.

Figuring out the first bullet point is probably the hardest part. If you can get our settings loaded in the context menu code, then it's easy1 to add settings to control this.

EDIT from "dumb idea central", some time after 5pm local time:

the shell extension has to be fast. there's that boolean for "you can do slow stuff," but we don't want to use it because win11 already fucked us over

i think parsing appdata, loading json etc is gonna put us over budget

that is, to figure out how to build the shell ext menu from user settings

because we're packaged, we get our own registry. why shouldn't we cache this stuff in our isolated registry? it's way way faster than opening a file on disk, and has near 0 parsing

so if you set contextMenu.showElevatedThing, we set a single DWORD

and we don't need to do the shell(reg.exe) hack, it's all literally just local state

the only real downside is, you gotta launch terminal once after editing settings.json to push the real values in

none of this, "edit settings.json, then right click"

but also, we could store the names/GUIDs/icons of profiles in there too if we really wanted to. Show this profile -> ok we'll "memoize" it. It's not enough to reconstruct the profile from registry, just enough to make a menu item out of it.

so we aren't going into "store profiles in the registry" territory

  1. Of course, naming in software is a Hard problem, but adding settings is easy once you've figured that out 😋 ↩︎

@zadjii-msft commented on GitHub (Feb 8, 2023): Indeed, this isn't an immediate priority for us. You'll note that across the repo, there are plenty of older issues, with more upvotes, which are currently a higher priority for us. If you'd like to help, we'd be happy to help point you in the right direction! This is unfortunately kinda a tricky problem, because we need to solve two problems: * We need to add support for the shell context menu code to load our settings model. I don't know if we can do that easily currently. * We need to find a way to add settings to configure what our context menu settings should be. What shape do we want these settings to be? `contextMenu.showElevatedEntry` & `contextMenu.showProfilePicker`? `contextMenu.showElevatedProfilePicker`? We need some sort of design for that. * Putting nested entries in the menu is non-trivial, https://github.com/microsoft/terminal/issues/6111#issuecomment-1252946834 has some notes. At least I'm not enough of a shell32 guru to know. Figuring out the first bullet point is probably the hardest part. If you can get our settings loaded in the context menu code, then it's easy[^1] to add settings to control this. <hr> EDIT from "dumb idea central", some time after 5pm local time: > the shell extension has to be fast. there's that boolean for "you can do slow stuff," but we don't want to use it because win11 already fucked us over > > i think parsing appdata, loading json etc is gonna put us over budget > > that is, to figure out how to build the shell ext menu from user settings > > because we're packaged, we get our own registry. why shouldn't we cache this stuff in our isolated registry? it's way way faster than opening a file on disk, and has near 0 parsing > > so if you set contextMenu.showElevatedThing, we set a single DWORD > > and we don't need to do the shell(reg.exe) hack, it's all literally just local state > > the only real downside is, you gotta launch terminal once after editing settings.json to push the real values in > > none of this, "edit settings.json, then right click" > > but also, we could store the names/GUIDs/icons of profiles in there too if we really wanted to. Show this profile -> ok we'll "memoize" it. It's not enough to reconstruct the profile from registry, just enough to make a menu item out of it. > > so we aren't going into "store profiles in the registry" territory [^1]: Of course, naming in software is a **H**ard problem, but adding settings is easy once you've figured that out 😋
claunia commented 2026-01-31 03:46:08 +00:00
Author
Owner
Copy Link

@Mujtaba0150 commented on GitHub (Oct 3, 2024):

An easy workaround for someone willing to mess with the registry would be to add a registry key to the right click context menu to use PowerShell to open wt as an admin using the UAC prompt using this command:
powershell Start-Process wt.exe -ArgumentList '-p "Command Prompt"' -Verb RunAs

@Mujtaba0150 commented on GitHub (Oct 3, 2024): An easy workaround for someone willing to mess with the registry would be to add a registry key to the right click context menu to use PowerShell to open wt as an admin using the UAC prompt using this command: powershell Start-Process wt.exe -ArgumentList '-p \"Command Prompt\"' -Verb RunAs
claunia commented 2026-01-31 03:46:08 +00:00
Author
Owner
Copy Link

@akopetsch commented on GitHub (Feb 25, 2025):

I've created a workaround that adds an 'Open in Terminal as administrator' option to the extended context menu in Windows Explorer. You can find it here: akopetsch/WindowsTerminalAdmin.

@akopetsch commented on GitHub (Feb 25, 2025): I've created a workaround that adds an 'Open in Terminal as administrator' option to the extended context menu in Windows Explorer. You can find it here: [akopetsch/WindowsTerminalAdmin](https://github.com/akopetsch/WindowsTerminalAdmin).
claunia commented 2026-01-31 03:46:09 +00:00
Author
Owner
Copy Link

@eiqnepm commented on GitHub (May 29, 2025):

I've created a workaround that adds an 'Open in Terminal as administrator' option to the extended context menu in Windows Explorer. You can find it here: akopetsch/WindowsTerminalAdmin.

Nice!

I could've saved myself a couple hours had I found this yesterday before creating a solution myself.

eiqnepm/Terminal-CCM

Oh well, at least I learned the solution to a few annoying quirks along the way.

@eiqnepm commented on GitHub (May 29, 2025): > I've created a workaround that adds an 'Open in Terminal as administrator' option to the extended context menu in Windows Explorer. You can find it here: [akopetsch/WindowsTerminalAdmin](https://github.com/akopetsch/WindowsTerminalAdmin). Nice! I could've saved myself a couple hours had I found this yesterday before creating a solution myself. [eiqnepm/Terminal-CCM](https://github.com/eiqnepm/Terminal-CCM) Oh well, at least I learned the solution to a few annoying quirks along the way.
claunia commented 2026-01-31 03:46:09 +00:00
Author
Owner
Copy Link

@MarvinKlein1508 commented on GitHub (Jun 5, 2025):

Is there also any way to add it to the new context menu in Windows 11?

@MarvinKlein1508 commented on GitHub (Jun 5, 2025): Is there also any way to add it to the new context menu in Windows 11?
claunia commented 2026-01-31 03:46:09 +00:00
Author
Owner
Copy Link

@eiqnepm commented on GitHub (Jun 5, 2025):

Windows Terminal is already in the Windows 11 context menu

Are you sure you haven't disabled it by accident?

https://www.tenforums.com/tutorials/176295-add-remove-open-windows-terminal-context-menu-windows-10-a.html

@eiqnepm commented on GitHub (Jun 5, 2025): Windows Terminal is already in the Windows 11 context menu Are you sure you haven't disabled it by accident? https://www.tenforums.com/tutorials/176295-add-remove-open-windows-terminal-context-menu-windows-10-a.html
claunia commented 2026-01-31 03:46:09 +00:00
Author
Owner
Copy Link

@MarvinKlein1508 commented on GitHub (Jun 6, 2025):

I'Ve applied the registry patch and restarted my PC. Still no context menu:

Image

@MarvinKlein1508 commented on GitHub (Jun 6, 2025): I'Ve applied the registry patch and restarted my PC. Still no context menu: ![Image](https://github.com/user-attachments/assets/0d3219f7-1e40-46bd-9e33-99c642765f46)
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-Settings Area-ShellExtension Issue-Task Product-Terminal
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#13569
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?