starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

HDPI issue: Windows Terminal scales everything down #11254

New Issue
Open
opened 2026-01-31 02:42:38 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 02:42:38 +00:00
Owner
Copy Link

Originally created by @warpdesign on GitHub (Nov 2, 2020).

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):

Any other software?

Microsoft Windows [version 10.0.19041.610]
Windows Terminal: 1.3.2651.0

Steps to reproduce

I am not sure how to reproduce, but I have an external monitor that's not HDPI connected to my Surface Dock. After some time, opened up the Surface and noticed the Windows Terminal window was incorrectly scaled: display is way too small, just like the terminal window was on the other screen.

Notice how other apps, like Edge, that were also opened previously are correctly scaled.

Note that if at this point I open a new Windows Terminal window, it will be scaled correctly.

More information:

  • internal monitor: 3000x2000 Surface Book screen, scale set to 200% in Windows settings app
  • external monitor (that was switched to another computer when this happens): 2560x1440, scale set to 100% in Windows Settings

To sum up:

  • I started a Windows Terminal that was opened on the internal screen of the Surface Book
  • the external monitor was used to extend Windows's desktop (but the WT window was still on the internal monitor)
  • then the Surface Book was put to sleep, and the monitor disconnected (by switching to another computer)
  • then I woke up the laptop, and the WT window appeared to use the scaling (100%) of the external monitor instead of the 200% of the monitor it is displayed on

Expected behavior

Scaling should be correct.

Actual behavior

Scaling is wrong.

  • left: this is how Windows Terminal looked after I opened up my laptop
  • right: this is how it's supposed to look after a fresh start

image

Originally created by @warpdesign on GitHub (Nov 2, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] Windows Terminal version (if applicable): Any other software? ``` Microsoft Windows [version 10.0.19041.610] Windows Terminal: 1.3.2651.0 # Steps to reproduce <!-- A description of how to trigger this bug. --> I am not sure how to reproduce, but I have an external monitor that's not HDPI connected to my Surface Dock. After some time, opened up the Surface and noticed the Windows Terminal window was incorrectly scaled: display is way too small, just like the terminal window was on the other screen. Notice how other apps, like Edge, that were also opened previously are correctly scaled. Note that if at this point I open a new Windows Terminal window, it will be scaled correctly. More information: - internal monitor: 3000x2000 Surface Book screen, scale set to 200% in Windows settings app - external monitor (that was switched to another computer when this happens): 2560x1440, scale set to 100% in Windows Settings To sum up: - I started a Windows Terminal that was opened on the internal screen of the Surface Book - the external monitor was used to extend Windows's desktop (but the WT window was still on the internal monitor) - then the Surface Book was put to sleep, and the monitor disconnected (by switching to another computer) - then I woke up the laptop, and the WT window appeared to use the scaling (100%) of the external monitor instead of the 200% of the monitor it is displayed on # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Scaling should be correct. # Actual behavior Scaling is wrong. - left: this is how Windows Terminal looked after I opened up my laptop - right: this is how it's supposed to look after a fresh start ![image](https://user-images.githubusercontent.com/199648/97902966-a77b8500-1d3e-11eb-84f8-871a795ec037.png)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#11254
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?