starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 16:05:21 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Run this Profile as Admin starts Windows Powershell instead of Powershell7 #19911

New Issue
Closed
opened 2026-01-31 06:57:12 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 06:57:12 +00:00
Owner
Copy Link

Originally created by @leoniDEV on GitHub (May 20, 2023).

Windows Terminal version

1.17.1023

Windows build number

10.0.25352.0

Other Software

No response

Steps to reproduce

Create and account of type administrator;
Create a Windows Terminal's profile for Powershell7
In Windows Terminal set a profile for Windows Powershell as default profile;

Create an account of type standard;
login with this standard account;
Create a Windows Terminal's profile for Powershel7 an set Run this profile as Administrator to on
Try to open this Pwsh7 profile;
enter credential of the account of type administrator

Expected Behavior

Open a new elevated instance of Windows Terminal running Powershell 7

Actual Behavior

A new elevated instance of Windows Terminal is opened with the default profile loaded

Originally created by @leoniDEV on GitHub (May 20, 2023). ### Windows Terminal version 1.17.1023 ### Windows build number 10.0.25352.0 ### Other Software _No response_ ### Steps to reproduce Create and account of type administrator; Create a Windows Terminal's profile for `Powershell7` In Windows Terminal set a profile for `Windows Powershell` as default profile; Create an account of type standard; login with this standard account; Create a Windows Terminal's profile for `Powershel7` an set `Run this profile as Administrator` to `on` Try to open this `Pwsh7` profile; enter credential of the account of type administrator ### Expected Behavior Open a new elevated instance of Windows Terminal running Powershell 7 ### Actual Behavior A new elevated instance of Windows Terminal is opened with the default profile loaded
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:57:12 +00:00
claunia commented 2026-01-31 06:57:13 +00:00
Author
Owner
Copy Link

@leoniDEV commented on GitHub (May 20, 2023):

I think I understand what happen, when open a new tab, wt use the command new-tab --profile {GUID}, this GUID is the one of the profile in the settings of the standard account, but when try to open a profile as admin (when the admin is another account) it load the settings from the admin account which doesn't contains the GUID that wt try to load and then the default profile is loaded.

As a workaround I copied the GUID of the Powershell profile from the standard account to the Powershell profile in the setting file of the admin account.

@leoniDEV commented on GitHub (May 20, 2023): I think I understand what happen, when open a new tab, `wt` use the command `new-tab --profile {GUID}`, this `GUID` is the one of the profile in the settings of the standard account, but when try to open a profile as admin (when the admin is another account) it load the settings from the admin account which doesn't contains the `GUID` that `wt` try to load and then the default profile is loaded. As a workaround I copied the `GUID` of the Powershell profile from the standard account to the Powershell profile in the setting file of the admin account.
claunia commented 2026-01-31 06:57:13 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 22, 2023):

Ho boy this is a good edge case here. I don't think any of us considered that "Run as Admin" (where the admin account != your current user account) uses the settings from the admin account, not your own.

@zadjii-msft commented on GitHub (May 22, 2023): Ho boy this is a good edge case here. I don't think any of us considered that "Run as Admin" (where the admin account != your current user account) **uses the settings from the admin account**, not your own.
claunia commented 2026-01-31 06:57:13 +00:00
Author
Owner
Copy Link

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

Hey @leoniDEV! Thanks for filing, we're going to mark this as a dup of #11111.

/dup #11111

@carlos-zamora commented on GitHub (Jun 5, 2023): Hey @leoniDEV! Thanks for filing, we're going to mark this as a dup of #11111. /dup #11111
claunia commented 2026-01-31 06:57:13 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Jun 5, 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 5, 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!
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#19911
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?