📎 AI Summary:
The thread discusses a user experiencing resolution and display detection issues with a second monitor connected via a KVM switch on Windows 10, where the monitor is recognized as non-PnP and causes black screens and sleep mode activation. The user originally had display recognition problems since upgrading to Windows 10, unlike their Windows 7 systems which identify the monitors correctly. A respondent suggests checking the multiple displays setup, but the original poster responds that this advice did not resolve the core issue, which centers on Windows 10 not properly identifying the monitor, potentially requiring a registry hack or workaround. Overall, the user is frustrated with the difficulty in resolving monitor detection problems in Windows 10.

paulckruger

Extraordinary Member
Joined
Dec 22, 2016
Messages
3
Thread Author #1
I am dumbfounded.

I have dual monitors and KVM switch. I had issues getting both monitors to function at first as mouse would not move to second monitor. That was direct connect to monitors different brand/resolution but fixed that.

Now I have 4 PC on a rack and use a KVM switch with two identical monitors. For awhile the W10 PC worked okay then other day I noticed moving a window over to #2 it as much larger. Checked and resolution had changed for #2 so I reset to what it should be and the monitor went black.

I switch to another PC ( the others are all Win 7 ) and everything is fine. Switch back to W10, second monitor works again but with an OSD warning of a resolution mis match ( it is not mismatch as set correctly in display controls ) but then monitor goes to sleep. I cannot keep #2 working in W10.

I checked device manager on W10 and W7. In W7 machines both monitors appear as PnP monitors as they should. In Win10 the problem monitor is showing as non-PnP . I suspect this is causing the problem but cannot find any way to get W10 to correctly ID the monitor when I switch KVM back to W10.

There are no drivers for these from HP so uses windows drivers. I have removed device and scanned for changes. It finds non-PnP monitor?

Any clue? Any way even if require registry hack to FORCE this brain dead Win10 to accept this as a PnP monitor correctly?
 

Himend

Well-Known Member
Joined
Feb 14, 2020
Messages
7
You need to fully set up of Multiple displays section because It may cause of problem
 

paulckruger

Extraordinary Member
Joined
Dec 22, 2016
Messages
3
Thread Author #3
All due respect his reply offers zero help to the question asked.