System Change Display DPI Scaling Level in Windows 11


  • Staff
display_scaling_banner.png

This tutorial will show you how to change the DPI scaling level for all or specific displays to make everything appear smaller or larger on the display(s) for your account in Windows 11.

Dots per inch (DPI) is the physical measurement of number of pixels in a linear inch of a display. DPI is a function of display resolution and size; a higher resolution or a smaller size will lead to higher DPI, and a lower resolution or a larger size will lead to lower DPI. When a display has a higher DPI, pixels are smaller and closer together, so that the user interface (UI) and other displayed content appears smaller than intended.

Windows ensures that everything appears on the screen at a usable and consistent size by instructing applications (including the Windows desktop shell) to resize their content by a scale factor. This number depends on the display DPI as well as other factors that impact the user’s perception of the display. Almost all desktop displays and most current laptop displays are in the range of 95-110 DPI; for these devices, no scaling is required, and Windows sets a scale factor of 100%. However, there are a number of new devices, particularly in the premium laptop and tablet markets, which have higher displays with over 200 DPI. For these devices, Windows sets higher scale factors to ensure that the user experience is comfortably viewable.

You can adjust the display DPI scaling level in Windows 11 to change the size of text, apps, and other items to appear larger or smaller until comfortable to see for you.

When you increase the display DPI scaling level, everything will appear larger on the display.

When you decrease the display DPI scaling level, everything will appear smaller on the display.

The default DPI scaling level of a display is not always 100% (96 DPI). High resolution displays may have a higher "recommended" DPI than 100% by default.

Reference:


Contents

  • Option One: Change DPI Scaling Level for Specific Display in Settings
  • Option Two: Set Custom DPI Scaling Level for All Displays in Settings
  • Option Three: Set Custom DPI Scaling Level for All Displays in Registry Editor
  • Option Four: Restore Default DPI Scaling Level for All Displays using REG file




Option One

Change DPI Scaling Level for Specific Display in Settings


1 Open Settings (Win+I).

2 Click/tap on System on the left side, and click/tap on Display on the right side. (see screenshot below)


display_scaling_Settings-1.png

3 If you have more than one display connected to your PC, select a display (ex: "1") that you want to change the DPI scaling level for. (see screenshot below step 4)

If you are not sure which display belongs to what number, then you can click/tap on the Identify button to have each display's number briefly appear on the displays to see.


4 Select the Scale percentage you want in the drop menu. (see screenshot below)

The Recommended percentage is the default scale size.

This setting is stored as the DpiValue DWORD data value in a long subkey per display in the registry key location below.

HKEY_CURRENT_USER\Control Panel\Desktop\PerMonitorSettings


display_scaling_Settings-2.png

5 When finished, you can close Settings if you like.




Option Two

Set Custom DPI Scaling Level for All Displays in Settings


1 Open Settings (Win+I).

2 Click/tap on System on the left side, and click/tap on Display on the right side. (see screenshot below)


display_scaling_Settings-1.png

3 Do step 4 (set custom scaling) or step 5 (turn off custom scaling) for what you want.

4 To Set Custom Scaling Size for All Displays

This will override and gray out Option One


A) Click/tap on Scale on the right side. (see screenshot below)​

custom_display_scaling_Settings-1.png

B) Enter a custom scaling size between 100-500 % you want for all displays, and click/tap on the Check mark. (see screenshot below)​

custom_display_scaling_Settings-2.png

C) Click/tap on the Sign out now link to apply. (see screenshot below)​

custom_display_scaling_Settings-3.png

5 To Turn Off Custom Scaling for All Displays

This will undo the set custom scaling size, and allow you to use Option One


A) Click/tap on the Turn off custom scaling and sign out link on the right side under Scale & layout. (see screenshot below)​

custom_display_scaling_Settings-4.png




Option Three

Set Custom DPI Scaling Level for All Displays in Registry Editor


This option sets the same setting in Option Two, and will override and gray out Option One if you set a custom DPI.


1 Open Registry Editor (regedit.exe).

2 Navigate to the registry key location below in the left pane of Registry Editor. (see screenshot below)

HKEY_CURRENT_USER\Control Panel\Desktop

custom_display_scaling_regedit-1.png

3 In the right pane of the Desktop key, double click/tap on the LogPixels DWORD to modify it. (see screenshot above)

If the LogPixels DWORD doesn't exist, then right click or press and hold on an empty area in the right pane of the Desktop key, click/tap on New, click/tap on DWORD (32-bit) Value, type LogPixels, and press Enter.


4 Select (dot) Decimal, type in a value data from 96 to 480 for the scaling level you want, and click/tap on OK. (see screenshot and table below)

custom_display_scaling_regedit-2.png

DPI Scaling Level
Value data
Small 100% (default)96
Medium 125%120
Large 150%144
Extra Large 200%192
Custom 250%240
Custom 300%288
Custom 325%312
Custom 350%336
Custom 400%384
Custom 450%432
Custom 500%480

5 In the right pane of the Desktop key, double click/tap on the Win8DpiScaling DWORD to modify it. (see screenshot below)

If the Win8DpiScaling DWORD doesn't exist, then right click or press and hold on an empty area in the right pane of the Desktop key, click/tap on New, click/tap on DWORD (32-bit) Value, type Win8DpiScaling, and press Enter.


custom_display_scaling_regedit-3.png

6 Type 0 (turn off custom scaling) or 1 (turn on custom scaling) for the value data based on the table below, and click/tap on OK. (see screenshot below)

custom_display_scaling_regedit-4.png

Value data
Description
0Enter 0 if you used 96 in step 4 for no custom DPI scaling.
1Enter 1 if you used any size over 96 in step 4 for custom DPI scaling.

7 Close Registry Editor.

8 Sign out and sign in to apply.




Option Four

Restore Default DPI Scaling Level for All Displays using REG file


1 Click/tap on the Download button below for the DPI you want to restore to download the REG file below.


 To restore 100% DPI Scaling Level

Restore_100_DPI_in_Windows_11.reg


(Contents of REG file for reference)
Code:
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Control Panel\Desktop]
"LogPixels"=-
"Win8DpiScaling"=dword:00000000

[-HKEY_CURRENT_USER\Control Panel\Desktop\PerMonitorSettings]

[HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics]
"AppliedDPI"=dword:00000096


 To restore 200% DPI Scaling Level

This DPI is a good starting point for higher resolution displays.


Restore_200_DPI_in_Windows_11.reg


(Contents of REG file for reference)
Code:
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Control Panel\Desktop]
"LogPixels"=-
"Win8DpiScaling"=dword:00000000

[-HKEY_CURRENT_USER\Control Panel\Desktop\PerMonitorSettings]

[HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics]
"AppliedDPI"=dword:00000192

2 Save the .reg file to your desktop.

3 Double click/tap on the downloaded .reg file to merge it.

4 When prompted, click/tap on Run, Yes (UAC), Yes, and OK to approve the merge.

5 Sign out and sign in to apply.

6 You can now delete the downloaded .reg file if you like.


That's it,
Shawn Brink


 

Attachments

  • display_scaling.png
    display_scaling.png
    14 KB · Views: 222
  • Restore_100_DPI_in_Windows_11.reg
    962 bytes · Views: 88
  • Restore_200_DPI_in_Windows_11.reg
    962 bytes · Views: 101
Last edited:
You can also try changing the scaling for a specific app, as opposed to changing it for a specific display device. It works for me with HDDScan, which is an example of a free app the scale of which is tiny-microscopic on my 4k screen (with the scaling of my 4k screen set to 150% in Windows Settings | System | Display | Scale and using 3840x2160 display resolution).
:shawn:

 

My Computers

System One System Two

  • OS
    Windows 11 Pro for Workstations
    Computer type
    PC/Desktop
    Manufacturer/Model
    Custom self build
    CPU
    Intel i7-8700K 5 GHz
    Motherboard
    ASUS ROG Maximus XI Formula Z390
    Memory
    64 GB (4x16GB) G.SKILL TridentZ RGB DDR4 3600 MHz (F4-3600C18D-32GTZR)
    Graphics Card(s)
    ASUS ROG-STRIX-GTX1080TI-O11G-GAMING (11GB GDDR5X)
    Sound Card
    Integrated Digital Audio (S/PDIF)
    Monitor(s) Displays
    2 x Samsung Odyssey G75 27"
    Screen Resolution
    2560x1440
    Hard Drives
    1TB Samsung 990 PRO M.2,
    4TB Samsung 990 PRO M.2,
    8TB WD MyCloudEX2Ultra NAS
    PSU
    Seasonic Prime Titanium 850W
    Case
    Thermaltake Core P3 wall mounted
    Cooling
    Corsair Hydro H115i
    Keyboard
    Logitech wireless K800
    Mouse
    Logitech MX Master 3
    Internet Speed
    1 Gbps Download and 35 Mbps Upload
    Browser
    Google Chrome
    Antivirus
    Microsoft Defender and Malwarebytes Premium
    Other Info
    Logitech Z625 speaker system,
    Logitech BRIO 4K Pro webcam,
    HP Color LaserJet Pro MFP M477fdn,
    APC SMART-UPS RT 1000 XL - SURT1000XLI,
    Galaxy S23 Plus phone
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    HP Spectre x360 2in1 14-eu0098nr (2024)
    CPU
    Intel Core Ultra 7 155H 4.8 GHz
    Memory
    16 GB LPDDR5x-7467 MHz
    Graphics card(s)
    Integrated Intel Arc
    Sound Card
    Poly Studio
    Monitor(s) Displays
    14" 2.8K OLED multitouch
    Screen Resolution
    2880 x 1800
    Hard Drives
    2 TB PCIe NVMe M.2 SSD
    Internet Speed
    Intel Wi-Fi 7 BE200 (2x2) and Bluetooth 5.4
    Browser
    Chrome and Edge
    Antivirus
    Windows Defender and Malwarebytes Premium
Hey Brink!
So, I've used this fix for well over 2 years, with no issues; until now. So, this morning, I ran into a machine that had the Win8DpiScaling dword key set to "0", which should be fine for 100% scaling, and the LogPixels dword key set to "96" (decimal); which should also be correct for 100%. However, the user's desktop kept constantly rescaling to 125%, which it shouldn't have. So, I found that setting the keys in the registry merge to the HEXIDECIMAL number (60), and setting the WinDpiScaling to "1" corrected the issue. Do you have any idea why the registry merge file used to ALWAYS look like the following and work:
[HKEY_CURRENT_USER\Control Panel\Desktop]
"LogPixels"=dword:00000096
"Win8DpiScaling"=dword:00000000

[-HKEY_CURRENT_USER\Control Panel\Desktop\PerMonitorSettings]

[HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics]
"AppliedDPI"=dword:00000096



but NOW, it seems that it has to be set to the HEXIDECIMAL value and the Win8DpiScaling has to be set to "1" now, for the registry merge file to work:
[HKEY_CURRENT_USER\Control Panel\Desktop]
"LogPixels"=dword:00000060
"Win8DpiScaling"=dword:00000001

[-HKEY_CURRENT_USER\Control Panel\Desktop\PerMonitorSettings]

[HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics]
"AppliedDPI"=dword:00000060



The system is a Dell Precision 3580 Laptop, with a FHD non-touch 1920x1080 native resolution screen at 15.6in in size. I looked up Microsoft's documentation, regarding DPI scaling, and it "appears" that they now auto default monitors below 17in, with 1920x1080 resolution, to 125% magnification (scaling). Does that sound right? Here is Microsoft's documentation on the matter:
 

My Computer

System One

  • OS
    Windows 10
Hey Brink!
So, I've used this fix for well over 2 years, with no issues; until now. So, this morning, I ran into a machine that had the Win8DpiScaling dword key set to "0", which should be fine for 100% scaling, and the LogPixels dword key set to "96" (decimal); which should also be correct for 100%. However, the user's desktop kept constantly rescaling to 125%, which it shouldn't have. So, I found that setting the keys in the registry merge to the HEXIDECIMAL number (60), and setting the WinDpiScaling to "1" corrected the issue. Do you have any idea why the registry merge file used to ALWAYS look like the following and work:
[HKEY_CURRENT_USER\Control Panel\Desktop]
"LogPixels"=dword:00000096
"Win8DpiScaling"=dword:00000000

[-HKEY_CURRENT_USER\Control Panel\Desktop\PerMonitorSettings]

[HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics]
"AppliedDPI"=dword:00000096



but NOW, it seems that it has to be set to the HEXIDECIMAL value and the Win8DpiScaling has to be set to "1" now, for the registry merge file to work:
[HKEY_CURRENT_USER\Control Panel\Desktop]
"LogPixels"=dword:00000060
"Win8DpiScaling"=dword:00000001

[-HKEY_CURRENT_USER\Control Panel\Desktop\PerMonitorSettings]

[HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics]
"AppliedDPI"=dword:00000060



The system is a Dell Precision 3580 Laptop, with a FHD non-touch 1920x1080 native resolution screen at 15.6in in size. I looked up Microsoft's documentation, regarding DPI scaling, and it "appears" that they now auto default monitors below 17in, with 1920x1080 resolution, to 125% magnification (scaling). Does that sound right? Here is Microsoft's documentation on the matter:

Hello, :alien:

Odd, it's still shows the same in the tutorial for a default clean install of W11 on a VM.
 

My Computers

System One System Two

  • OS
    Windows 11 Pro for Workstations
    Computer type
    PC/Desktop
    Manufacturer/Model
    Custom self build
    CPU
    Intel i7-8700K 5 GHz
    Motherboard
    ASUS ROG Maximus XI Formula Z390
    Memory
    64 GB (4x16GB) G.SKILL TridentZ RGB DDR4 3600 MHz (F4-3600C18D-32GTZR)
    Graphics Card(s)
    ASUS ROG-STRIX-GTX1080TI-O11G-GAMING (11GB GDDR5X)
    Sound Card
    Integrated Digital Audio (S/PDIF)
    Monitor(s) Displays
    2 x Samsung Odyssey G75 27"
    Screen Resolution
    2560x1440
    Hard Drives
    1TB Samsung 990 PRO M.2,
    4TB Samsung 990 PRO M.2,
    8TB WD MyCloudEX2Ultra NAS
    PSU
    Seasonic Prime Titanium 850W
    Case
    Thermaltake Core P3 wall mounted
    Cooling
    Corsair Hydro H115i
    Keyboard
    Logitech wireless K800
    Mouse
    Logitech MX Master 3
    Internet Speed
    1 Gbps Download and 35 Mbps Upload
    Browser
    Google Chrome
    Antivirus
    Microsoft Defender and Malwarebytes Premium
    Other Info
    Logitech Z625 speaker system,
    Logitech BRIO 4K Pro webcam,
    HP Color LaserJet Pro MFP M477fdn,
    APC SMART-UPS RT 1000 XL - SURT1000XLI,
    Galaxy S23 Plus phone
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    HP Spectre x360 2in1 14-eu0098nr (2024)
    CPU
    Intel Core Ultra 7 155H 4.8 GHz
    Memory
    16 GB LPDDR5x-7467 MHz
    Graphics card(s)
    Integrated Intel Arc
    Sound Card
    Poly Studio
    Monitor(s) Displays
    14" 2.8K OLED multitouch
    Screen Resolution
    2880 x 1800
    Hard Drives
    2 TB PCIe NVMe M.2 SSD
    Internet Speed
    Intel Wi-Fi 7 BE200 (2x2) and Bluetooth 5.4
    Browser
    Chrome and Edge
    Antivirus
    Windows Defender and Malwarebytes Premium
Hello, :alien:

Odd, it's still shows the same in the tutorial for a default clean install of W11 on a VM.
So, I doubt that a VM will display this same scenario. It's ONLY occurring on the user's console laptop screen (15.6in in size). If they connect an external monitor to the system, it does not appear to have that issue. It seems like "perhaps" Microsoft made a change to how they default DPI scaling, based on the size of the monitor. It "used to be" that you could just set Win8DpiScaling to "0", and as long as the system had a native resolution of 1920x1080, it would set the magnification to 100%...at least as far as I remember. Now, it appears that if the screen is a certain size, Microsoft overrides this to a default of 125%, and I have NO IDEA why the registry merge with the "LogPixels"=dword:00000096 and "AppliedDPI"=dword:00000096 no longer works. Every time I did that, it just defaulted it to 150%. Only changing the registry merge file to use the HEXIDECIMAL equivalent worked. =\

Sorry to bother, and thanks for your quick response and research in this matter. I'm just trying to figure out what's going on here...because I KNOW that your fix used to work perfectly. This is the first time I've ever seen it not work...but Microsoft's documentation "kind of" makes sense, as to what they're doing now. Do you have a way to possibly replicate on a 15.6in laptop of some kind? I know that's a LOT of work, so if not, it's perfectly fine. I plan to continue testing on my end anyways.
 

My Computer

System One

  • OS
    Windows 10
So, I doubt that a VM will display this same scenario. It's ONLY occurring on the user's console laptop screen (15.6in in size). If they connect an external monitor to the system, it does not appear to have that issue. It seems like "perhaps" Microsoft made a change to how they default DPI scaling, based on the size of the monitor. It "used to be" that you could just set Win8DpiScaling to "0", and as long as the system had a native resolution of 1920x1080, it would set the magnification to 100%...at least as far as I remember. Now, it appears that if the screen is a certain size, Microsoft overrides this to a default of 125%, and I have NO IDEA why the registry merge with the "LogPixels"=dword:00000096 and "AppliedDPI"=dword:00000096 no longer works. Every time I did that, it just defaulted it to 150%. Only changing the registry merge file to use the HEXIDECIMAL equivalent worked. =\

Sorry to bother, and thanks for your quick response and research in this matter. I'm just trying to figure out what's going on here...because I KNOW that you're fix used to work perfectly. This is the first time I've ever seen it not work...but Microsoft's documentation "kind of" makes sense, as to what they're doing now. Do you have a way to possibly replicate on a 15.6in laptop of some kind? I know that's a LOT of work, so if not, it's perfectly fine. I plan to continue testing on my end anyways.
It's never a bother. It would be good to hear from others seeing the same or different.

I'll do some more playing. It doesn't help when not everything uses 100% by default though. LOL

I tweaked option four to delete the "LogPixels" DWORD value to remove any custom DPI set so it'll use the default.

"AppliedDPI" only works when "PerMonitorSettings" is deleted first since it will override "AppliedDPI".

Of course the default "AppliedDPI" value for a display is not always 100% DPI.
 
Last edited:

My Computers

System One System Two

  • OS
    Windows 11 Pro for Workstations
    Computer type
    PC/Desktop
    Manufacturer/Model
    Custom self build
    CPU
    Intel i7-8700K 5 GHz
    Motherboard
    ASUS ROG Maximus XI Formula Z390
    Memory
    64 GB (4x16GB) G.SKILL TridentZ RGB DDR4 3600 MHz (F4-3600C18D-32GTZR)
    Graphics Card(s)
    ASUS ROG-STRIX-GTX1080TI-O11G-GAMING (11GB GDDR5X)
    Sound Card
    Integrated Digital Audio (S/PDIF)
    Monitor(s) Displays
    2 x Samsung Odyssey G75 27"
    Screen Resolution
    2560x1440
    Hard Drives
    1TB Samsung 990 PRO M.2,
    4TB Samsung 990 PRO M.2,
    8TB WD MyCloudEX2Ultra NAS
    PSU
    Seasonic Prime Titanium 850W
    Case
    Thermaltake Core P3 wall mounted
    Cooling
    Corsair Hydro H115i
    Keyboard
    Logitech wireless K800
    Mouse
    Logitech MX Master 3
    Internet Speed
    1 Gbps Download and 35 Mbps Upload
    Browser
    Google Chrome
    Antivirus
    Microsoft Defender and Malwarebytes Premium
    Other Info
    Logitech Z625 speaker system,
    Logitech BRIO 4K Pro webcam,
    HP Color LaserJet Pro MFP M477fdn,
    APC SMART-UPS RT 1000 XL - SURT1000XLI,
    Galaxy S23 Plus phone
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    HP Spectre x360 2in1 14-eu0098nr (2024)
    CPU
    Intel Core Ultra 7 155H 4.8 GHz
    Memory
    16 GB LPDDR5x-7467 MHz
    Graphics card(s)
    Integrated Intel Arc
    Sound Card
    Poly Studio
    Monitor(s) Displays
    14" 2.8K OLED multitouch
    Screen Resolution
    2880 x 1800
    Hard Drives
    2 TB PCIe NVMe M.2 SSD
    Internet Speed
    Intel Wi-Fi 7 BE200 (2x2) and Bluetooth 5.4
    Browser
    Chrome and Edge
    Antivirus
    Windows Defender and Malwarebytes Premium
It's never a bother. It would be good to hear from others seeing the same or different.

I'll do some more playing. It doesn't help when not everything uses 100% by default though. LOL

I tweaked option four to delete the "LogPixels" DWORD value to remove any custom DPI set so it'll use the default.

"AppliedDPI" only works when "PerMonitorSettings" is deleted first since it will override "AppliedDPI".

Of course the default "AppliedDPI" value for a display is not always 100% DPI.
Thank you sir! I'll attempt to keep testing on my end as well. I'll let you know what I come up with soon. Have two other machines that I'm going to setup that are BOTH 15.6in display laptops. Hopefully, they will replicate this issue.
 

My Computer

System One

  • OS
    Windows 10
It's never a bother. It would be good to hear from others seeing the same or different.

I'll do some more playing. It doesn't help when not everything uses 100% by default though. LOL

I tweaked option four to delete the "LogPixels" DWORD value to remove any custom DPI set so it'll use the default.

"AppliedDPI" only works when "PerMonitorSettings" is deleted first since it will override "AppliedDPI".

Of course the default "AppliedDPI" value for a display is not always 100% DPI.
Good morning Brink! So, I did some EXTENSIVE testing on this, and this is what I found...so, what you have currently, NOW (after edits), does INDEED reset the scaling back to the default; however, it's worth noting, that if Windows is running on a low-res monitor, Microsoft automatically detects the monitor size and then automatically sets the scaling depending on the monitor resolution. So, in OUR case, what we were trying to do, was set a CUSTOM scaling that would override the default value that Microsoft automatically sets upon logging in. To do that, I needed to set the following:
HKCU\Control Panel\Desktop\
LogPixels = '96' <- (100% - this actually set the custom scaling size)
Win8DpiScaling = '1' <- (this actually TURNS ON the custom scaling)

-HKCU\Control Panel\Desktop\PerMonitorSettings <- (gets removed entirely, if you want it to be the same across ALL displays)

HKCU\Control Panel\Desktop\WindowMetrics
AppliedDPI = '96' <- (100% - honestly, this does NOT even need to be set, as this is what windows "auto" applies based on either the screen resolution or the CUSTOM DPI scaling that you have set...I just set it to 100% to match the custom scaling, but even NOT applying this, as long as custom DPI is set and ON, Windows will set this to match the CUSTOM DPI automatically)

This general occurs when their is a low-res monitor or SMALL monitor OR a monitor with a non-common 16:9/16:10 ratio. It does NOT appear to do it on virtual machines, because the scaling is obviously inherited from the HOST box. Sorry for being long-winded, just wanted to give you all the details.

Not even sure that anything in your guide needs to be "altered", I would probably just add a few details to state that if you WANT it to use a custom DPI, and STAY that way (without Windows automatically setting it to something that you don't want), that you have to set the Win8DpiScaling to '1' to turn it on. Thank you VERY much for your time sir! =)
 

My Computer

System One

  • OS
    Windows 10
Good morning Brink! So, I did some EXTENSIVE testing on this, and this is what I found...so, what you have currently, NOW (after edits), does INDEED reset the scaling back to the default; however, it's worth noting, that if Windows is running on a low-res monitor, Microsoft automatically detects the monitor size and then automatically sets the scaling depending on the monitor resolution. So, in OUR case, what we were trying to do, was set a CUSTOM scaling that would override the default value that Microsoft automatically sets upon logging in. To do that, I needed to set the following:
HKCU\Control Panel\Desktop\
LogPixels = '96' <- (100% - this actually set the custom scaling size)
Win8DpiScaling = '1' <- (this actually TURNS ON the custom scaling)

-HKCU\Control Panel\Desktop\PerMonitorSettings <- (gets removed entirely, if you want it to be the same across ALL displays)

HKCU\Control Panel\Desktop\WindowMetrics
AppliedDPI = '96' <- (100% - honestly, this does NOT even need to be set, as this is what windows "auto" applies based on either the screen resolution or the CUSTOM DPI scaling that you have set...I just set it to 100% to match the custom scaling, but even NOT applying this, as long as custom DPI is set and ON, Windows will set this to match the CUSTOM DPI automatically)

This general occurs when their is a low-res monitor or SMALL monitor OR a monitor with a non-common 16:9/16:10 ratio. It does NOT appear to do it on virtual machines, because the scaling is obviously inherited from the HOST box. Sorry for being long-winded, just wanted to give you all the details.

Not even sure that anything in your guide needs to be "altered", I would probably just add a few details to state that if you WANT it to use a custom DPI, and STAY that way (without Windows automatically setting it to something that you don't want), that you have to set the Win8DpiScaling to '1' to turn it on. Thank you VERY much for your time sir! =)
Thank you for testing more. That's what I was seeing as well. :alien:
 

My Computers

System One System Two

  • OS
    Windows 11 Pro for Workstations
    Computer type
    PC/Desktop
    Manufacturer/Model
    Custom self build
    CPU
    Intel i7-8700K 5 GHz
    Motherboard
    ASUS ROG Maximus XI Formula Z390
    Memory
    64 GB (4x16GB) G.SKILL TridentZ RGB DDR4 3600 MHz (F4-3600C18D-32GTZR)
    Graphics Card(s)
    ASUS ROG-STRIX-GTX1080TI-O11G-GAMING (11GB GDDR5X)
    Sound Card
    Integrated Digital Audio (S/PDIF)
    Monitor(s) Displays
    2 x Samsung Odyssey G75 27"
    Screen Resolution
    2560x1440
    Hard Drives
    1TB Samsung 990 PRO M.2,
    4TB Samsung 990 PRO M.2,
    8TB WD MyCloudEX2Ultra NAS
    PSU
    Seasonic Prime Titanium 850W
    Case
    Thermaltake Core P3 wall mounted
    Cooling
    Corsair Hydro H115i
    Keyboard
    Logitech wireless K800
    Mouse
    Logitech MX Master 3
    Internet Speed
    1 Gbps Download and 35 Mbps Upload
    Browser
    Google Chrome
    Antivirus
    Microsoft Defender and Malwarebytes Premium
    Other Info
    Logitech Z625 speaker system,
    Logitech BRIO 4K Pro webcam,
    HP Color LaserJet Pro MFP M477fdn,
    APC SMART-UPS RT 1000 XL - SURT1000XLI,
    Galaxy S23 Plus phone
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    HP Spectre x360 2in1 14-eu0098nr (2024)
    CPU
    Intel Core Ultra 7 155H 4.8 GHz
    Memory
    16 GB LPDDR5x-7467 MHz
    Graphics card(s)
    Integrated Intel Arc
    Sound Card
    Poly Studio
    Monitor(s) Displays
    14" 2.8K OLED multitouch
    Screen Resolution
    2880 x 1800
    Hard Drives
    2 TB PCIe NVMe M.2 SSD
    Internet Speed
    Intel Wi-Fi 7 BE200 (2x2) and Bluetooth 5.4
    Browser
    Chrome and Edge
    Antivirus
    Windows Defender and Malwarebytes Premium
how i change dpi for windows copilot ???
 

My Computer

System One

  • OS
    Windows 11 Pro insiders
    Computer type
    PC/Desktop
    Screen Resolution
    Full HD
    Browser
    Microsoft Edge Chromium Canary
    Antivirus
    Eset Smart Security Premium
how i change dpi for windows copilot ???

Hello, :alien:

I'm afraid the DPI scaling level setting affects everything. Currently, there's not a setting to change the size of Copilot.

Please send a request to Microsoft via the Feedback Hub app. If enough requests are made, it could happen.
 

My Computers

System One System Two

  • OS
    Windows 11 Pro for Workstations
    Computer type
    PC/Desktop
    Manufacturer/Model
    Custom self build
    CPU
    Intel i7-8700K 5 GHz
    Motherboard
    ASUS ROG Maximus XI Formula Z390
    Memory
    64 GB (4x16GB) G.SKILL TridentZ RGB DDR4 3600 MHz (F4-3600C18D-32GTZR)
    Graphics Card(s)
    ASUS ROG-STRIX-GTX1080TI-O11G-GAMING (11GB GDDR5X)
    Sound Card
    Integrated Digital Audio (S/PDIF)
    Monitor(s) Displays
    2 x Samsung Odyssey G75 27"
    Screen Resolution
    2560x1440
    Hard Drives
    1TB Samsung 990 PRO M.2,
    4TB Samsung 990 PRO M.2,
    8TB WD MyCloudEX2Ultra NAS
    PSU
    Seasonic Prime Titanium 850W
    Case
    Thermaltake Core P3 wall mounted
    Cooling
    Corsair Hydro H115i
    Keyboard
    Logitech wireless K800
    Mouse
    Logitech MX Master 3
    Internet Speed
    1 Gbps Download and 35 Mbps Upload
    Browser
    Google Chrome
    Antivirus
    Microsoft Defender and Malwarebytes Premium
    Other Info
    Logitech Z625 speaker system,
    Logitech BRIO 4K Pro webcam,
    HP Color LaserJet Pro MFP M477fdn,
    APC SMART-UPS RT 1000 XL - SURT1000XLI,
    Galaxy S23 Plus phone
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    HP Spectre x360 2in1 14-eu0098nr (2024)
    CPU
    Intel Core Ultra 7 155H 4.8 GHz
    Memory
    16 GB LPDDR5x-7467 MHz
    Graphics card(s)
    Integrated Intel Arc
    Sound Card
    Poly Studio
    Monitor(s) Displays
    14" 2.8K OLED multitouch
    Screen Resolution
    2880 x 1800
    Hard Drives
    2 TB PCIe NVMe M.2 SSD
    Internet Speed
    Intel Wi-Fi 7 BE200 (2x2) and Bluetooth 5.4
    Browser
    Chrome and Edge
    Antivirus
    Windows Defender and Malwarebytes Premium
i send Brink
 

My Computer

System One

  • OS
    Windows 11 Pro insiders
    Computer type
    PC/Desktop
    Screen Resolution
    Full HD
    Browser
    Microsoft Edge Chromium Canary
    Antivirus
    Eset Smart Security Premium
Back
Top Bottom