The current screen size is wrong?

[Tudsday]

powershell.ps1

Add-Type -AssemblyName System.Windows.Forms
$bounds = [System.Windows.Forms.SystemInformation]::VirtualScreen

Write-Host "W=$($bounds.Width) H=$($bounds.Height) X=$($bounds.X) Y=$($bounds.Y)"

output: W=2560 H=1440 X=0 Y=0

But my monitor is 4K. Why is the reading error?

[JeremyKuhne]

This is not a DPI aware method. This is likely related to the DPI settings for the window you're running in. Consider using the https://learn.microsoft.com/dotnet/api/system.windows.forms.screen class to see if you can get what you're looking for.

[Tudsday]

This is not a DPI aware method. This is likely related to the DPI settings for the window you're running in. Consider using the https://learn.microsoft.com/dotnet/api/system.windows.forms.screen class to see if you can get what you're looking for.

Screen(Bounds, PrimaryScreen, WorkingArea)
I tested them all, but I couldn't get the correct values. In fact, my workspace size is indeed 4K, and the monitor size is also 4K. I hope you can help me.

[JeremyKuhne]

@Tudsday This is all related to the current DPI settings. I'm not super familiar with the nuances of PowerShell and the Terminal, but with help from CoPilot, this works for me.

PowerShell 7.5.1
PS D:\repos> Add-Type -AssemblyName System.Windows.Forms
PS D:\repos> [System.Windows.Forms.Application]::SetHighDpiMode([System.Windows.Forms.HighDpiMode]::PerMonitorV2)
True
PS D:\repos> [System.Windows.Forms.Screen]::AllScreens | ForEach-Object {
>>     [PSCustomObject]@{
>>         DeviceName = $_.DeviceName
>>         Bounds     = $_.Bounds
>>         Width      = $_.Bounds.Width
>>         Height     = $_.Bounds.Height
>>         Primary    = $_.Primary
>>     }
>> }

DeviceName : \\.\DISPLAY801
Bounds     : {X=0,Y=0,Width=3440,Height=1440}
Width      : 3440
Height     : 1440
Primary    : True

DeviceName : \\.\DISPLAY802
Bounds     : {X=-1055,Y=-2160,Width=5120,Height=2160}
Width      : 5120
Height     : 2160
Primary    : False

DISPLAY802 will give scaled results without the first call (running at 150% on that one).

[Tudsday]

@Tudsday This is all related to the current DPI settings. I'm not super familiar with the nuances of PowerShell and the Terminal, but with help from CoPilot, this works for me.

PowerShell 7.5.1
PS D:\repos> Add-Type -AssemblyName System.Windows.Forms
PS D:\repos> [System.Windows.Forms.Application]::SetHighDpiMode([System.Windows.Forms.HighDpiMode]::PerMonitorV2)
True
PS D:\repos> [System.Windows.Forms.Screen]::AllScreens | ForEach-Object {

    [PSCustomObject]@{
        DeviceName = $.DeviceName
        Bounds     = $.Bounds
        Width      = $.Bounds.Width
        Height     = $.Bounds.Height
        Primary    = $_.Primary
    }
}

DeviceName : \.\DISPLAY801
Bounds : {X=0,Y=0,Width=3440,Height=1440}
Width : 3440
Height : 1440
Primary : True

DeviceName : \.\DISPLAY802
Bounds : {X=-1055,Y=-2160,Width=5120,Height=2160}
Width : 5120
Height : 2160
Primary : False
DISPLAY802 will give scaled results without the first call (running at 150% on that one).

Why does the system win11 have.NET 4.8 installed,
Powershell is still running on. Net 4.0, which prevents the code you gave you from passing.
Please help me.

[Tudsday]

PS C:\Users\Yuan> $PSVersionTable

Name Value

---

PSVersion 5.1.26100.4202
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.26100.4202
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

---

I wonder why Microsoft's default PowerShell version is so low that.NET 4.8 cannot be loaded? What should I do?