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

Support configuring a profile to run as Administrator / Elevated Permissions #11629

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

Originally created by @Jaans on GitHub (Nov 30, 2020).

Description of the new feature/enhancement

As a Full Stack Developer using Visual Studio 2019, Service Fabric, NodeJS, and VS Code I have multiple profiles configured for various PowerShell command line scenarios. Some of these require elevated / administrative permissions in order to function correctly.

I would like to be able to have some profiles always run with elevated / administrative permissions.
Alternatively, a less ideal solution is for the entire Windows Terminal application to support configuration to start with administrative permissions.

Proposed technical implementation details (optional)

Ideal would be to configure - at profile level - that it must elevate. E.g. an additional property in the profile.

If it is only viable to start the entire Windows Terminal application with elevated permissions, then there seems behaviours coming from Windows Store Apps that prevent the traditional method of ensuring an application always starts with elevated prompt.

Normally applications can be configured to automatically elevate at start-up by configuring it with either a shortcut and the relevant shortcut settings, or my using my preferred method which is via Compatibility Settings.

However, it seems that applications delivered as Windows Store Apps do not offer the same capability or shortcut. You can manually right-click and "Run as Administrator", but not set it as a default start up.

Originally created by @Jaans on GitHub (Nov 30, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 As a Full Stack Developer using Visual Studio 2019, Service Fabric, NodeJS, and VS Code I have multiple profiles configured for various PowerShell command line scenarios. Some of these require elevated / administrative permissions in order to function correctly. I would like to be able to have some profiles **always** run with elevated / administrative permissions. Alternatively, a less ideal solution is for the entire Windows Terminal application to support configuration to start with administrative permissions. # Proposed technical implementation details (optional) Ideal would be to configure - at profile level - that it must elevate. E.g. an additional property in the profile. If it is only viable to start the entire Windows Terminal application with elevated permissions, then there seems behaviours coming from Windows Store Apps that prevent the traditional method of ensuring an application always starts with elevated prompt. Normally applications can be configured to automatically elevate at start-up by configuring it with either a shortcut and the relevant shortcut settings, or my using my preferred method which is via Compatibility Settings. However, it seems that applications delivered as Windows Store Apps do not offer the same capability or shortcut. You can manually right-click and "Run as Administrator", but not set it as a default start up.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 02:52:56 +00:00
claunia commented 2026-01-31 02:52:57 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 30, 2020):

You can't mix elevated and non-elevated tabs and BTW, this is also a dup of #632.

@ghost commented on GitHub (Nov 30, 2020): You can't mix elevated and non-elevated tabs and BTW, this is also a dup of #632.
claunia commented 2026-01-31 02:52:57 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 30, 2020):

Yep, this is a pretty specific /dup of #632. We're also tracking a bunch of related work in #5000, and this is also something that I'm writing the spec for currently.

Thanks!

@zadjii-msft commented on GitHub (Nov 30, 2020): Yep, this is a pretty specific /dup of #632. We're also tracking a bunch of related work in #5000, and this is also something that [I'm writing the spec for currently](https://github.com/microsoft/terminal/blob/dev/migrie/s/1032-elevation-qol/doc/specs/%235000%20-%20Process%20Model%202.0/%231032%20-%20Elevation%20Quality%20of%20Life%20Improvements.md). Thanks!
claunia commented 2026-01-31 02:52:57 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 30, 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 (Nov 30, 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!
claunia commented 2026-01-31 02:52:57 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 30, 2020):

Elevation Quality of Life Improvements

Nice title 😄

@ghost commented on GitHub (Nov 30, 2020): > Elevation Quality of Life Improvements Nice title :smile:
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-Feature 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#11629
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?