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

Passing a commandline to an elevate:true profile on the commandline doesn't separate args #16894

New Issue
Open
opened 2026-01-31 05:26:30 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 05:26:30 +00:00
Owner
Copy Link

Originally created by @zadjii-msft on GitHub (Feb 28, 2022).

(from a teams convo)

I bet that

wt --profile "Admin Cmd" -- cmd.exe /c D:\os\src\tools\razzle.cmd amd64fre developer_dir D:\Repos\developer\groups\jevansa no_opt

would work

[error 2147942402 (0x80070002) when launching `"cmd.exe /c D:\os\src\tools\razzle.cmd amd64fre developer_dir D:\Repos\developer\groups\jevansa no_opt"']
I ran: wt --profile "Admin Cmd" -- cmd.exe /c D:\os\src\tools\razzle.cmd amd64fre developer_dir D:\Repos\developer\groups\jevansa no_opt

I think it's still trying to take the whole string and pass to CreateProcess. Is there a way to get it split up?

it might be the fact that when you do have an elevate:true profile, we have to CreateProcess another terminal process, and I bet we're passing the whole bit after -- as a single arg to the elevated wt

Originally created by @zadjii-msft on GitHub (Feb 28, 2022). (from a teams convo) > I bet that > > ``` > wt --profile "Admin Cmd" -- cmd.exe /c D:\os\src\tools\razzle.cmd amd64fre developer_dir D:\Repos\developer\groups\jevansa no_opt > ``` > > would work > ```[error 2147942402 (0x80070002) when launching `"cmd.exe /c D:\os\src\tools\razzle.cmd amd64fre developer_dir D:\Repos\developer\groups\jevansa no_opt"']``` > I ran: `wt --profile "Admin Cmd" -- cmd.exe /c D:\os\src\tools\razzle.cmd amd64fre developer_dir D:\Repos\developer\groups\jevansa no_opt` > > I think it's still trying to take the whole string and pass to CreateProcess. Is there a way to get it split up? > it might be the fact that when you do have an `elevate:true` profile, we have to `CreateProcess` another terminal process, and I bet we're passing the whole bit after `--` as a single arg to the elevated wt
claunia added the Help WantedIssue-BugProduct-TerminalPriority-2Area-Commandline labels 2026-01-31 05:26:31 +00:00
claunia commented 2026-01-31 05:26:32 +00:00
Author
Owner
Copy Link

@Fred-Vatin commented on GitHub (Nov 14, 2022):

WT OS
1.15.2874.0 Win 10 x64 pro 21H1 19043.2251

I confirm. Very annoying bug.

My default profile is named PowerShell 7.
My admin profile named PowerShell 7 [admin] is the same but with "elevate": true.

Case 1 [success]

Run a .ps1 in the default profile.
wt.exe --window 0 new-tab --profile "PowerShell 7" pwsh "E:\OneDrive\Mes Documents\PowerShell\Scripts\Chemin des profiles pwsh.ps1"

Case 2 [success]

Open a new tab in the admin profile.
wt.exe --window 0 new-tab --profile "PowerShell 7 [admin]"

It works but still opens a new window even when ran from a terminal as admin.

Case 3 [fail]

Run a .ps1 in the admin profile
wt.exe --window 0 new-tab --profile "PowerShell 7 [admin]" pwsh "E:\OneDrive\Mes Documents\PowerShell\Scripts\Chemin des profiles pwsh.ps1"

Error thrown
[error 2147942402 (0x80070002) when launching `"pwsh E:\OneDrive\Mes" Documents\PowerShell\Scripts\Chemin des profiles pwsh.ps1']

Any workaround to succeed to run .ps1 script in the terminal as admin ?

@Fred-Vatin commented on GitHub (Nov 14, 2022): WT | OS ------------------ | ---- 1.15.2874.0 | Win 10 x64 pro 21H1 19043.2251 I confirm. Very annoying bug. My default profile is named **PowerShell 7**. My admin profile named **PowerShell 7 [admin]** is the same but with `"elevate": true`. ## Case 1 [success] Run a .ps1 in the default profile. `wt.exe --window 0 new-tab --profile "PowerShell 7" pwsh "E:\OneDrive\Mes Documents\PowerShell\Scripts\Chemin des profiles pwsh.ps1"` ## Case 2 [success] Open a new tab in the admin profile. `wt.exe --window 0 new-tab --profile "PowerShell 7 [admin]"` It works but still opens a new window even when ran from a terminal as admin. ## Case 3 [fail] Run a .ps1 in the admin profile `wt.exe --window 0 new-tab --profile "PowerShell 7 [admin]" pwsh "E:\OneDrive\Mes Documents\PowerShell\Scripts\Chemin des profiles pwsh.ps1"` Error thrown ``[error 2147942402 (0x80070002) when launching `"pwsh E:\OneDrive\Mes" Documents\PowerShell\Scripts\Chemin des profiles pwsh.ps1']`` --- Any workaround to succeed to run .ps1 script in the terminal as admin ?
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-Commandline Help Wanted Issue-Bug Priority-2 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#16894
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?