Incorrect DPI scaling for font preview in shell properties dialog #2646

Open
opened 2026-01-30 23:01:09 +00:00 by claunia · 2 comments
Owner

Originally created by @fluffninja on GitHub (Jul 8, 2019).

Environment

Windows Build Number: 10.0.18362.207
  • This issue relates to the built-in conhost.
  • Tested on a single monitor system at 200% DPI.

Description

The font preview shown on the Fonts tab or Colours tab doesn't use the correct DPI scaling when accessed via a shortcut's property dialog. However, the same font preview shown on a console window's property dialog does use the correct scaling.

Comparison Screenshot

Steps to reproduce

  1. Set the system DPI scaling to be higher than 100% (I use 200%). Sign in and out if changing.
  2. Find or create a shortcut to a console app (e.g. Command Prompt).
  3. Open the shortcut's property dialog and go to the Fonts tab or Colours tab.
  4. See that the font preview is not correctly scaled for the DPI.
  5. Run the console app and open the console window's property dialog.
  6. Go to the Fonts tab or Colours tab, and see that the font preview is correctly scaled for the DPI.
Originally created by @fluffninja on GitHub (Jul 8, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows Build Number: 10.0.18362.207 ``` * This issue relates to the built-in conhost. * Tested on a single monitor system at 200% DPI. # Description The font preview shown on the Fonts tab or Colours tab doesn't use the correct DPI scaling when accessed via a shortcut's property dialog. However, the same font preview shown on a console window's property dialog does use the correct scaling. ![Comparison Screenshot](https://user-images.githubusercontent.com/14015806/60824896-6737e100-a1a2-11e9-96ef-f87a33ca193e.PNG) # Steps to reproduce 1. Set the system DPI scaling to be higher than 100% (I use 200%). Sign in and out if changing. 2. Find or create a shortcut to a console app (e.g. Command Prompt). 3. Open the shortcut's property dialog and go to the Fonts tab or Colours tab. 4. See that the font preview is not correctly scaled for the DPI. 5. Run the console app and open the console window's property dialog. 6. Go to the Fonts tab or Colours tab, and see that the font preview is correctly scaled for the DPI.
claunia added the Help WantedProduct-ConhostIssue-BugArea-UserInterface labels 2026-01-30 23:01:10 +00:00
Author
Owner

@fluffninja commented on GitHub (Jul 8, 2019):

For comparison, both dialogs appear correct at 100% DPI.

Gallery2

@fluffninja commented on GitHub (Jul 8, 2019): For comparison, both dialogs appear correct at 100% DPI. ![Gallery2](https://user-images.githubusercontent.com/14015806/60826343-871cd400-a1a5-11e9-9d7c-889fe34094c2.PNG)
Author
Owner

@DHowett-MSFT commented on GitHub (Jul 11, 2019):

This is probably a quick fix, we just haven't had the time to look at it. To whomever does look at it: taking console.dll from the build system and replacing the one in %WINDIR%\system32 will work for testing plus or minus a reboot.

@DHowett-MSFT commented on GitHub (Jul 11, 2019): This is probably a quick fix, we just haven't had the time to look at it. To whomever _does_ look at it: taking `console.dll` from the build system and replacing the one in `%WINDIR%\system32` will work for testing plus or minus a reboot.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#2646