Possible regression: "windowingBehavior": "useExisting" #23744

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

Originally created by @elibarzilay on GitHub (Oct 22, 2025).

Windows Terminal version

1.23.12811.0

Windows build number

10.0.26100.6899

Other Software

No response

Steps to reproduce

Looks like the "windowingBehavior": "useExisting" setting (New instance behavior: ...on this desktop) broke recently. I have a terminal on a second desktop, and starting a new terminal with wt.exe new-tab switches to the second desktop and creates a new tab in that window.

IOW, useExisting behaves the same as useAnyExisting for me.

Expected Behavior

As previously, should create a new terminal when an existing one is on an unselected desktop.

Actual Behavior

Jumps to the other desktop.

Originally created by @elibarzilay on GitHub (Oct 22, 2025). ### Windows Terminal version 1.23.12811.0 ### Windows build number 10.0.26100.6899 ### Other Software _No response_ ### Steps to reproduce Looks like the `"windowingBehavior": "useExisting"` setting (`New instance behavior: ...on this desktop`) broke recently. I have a terminal on a second desktop, and starting a new terminal with `wt.exe new-tab` switches to the second desktop and creates a new tab in that window. IOW, `useExisting` behaves the same as `useAnyExisting` for me. ### Expected Behavior As previously, should create a new terminal when an existing one is on an unselected desktop. ### Actual Behavior Jumps to the other desktop.
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:51:16 +00:00
Author
Owner

@DHowett commented on GitHub (Oct 22, 2025):

Good news! This was fixed with #19458 and is a duplicate of #18652. The fix will be included in the next servicing update.

@DHowett commented on GitHub (Oct 22, 2025): Good news! This was fixed with #19458 and is a duplicate of #18652. The fix will be included in the next servicing update.
Author
Owner

@elibarzilay commented on GitHub (Oct 22, 2025):

@DHowett Thanks!!

Also, apologies that I didn't find it (I didn't think to look for closed issues...)

@elibarzilay commented on GitHub (Oct 22, 2025): @DHowett Thanks!! Also, apologies that I didn't find it (I didn't think to look for closed issues...)
Author
Owner

@DHowett commented on GitHub (Oct 23, 2025):

To be totally fair, given our track record, I would not have looked in Closed first either. 😁

@DHowett commented on GitHub (Oct 23, 2025): To be totally fair, given our track record, I would not have looked in Closed first either. 😁
Author
Owner

@elibarzilay commented on GitHub (Dec 20, 2025):

@DHowett Just a quick comment to confirm that finally after an update this finally works fine again! -- Thanks!

@elibarzilay commented on GitHub (Dec 20, 2025): @DHowett Just a quick comment to confirm that finally after an update this finally works fine again! -- Thanks!
Author
Owner

@DHowett commented on GitHub (Dec 20, 2025):

Thanks for confirming and sorry for the delay in releasing it!

@DHowett commented on GitHub (Dec 20, 2025): Thanks for confirming and sorry for the delay in releasing it!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#23744