Windows Terminal as default terminal doesn't play well with existing windows #20688

Closed
opened 2026-01-31 07:21:16 +00:00 by claunia · 5 comments
Owner

Originally created by @bracco23 on GitHub (Oct 18, 2023).

Windows Terminal version

1.18.2681.0

Windows build number

10.0.19045.3448

Other Software

none

Steps to reproduce

  • open a new terminal window
  • set "new instance behaviour" to "attach to the most recently used window"
  • Set Windows terminal as default terminal
  • create a bat on the desktop with just the pause command
  • double click on the bat file

Expected Behavior

a new tab in the opened window is created, and the tab behaves as a normal tab

Actual Behavior

A new terminal window is created instead of using the existing one and it is not possible to drag tabs between the two Windows or between any windows spawned off the two (they basically seem to create two completely unrelated window groups.)

It might be included in the scope of #14900, but opening a new issue as it seems there is more to it that just the tab behaviour.

Originally created by @bracco23 on GitHub (Oct 18, 2023). ### Windows Terminal version 1.18.2681.0 ### Windows build number 10.0.19045.3448 ### Other Software none ### Steps to reproduce - open a new terminal window - set "new instance behaviour" to "attach to the most recently used window" - Set Windows terminal as default terminal - create a bat on the desktop with just the pause command - double click on the bat file ### Expected Behavior a new tab in the opened window is created, and the tab behaves as a normal tab ### Actual Behavior A new terminal window is created instead of using the existing one and it is not possible to drag tabs between the two Windows or between any windows spawned off the two (they basically seem to create two completely unrelated window groups.) It might be included in the scope of #14900, but opening a new issue as it seems there is more to it that just the tab behaviour.
claunia added the Issue-BugResolution-DuplicateProduct-TerminalArea-Remoting labels 2026-01-31 07:21:17 +00:00
Author
Owner

@PankajBhojwani commented on GitHub (Oct 18, 2023):

Thank you for reporting this!

Just want to clarify - neither of the terminal windows in the repro steps you listed are elevated right?

@PankajBhojwani commented on GitHub (Oct 18, 2023): Thank you for reporting this! Just want to clarify - neither of the terminal windows in the repro steps you listed are elevated right?
Author
Owner

@zadjii-msft commented on GitHub (Oct 18, 2023):

(this may also be #15509, but I haven't been able to repro it, and neither can Dustin anymore)

@zadjii-msft commented on GitHub (Oct 18, 2023): (this may also be #15509, but I haven't been able to repro it, and neither can Dustin anymore)
Author
Owner

@bracco23 commented on GitHub (Oct 22, 2023):

Neither the bat nor the standalone terminal is run elevated, at least not intentionally.

yeah #15509 sounds like it might be related.

@bracco23 commented on GitHub (Oct 22, 2023): Neither the bat nor the standalone terminal is run elevated, at least not intentionally. yeah #15509 sounds like it might be related.
Author
Owner

@carlos-zamora commented on GitHub (Oct 24, 2023):

Thanks again for filing! We're going to mark this as a /dup of #15509.

That said, we could definitely use some extra info to help debug this. Mind following this guide to get a trace and share it over in #15509? Thanks

@carlos-zamora commented on GitHub (Oct 24, 2023): Thanks again for filing! We're going to mark this as a /dup of #15509. That said, we could definitely use some extra info to help debug this. Mind following [this guide](https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capturing-a-debug-etl-trace) to get a trace and share it over in #15509? Thanks
Author
Owner

@microsoft-github-policy-service[bot] commented on GitHub (Oct 24, 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 (Oct 24, 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! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20688