Quake mode starts on wrong monitor #23684

Closed
opened 2026-01-31 08:49:14 +00:00 by claunia · 4 comments
Owner

Originally created by @vefatica on GitHub (Oct 13, 2025).

Windows Terminal version

Any recent

Windows build number

10.0.19045.6332 (2009, 22H2)

Other Software

No response

Steps to reproduce

WT starts on monitor 2 (on the right). Before invoking Quake mode, left-drag WT to monitor 1 (on the left). Press Ctrl+Shift+Q.

Expected Behavior

The Quake window opens on monitor 1.

Actual Behavior

The Quake window opens on monitor 2.

[And] Another Ctrl+Shift+Q moves the Quake window to monitor 1 (also a bit odd).

Apparently, regardless of WT's position history (or where it is currently), if the Quake window does not exist it will open on WT's start-up monitor.

Originally created by @vefatica on GitHub (Oct 13, 2025). ### Windows Terminal version Any recent ### Windows build number 10.0.19045.6332 (2009, 22H2) ### Other Software _No response_ ### Steps to reproduce WT starts on monitor 2 (on the right). Before invoking Quake mode, left-drag WT to monitor 1 (on the left). Press Ctrl+Shift+Q. ### Expected Behavior The Quake window opens on monitor 1. ### Actual Behavior The Quake window opens on monitor 2. [And] Another Ctrl+Shift+Q moves the Quake window to monitor 1 (also a bit odd). Apparently, regardless of WT's position history (or where it is currently), if the Quake window **does not exist** it will open on WT's start-up monitor.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 08:49:14 +00:00
Author
Owner

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

Looks like this is a /dup of #18652! Thanks!

@DHowett commented on GitHub (Oct 15, 2025): Looks like this is a /dup of #18652! Thanks!
Author
Owner

@microsoft-github-policy-service[bot] commented on GitHub (Oct 15, 2025):

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 15, 2025): 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. -->
Author
Owner

@vefatica commented on GitHub (Oct 15, 2025):

If you say so ...

My report has nothing to do with desktops, rather monitors.

It seems you're doing something about #18652. Will that be in a nightly build soon?

@vefatica commented on GitHub (Oct 15, 2025): If you say so ... My report has nothing to do with desktops, rather monitors. It seems you're doing something about #18652. Will that be in a nightly build soon?
Author
Owner

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

Hm. @lhecker we may have been somewhat premature. This seems like a different issue.

@DHowett commented on GitHub (Oct 16, 2025): Hm. @lhecker we may have been somewhat premature. This seems like a different issue.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#23684