PowerShell script returning the wrong screen resolution

Question

I just wrote a simple PowerShell script to get the screen resolution of my monitor, but it seems to be returning the wrong values.

# Returns an screen width and screen height of maximum screen resolution
function Get-ScreenSize {
    $screen = [System.Windows.Forms.Screen]::PrimaryScreen
    $width  = $screen.Bounds.Width
    $height = $screen.Bounds.Height
    return $width, $height
}

Get-ScreenSize

I am running this script on a 4k monitor with the resolution set at 3840 x 2160, but it is giving me the following output:

1536

864

Is there anything that would cause System.Windows.Forms.Screen to get the wrong "Bounds" values?

What values do you get when using the WorkingArea instead of the Bounds property? — IInspectable
– IInspectable, Commented Mar 12, 2016 at 21:58
I get 3840 x 2060 which is very close, but still not quite correct. — tjwrona
– tjwrona, Commented Mar 12, 2016 at 21:59
That looks correct. Full width, and height minus the taskbar. — IInspectable
– IInspectable, Commented Mar 12, 2016 at 22:00
Okay, hmm then I wonder why bounds is returning the wrong value... — tjwrona
– tjwrona, Commented Mar 12, 2016 at 22:01
Looking at the reference implementation for Screen, it looks like Bounds uses the virtual screen size (not entirely sure, why the numbers are smaller than expected, though), while WorkingArea uses the multi-monitor API. I don't know how to fix the PowerShell commandlet, though. — IInspectable
– IInspectable, Commented Mar 12, 2016 at 22:14

tjwrona · Accepted Answer · 2016-03-13 02:30:34Z

6

Well I didn't exactly find out why I was getting such strange results... but I did find another approach that actually seems simpler and appears to be accurate.

$vc = Get-WmiObject -class "Win32_VideoController"
$vc.CurrentHorizontalResolution
$vc.CurrentVerticalResolution

This will print the current screen resolution and appears to be giving me accurate results which is what I was actually looking for. If anyone figures out what could cause the other approach to produce inaccurate results I would still really like to know why it is happening though...

answered Mar 13, 2016 at 2:30

tjwrona

9,09710 gold badges44 silver badges118 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Julian Chow · Accepted Answer · 2018-02-20 15:28:44Z

1

It's because that command gives you the scaled resolution. If you're running 3840 x 2160 but you're not running on 100% scaling you'll get a different value.

answered Feb 20, 2018 at 15:28

Julian Chow

764 bronze badges

1 Comment

tjwrona Over a year ago

That is very interesting, but I guess it makes sense if that's the command apps use internally to scale themselves properly.

Community · Accepted Answer · 2017-05-23 11:50:40Z

-2

That's odd.

Why on earth has Microsoft only provided the Get-DisplayResolution cmdlet with Server Core?

That edition ships without a Start-button... and according to the comment above on the returned display size (minus start-bar); I won't be surprised to hear that cmdlet is using the same .NET code library.

Quick search in my HKLM\SYSTEM\CurrentControlSet\Control lists a few keys for monitors and values per screen, but nothing useful.

Edit: see Q7967699.

PS D:\Scripts> Add-Type -AssemblyName System.Windows.Forms

PS D:\Scripts> [System.Windows.Forms.Screen]::AllScreens


BitsPerPixel : 32
Bounds       : {X=0,Y=0,Width=3840,Height=2160}
DeviceName   : \\.\DISPLAY1
Primary      : True
WorkingArea  : {X=0,Y=0,Width=3840,Height=2120}

edited May 23, 2017 at 11:50

CommunityBot

11 silver badge

answered Mar 13, 2016 at 0:15

M.M.

1514 bronze badges

Collectives™ on Stack Overflow

PowerShell script returning the wrong screen resolution

3 Answers 3

Comments

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related