Setting Launch mode to Maximized doesn't maximize #17550

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

Originally created by @gurnec on GitHub (May 24, 2022).

Windows Terminal version

1.14.1432.0

Windows build number

10.0.19044.0

Other Software

No response

Steps to reproduce

  1. Set the Launch mode to Maximized.
  2. Close Windows Terminal.
  3. Start Windows Terminal.

Expected Behavior

The window starts in a maximized state.

Actual Behavior

The window fills the entire screen, but it isn't actually maximized, instead it's in "restored" state. Note in the screenshot below, the system menu has Restore grayed out, but Maximize is available. Likewise in the upper right, the maximize button is visible instead of the restore button.

image

Just a guess without any basis, but I wonder if this is related to #13158....

Originally created by @gurnec on GitHub (May 24, 2022). ### Windows Terminal version 1.14.1432.0 ### Windows build number 10.0.19044.0 ### Other Software _No response_ ### Steps to reproduce 1. Set the Launch mode to Maximized. 2. Close Windows Terminal. 3. Start Windows Terminal. ### Expected Behavior The window starts in a maximized state. ### Actual Behavior The window fills the entire screen, but it isn't actually maximized, instead it's in "restored" state. Note in the screenshot below, the system menu has `Restore` grayed out, but `Maximize` is available. Likewise in the upper right, the maximize button is visible instead of the restore button. ![image](https://user-images.githubusercontent.com/2966862/170121714-6ef6d8a1-c0c0-45f8-90df-2751be424423.png) Just a guess without any basis, but I wonder if this is related to #13158....
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 05:45:43 +00:00
Author
Owner

@zadjii-msft commented on GitHub (May 24, 2022):

I'd bet on this being the same root cause as /dup #13158.

@zadjii-msft commented on GitHub (May 24, 2022): I'd bet on this being the same root cause as /dup #13158.
Author
Owner

@ghost commented on GitHub (May 24, 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 (May 24, 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#17550