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

Run Terminal as another user #14099

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

Originally created by @eglyn on GitHub (Jun 3, 2021).

Hi all,

is there a way to launch a new tab with a different user ?
We have differents username for a same user (with differents privileges), and we need to launch some ps command with another user than the current user.
The only way I found is to create another profile with the following command line:

"commandline": "C:\\Windows\\System32\\runas.exe /savecred /user:domain\\anotherlogin powershell.exe",

But, it opens another windows PS, that is not a terminal windows, so with no split screen option, etc...

So is there a way to open a new tab with this user instead a new PS window ?

Thx !

Originally created by @eglyn on GitHub (Jun 3, 2021). Hi all, is there a way to launch a new tab with a different user ? We have differents username for a same user (with differents privileges), and we need to launch some ps command with another user than the current user. The only way I found is to create another profile with the following command line: ``` "commandline": "C:\\Windows\\System32\\runas.exe /savecred /user:domain\\anotherlogin powershell.exe", ``` But, it opens another windows PS, that is not a terminal windows, so with no split screen option, etc... So is there a way to open a new tab with this user instead a new PS window ? Thx !
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 04:00:52 +00:00
claunia commented 2026-01-31 04:00:53 +00:00
Author
Owner
Copy Link

@rosettet commented on GitHub (Jun 3, 2021):

If you are using Remote Management then you can specify a config file for each profile by adding -config /path/to/file to the end of the command line by using the '-config' flag.
You can even run custom commands to change profile on startup by adding the '-noexit' and '-command' tags to the end of the command line.
image
image
In your case (assuming wt is in your path) your Command Line may be:
C:\Program Files\PowerShell\7\pwsh.exe -noexit -command runas /savecred /user:domain\anotherlogin wt.exe

@rosettet commented on GitHub (Jun 3, 2021): If you are using Remote Management then you can specify a config file for each profile by adding -config /path/to/file to the end of the command line by using the '-config' flag. You can even run custom commands to change profile on startup by adding the '-noexit' and '-command' tags to the end of the command line. ![image](https://user-images.githubusercontent.com/79660359/120690180-814fcc00-c46a-11eb-92a9-c18a19ba447f.png) ![image](https://user-images.githubusercontent.com/79660359/120690306-a80e0280-c46a-11eb-894a-178f0264f88c.png) In your case (assuming wt is in your path) your Command Line may be: C:\Program Files\PowerShell\7\pwsh.exe -noexit -command runas /savecred /user:domain\\anotherlogin wt.exe
claunia commented 2026-01-31 04:00:53 +00:00
Author
Owner
Copy Link

@eglyn commented on GitHub (Jun 4, 2021):

it does not work, it says: wt.exe not found :/
Path of wt.exe is ok, if I change wt.exe by powershell, it launch powershell with the new account (user-c) , but in another window, not in a tab -_-

If I try to open wt via a powershell already with the user-c account, it says:

Annotation 2021-06-04 094754

If I open the windows session of the user-c, wt works :/

WT is installed on both sessions.

It seems we can't execute WT with a different user in powershell

@eglyn commented on GitHub (Jun 4, 2021): it does not work, it says: wt.exe not found :/ Path of wt.exe is ok, if I change wt.exe by powershell, it launch powershell with the new account (user-c) , but in another window, not in a tab -_- If I try to open wt via a powershell already with the user-c account, it says: ![Annotation 2021-06-04 094754](https://user-images.githubusercontent.com/24936778/120765884-f4644b80-c519-11eb-9da0-5b4368150b99.png) If I open the windows session of the user-c, wt works :/ WT is installed on both sessions. It seems we can't execute WT with a different user in powershell
claunia commented 2026-01-31 04:00:53 +00:00
Author
Owner
Copy Link

@eglyn commented on GitHub (Jun 4, 2021):

I found a workarround, but not really perfect:

  • Download the last version 1.9
  • extract the bundle with 7zip
  • extract the x64 msix
  • in the command line of WT this command:
    "commandline": "powershell -noexit -command runas /savecred /user:domain\user-c C:\WT\WindowsTerminal.exe",

it opens another WT with privilege account, not really in the same tab, but it is WT, so I can open new tab with my privilege account

@eglyn commented on GitHub (Jun 4, 2021): I found a workarround, but not really perfect: - Download the last version 1.9 - extract the bundle with 7zip - extract the x64 msix - in the command line of WT this command: "commandline": "powershell -noexit -command runas /savecred /user:domain\\user-c C:\\WT\\WindowsTerminal.exe", it opens another WT with privilege account, not really in the same tab, but it is WT, so I can open new tab with my privilege account
claunia commented 2026-01-31 04:00:53 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 6, 2021):

I'm glad you found a workaround! We're not really planning on allowing mixed elevation levels / mixed users within a single terminal Window - there are unfortunately a few security issues with that which we're not willing to ship ourselves. There are more details in the threads linked to #5000.

/dup #2200

@zadjii-msft commented on GitHub (Jul 6, 2021): I'm glad you found a workaround! We're not really planning on allowing mixed elevation levels / mixed users within a single terminal Window - there are unfortunately a few security issues with that which we're not willing to ship ourselves. There are more details in the threads linked to #5000. /dup #2200
claunia commented 2026-01-31 04:00:53 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 6, 2021):

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 (Jul 6, 2021): 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-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#14099
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?