Wrong screen resolution reported when display scaling is not at 100%

[dejvizelo]

My laptop has a 1920x1080 display and it uses 125% display scaling. Winfetch shows the resolution as 1535x864. However it reports the correct resolution when scaling is set to 100%.

[rashil2000]

We are reporting the actual workable screen area, with scaling adjusted. We can shift to reporting the actual resolution, but it's slightly more difficult if you have multiple screens (because of multiple WMI queries), and that would also make it quite slower. You'll lose out on any information about scaling too.

[dejvizelo]

I see. Thanks for the answer. As a suggestion, maybe in the future it can be implemented in a way that gives the user the freedom of choice between the two approaches (let this comment serve as a feature request I guess).

[ferdinandk55]

I fixed it by using

"$($(Get-CimInstance -ClassName Win32_VideoController).CurrentHorizontalResolution) x$($(Get-CimInstance -ClassName Win32_VideoController).CurrentVerticalResolution)"

instead of Monitor.Bounds.Size

Top is with normal, bottom with change.

[HO-COOH]

@ferdinandk55 This does not work for mulitiple monitor.

[baraa272]

i still have this issue too

[TheNewJavaman]

I also have this issue (side note: GitHub needs issue voting). Screenshot in case it helps:

The first screen is 2560x1440 at 150% scaling.

[BobbyWibowo]

Hi there, is there no plan to merge the relevant PRs yet?

[jomaskm]

Came here to post about this. Would be nice to have the option to choose if winfetch should show actual set resolution or "effective" resolution when using scaling. Have it set to 125% myself.

[rashil2000]

Came here to post about this. Would be nice to have the option to choose if winfetch should show actual set resolution or "effective" resolution when using scaling. Have it set to 125% myself.

Given how regressive (performance-wise) #131 is, this might actually be a better idea. Would you like to work on this?