quake mode window doesn't resize when screen width changes in mstsc remote desktop #17120

Closed
opened 2026-01-31 05:32:46 +00:00 by claunia · 2 comments
Owner

Originally created by @Fan-iX on GitHub (Mar 29, 2022).

Windows Terminal version

1.12.10393.0

Windows build number

10.0.22581.0

Other Software

mstsc.exe remote desktop

Steps to reproduce

  1. One local PC with two monitors, and one remote PC
  2. Connect to the remote PC using mstsc.exe (full screen)
  3. start wt in quake mode in the remote desktop
  4. move the mstsc.exe window to another monitor and maximize (full screen) it

Expected Behavior

Quake mode window width adjusted to the new screen width

Actual Behavior

Quake mode window width doesn't change, even after hiding and re-showing the window

quake_window

monitor information:
mstsc.exe window moved form [3000×2000, 200% scale]
to [1920×1200, 100% scale] (the screenshot)

Originally created by @Fan-iX on GitHub (Mar 29, 2022). ### Windows Terminal version 1.12.10393.0 ### Windows build number 10.0.22581.0 ### Other Software `mstsc.exe` remote desktop ### Steps to reproduce 0. One local PC with two monitors, and one remote PC 1. Connect to the remote PC using `mstsc.exe` (full screen) 2. start `wt` in quake mode in the remote desktop 3. move the `mstsc.exe` window to another monitor and maximize (full screen) it ### Expected Behavior Quake mode window width adjusted to the new screen width ### Actual Behavior Quake mode window width doesn't change, even after hiding and re-showing the window ![quake_window](https://user-images.githubusercontent.com/61686936/160635595-e025952d-805d-45da-a87e-4138bfbf7191.png) monitor information: `mstsc.exe` window moved form [3000×2000, 200% scale] to [1920×1200, 100% scale] (the screenshot)
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 05:32:46 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Mar 30, 2022):

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #11125 for more discussion.

/dup #11125

@zadjii-msft commented on GitHub (Mar 30, 2022): Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #11125 for more discussion. /dup #11125
Author
Owner

@ghost commented on GitHub (Mar 30, 2022):

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!

@ghost commented on GitHub (Mar 30, 2022): 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!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#17120