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

CMD's start command and Start-Process pwsh opens all new tabs in new second instance of WT, despite settings #22435

New Issue
Open
opened 2026-01-31 08:13:09 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 08:13:09 +00:00
Owner
Copy Link

Originally created by @muizzsiddique on GitHub (Oct 20, 2024).

Windows Terminal version

1.20.11781.0

Windows build number

10.0.19044.5011

Other Software

No response

Steps to reproduce

Edit: This can also be done from Powershell using start-process pwsh (and likely start powershell)

  1. Open Windows Terminal with no other instances already running.
  2. In that same window, open Command Prompt profile (unless it is your default launch profile)
  3. Execute start command.
  4. Execute start command from the same window as step 3.
  5. Execute start command on the new spawned window from steps 3 or 4.

Startup settings:

Image

Expected Behavior

  • With step 3, start should open a new tab in the same window we just opened.
  • With step 4, start should open a new tab in the same window we just opened, again.
  • With step 5, if executing start from a new window, it should open a new tab in that same window.
  • If step 3 and 4 go as expected, step 5 shouldn't even exist.

Actual Behavior

  • With step 3, start opens a new tab in a new window. (unexpected)
  • With step 4, start opens a new tab in the same new window opened in step 2. (unexpected)
  • With step 5, start in the same new window as step 3 opens a new tab in the same new window opened in step 3 (this one works as expected).
Originally created by @muizzsiddique on GitHub (Oct 20, 2024). ### Windows Terminal version 1.20.11781.0 ### Windows build number 10.0.19044.5011 ### Other Software _No response_ ### Steps to reproduce Edit: This can also be done from Powershell using `start-process pwsh` (and likely `start powershell`) 1. Open Windows Terminal with no other instances already running. 2. In that same window, open Command Prompt profile (unless it is your default launch profile) 3. Execute `start` command. 4. Execute `start` command from the same window as step 3. 5. Execute `start` command on the new spawned window from steps 3 or 4. ### Startup settings: ![Image](https://github.com/user-attachments/assets/c985748c-c155-4dae-b762-87d7f3b5e40e) ### Expected Behavior - With step 3, `start` should open a new tab in the same window we just opened. - With step 4, `start` should open a new tab in the same window we just opened, again. - With step 5, if executing `start` from a new window, it should open a new tab in that same window. - If step 3 and 4 go as expected, step 5 shouldn't even exist. ### Actual Behavior - With step 3, `start` opens a new tab in a new window. (unexpected) - With step 4, `start` opens a new tab in the same new window opened in step 2. (unexpected) - With step 5, `start` in the same new window as step 3 opens a new tab in the same new window opened in step 3 (this one works as expected).
claunia added the Issue-BugProduct-TerminalArea-Windowing labels 2026-01-31 08:13:09 +00:00
claunia commented 2026-01-31 08:13:10 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 22, 2024):

This is definitely highly irregular.

Can I ask a couple follow ups?

  1. When you're launching the Terminal "Open Windows Terminal with no other instances already running"
    Are you starting the Terminal from the Start Menu / taskbar, or by running wt.exe?
  2. Is there an elevated (admin) instance running by any chance?
  3. Does this repro with Terminal 1.22 Preview (you can find this on our releases page)
  4. By any chance, are you running a portable / unpackaged Terminal in step 1?

I seemingly can't repro this locally.

@zadjii-msft commented on GitHub (Oct 22, 2024): This is definitely highly irregular. Can I ask a couple follow ups? 1. When you're launching the Terminal _"Open Windows Terminal with no other instances already running"_ Are you starting the Terminal from the Start Menu / taskbar, or by running `wt.exe`? 2. Is there an elevated (admin) instance running by any chance? 3. Does this repro with Terminal 1.22 Preview (you can find this on our releases page) 4. By any chance, are you running a portable / unpackaged Terminal in step 1? I seemingly can't repro this locally.
claunia commented 2026-01-31 08:13:10 +00:00
Author
Owner
Copy Link

@muizzsiddique commented on GitHub (Oct 22, 2024):

  1. I am running it from the Start bar via Searching, and from my taskbar (it's pinned)
  2. No. I launch it when there are no other Windows Terminal windows opened.
  3. This still happens on Microsoft.WindowsTerminal.Preview 1.22.2702.0
  4. I installed Windows Terminal as Microsoft.WindowsTerminal from winget, so whatever the default app/environment that provides.

I Reset both Windows Terminal and WT Preview, and it still happens (of course, after change the setting to open new instances in new tabs).

What's the best way to reset all my Windows Terminal settings?

Here's a recording showing it happen:

https://github.com/user-attachments/assets/15dad16b-4392-4bd8-86da-37c2cab57d50

@muizzsiddique commented on GitHub (Oct 22, 2024): 1. I am running it from the Start bar via Searching, and from my taskbar (it's pinned) 2. No. I launch it when there are no other Windows Terminal windows opened. 3. This still happens on `Microsoft.WindowsTerminal.Preview` 1.22.2702.0 4. I installed Windows Terminal as `Microsoft.WindowsTerminal` from winget, so whatever the default app/environment that provides. I Reset both Windows Terminal and WT Preview, and it still happens (of course, after change the setting to open new instances in new tabs). What's the best way to reset all my Windows Terminal settings? Here's a recording showing it happen: https://github.com/user-attachments/assets/15dad16b-4392-4bd8-86da-37c2cab57d50
claunia commented 2026-01-31 08:13:10 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Oct 30, 2024):

Interesting! Could you get an ETL Trace (refer to this guide) /? That'll help us debug this further.

@carlos-zamora commented on GitHub (Oct 30, 2024): Interesting! Could you get an ETL Trace (refer to [this guide](https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capturing-a-debug-etl-trace)) /? That'll help us debug this further.
claunia commented 2026-01-31 08:13:10 +00:00
Author
Owner
Copy Link

@muizzsiddique commented on GitHub (Oct 31, 2024):

Here's the terminal-trace.etl: https://user.fm/files/v2-8e77f46b31d98ec7a911ad51c7a49329/terminal-trace.zip

@muizzsiddique commented on GitHub (Oct 31, 2024): Here's the terminal-trace.etl: https://user.fm/files/v2-8e77f46b31d98ec7a911ad51c7a49329/terminal-trace.zip
claunia commented 2026-01-31 08:13:10 +00:00
Author
Owner
Copy Link

@muizzsiddique commented on GitHub (Nov 3, 2024):

I have to add, this does not happen if I spawn my first WT window by running pwsh.exe, powershell.exe or cmd.exe, only if I launch WT itself.

@muizzsiddique commented on GitHub (Nov 3, 2024): I have to add, this does not happen if I spawn my first WT window by running pwsh.exe, powershell.exe or cmd.exe, only if I launch WT itself.
claunia commented 2026-01-31 08:13:11 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 6, 2024):

Image

So, so far the only weird thing I've found is that during your first "open a new tab in the existing window" (with start), we for some reason disconnect the window from its desktop in our internal accounting...

I can't explain that.

Still looking!

@DHowett commented on GitHub (Nov 6, 2024): ![Image](https://github.com/user-attachments/assets/4edc006f-0352-4802-8829-f37debb48b99) So, so far the only weird thing I've found is that during your first "open a new tab in the existing window" (with `start`), we for some reason disconnect the window from its desktop in our internal accounting... I can't explain that. Still looking!
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-Windowing Issue-Bug 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#22435
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?