Styjun

In windows, I can use the identify button in the display control panel to display a number on each monitor corresponding to their ID in windows display manager.

Can I, preferably using powershell, show these ID temporarily just like clicking the button.

If it's not possible to get to show the ID as windows does it, would it be possible to popup a window in a specific monitor display ?

My goal is to get a monitor to show information on itself either by correlating display id with WMI information or by showing a window with the current monitor information.

For example, let's say i have 4 monitor in a 2x2 matrix. All the monitors are the same models, only thing that would change is the serial numbers. Using WMI, i can get information on the monitors, but is there a way to know which monitor is which physically?

1. What have you tried?


2. Where is your code and what is not working?


3. What do you search for?

There are many classes for examining virtually every part of Windows and hardware.

Win32 Classes

Get-WMIObject -List | 
Where$_.name -match "^Win32_" | 
Sort Name | Out-Gridview

Look for the ones that are for video or monitor

Get-WMIObject -List | 
Wheremonitor" | 
Sort Name | Out-Gridview

Then play around with each until you see which one gives you what you need.

Get-WmiObject win32_desktopmonitor | ft -a

DeviceID DisplayType MonitorManufacturer Name ScreenHeight ScreenWidth
-------- ----------- ------------------- ---- ------------ -----------
DesktopMonitor1 Default Monitor
DesktopMonitor2 (Standard monitor types) Generic PnP Monitor 1080 1920
DesktopMonitor3 Lenovo Wide viewing angle & High density FlexView Display 1920x1080 1080 1920
DesktopMonitor4 (Standard monitor types) Generic PnP Monitor 1080 1920
DesktopMonitor5 Default Monitor
DesktopMonitor6 Default Monitor

For your other use case, displaying popups or toast info is well documented and there are modules you can download for that.

Example: BurntToast

Module for creating and displaying Toast Notifications on Microsoft
Windows 10.

Are you saying you are trying to replicate what the Windows Settings provide as a permanent display like say BGInfo does?

That is a whole project, not a simple script.

Update for the OP

Understood, and as per my response, I have 4 monitor on my laptop, Well 3 external and the laptop monitor.

For correlation of course that means using combined results from other cmdlets / classes.

Example:

Get-CimInstance -ClassName win32_desktopmonitor | 
Select Name, DeviceID, PNPDeviceID | 
ft -a

Name DeviceID PNPDeviceID 
---- -------- ----------- 
Default Monitor DesktopMonitor1 
Generic PnP Monitor DesktopMonitor2 DISPLAYACI27F68&5458763&0&UID256 
Wide viewing angle & High density FlexView Display 1920x1080 DesktopMonitor3 DISPLAYLEN41214&90CEFB8&0&UID265988
Generic PnP Monitor DesktopMonitor4 DISPLAYACI21839&2E298509&0&UID256 
Default Monitor DesktopMonitor5 
Default Monitor DesktopMonitor6 



(Get-CimInstance -ClassName Win32_PnPEntity) -match 'monitor' | 
Select Name, Manufacturer, HardwareID, PNPDeviceID | 
ft -a

Name Manufacturer HardwareID PNPDeviceID 
---- ------------ ---------- ----------- 
Generic PnP Monitor (Standard monitor types) MONITORACI27F6 DISPLAYACI27F68&5458763&0&UID256 
Generic PnP Monitor (Standard monitor types) MONITORACI27F6 DISPLAYACI27F68&5458763&0&UID257 
Generic PnP Monitor (Standard monitor types) MONITORACI2183 DISPLAYACI21839&2E298509&0&UID256
WAN Miniport (Network Monitor) Microsoft ms_ndiswanbh SWDMSRRASMS_NDISWANBH 

Yet, even here, it gets hinky with matching up the PNPDeviceID's for identical vendor monitor types.

Again, this why what you are asking for is a real project. NNot just a simple script. Meaning it may require very potentially diving in to C++ code to get the depth control need to do the. The code has to get to the settings, drivers, adapter to do this. Then combine all that together. That is a good deal of work, and not something that can prudently be handled on a Q&A like this.

Example see this Q&A.

EnumDisplayDevices vs WMI Win32_DesktopMonitor, how to detect active monitors

What you see and get in Windows settings, is implemented via several under the cover libraries (DLL) to do this reliably, which you first need to discover to consume and learn how to use or writing your own.

We all love us some PowerShell, but it is not the answer to everything standalone.

Burnt toast will only pop where the system tray is docked.

So, you now would have to write your own GUI form(s) (WPF) to position on whatever screen as needed.