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

wt -w 0 -p "MyProfile" No Longer Opens New Tab #23309

New Issue
Closed
opened 2026-01-31 08:38:27 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 08:38:27 +00:00
Owner
Copy Link

Originally created by @PaulCoddington on GitHub (May 28, 2025).

Windows Terminal version

1.22.11141.0

Windows build number

10.0.26100.0

Other Software

Powershell 7.5.1

Steps to reproduce

In recent versions of Windows Terminal, the following Powershell script command:

wt -w 0 -p "MyProfile"

no longer opens a new tab in the target window, as it used to.

Instead, it executes in the current tab, causing the calling script to block
until the MyProfile process exits.

This breaks existing workflows and scripts that rely on the previous behavior
to launch services in background tabs and continue execution asynchronously.

Expected Behavior

A Powershell script containing the command:

wt -w 0 -p "MyProfile"

should:

  • Open a new tab in the current window
  • Launch the specified profile
  • Return control immediately to the script that launched it

This allows launching multiple server applications in parallel, and/or in
sequence after availability checks (e.g. Test-NetConnection or Start-Sleep),
each in its own customized terminal environment.

Actual Behavior

The first profile launched now:

  • Runs in the current tab

  • Blocks the script until it exits

  • Ignores new-tab behavior implicitly expected by -p

  • Ignores new-tab behavior explicitly expected by new-tab or by wrapping the command in start-process.

This change breaks automation scripts that:

  • Launch local services in isolated profiles

  • Use Windows Terminal as a service supervisor

Originally created by @PaulCoddington on GitHub (May 28, 2025). ### Windows Terminal version 1.22.11141.0 ### Windows build number 10.0.26100.0 ### Other Software Powershell 7.5.1 ### Steps to reproduce In recent versions of Windows Terminal, the following Powershell script command: ``` wt -w 0 -p "MyProfile" ``` no longer opens a new tab in the target window, as it used to. Instead, it executes in the current tab, causing the calling script to block until the MyProfile process exits. This breaks existing workflows and scripts that rely on the previous behavior to launch services in background tabs and continue execution asynchronously. ### Expected Behavior A Powershell script containing the command: ``` wt -w 0 -p "MyProfile" ``` should: * Open a new tab in the current window * Launch the specified profile * Return control immediately to the script that launched it This allows launching multiple server applications in parallel, and/or in sequence after availability checks (e.g. Test-NetConnection or Start-Sleep), each in its own customized terminal environment. ### Actual Behavior The first profile launched now: * Runs in the current tab * Blocks the script until it exits * Ignores new-tab behavior implicitly expected by `-p` * Ignores new-tab behavior explicitly expected by `new-tab` or by wrapping the command in `start-process`. This change breaks automation scripts that: * Launch local services in isolated profiles * Use Windows Terminal as a service supervisor
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:38:27 +00:00
claunia commented 2026-01-31 08:38:28 +00:00
Author
Owner
Copy Link

@PaulCoddington commented on GitHub (May 28, 2025):

Solved it: problem between chair and desk. Apologies for letting loose a wild goose. It's been one of those days.

@PaulCoddington commented on GitHub (May 28, 2025): Solved it: problem between chair and desk. Apologies for letting loose a wild goose. It's been one of those days.
claunia commented 2026-01-31 08:38:28 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 28, 2025):

Untamed ornithoids, in my repository?

Thanks for following up. We run triage every Wednesday, and you beat us to asking additional questions. 🙂

@DHowett commented on GitHub (May 28, 2025): Untamed ornithoids, in _my_ repository? Thanks for following up. We run triage every Wednesday, and you beat us to asking additional questions. 🙂
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 Needs-Triage
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#23309
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?