morgot.blogg.se - Disable monitor windows 10

I have also hunted in my monitor settings menus, trying to find settings for the power saving mode, but couldn't locate anything useful.

In my own research, I've heard tell that this is due to a feature called Transient Multimon Manager (TMM), which in previous versions of windows could be disabled via the registry ( ), however the registry key is not present in W10.Īnother workaround ive seen is to use the Nvidia Control Panel to do an EDID override so that the driver will always report the same monitor status/capability regardless of whats plugged in, or whether its off, however the settings pane where I should be able to do that is missing from my Nvidia Control Panel

When unlocking the computer, or coming back after being away more than 10 minutes, all of my windows and icons have been rearranged. When the computer is locked, the backlight on the primary display constantly turns on and off every couple of seconds The effect being two astonishingly annoying things: This is even worse when the computer is locked, because after detecting the "new monitor" and switching modes, Windows immediately tries to put the monitor to sleep, at which point it thinks the monitor was unplugged and repeats. Even worse, the mode switch causes the primary monitor to wake up again, at which point it is re-detected, re-enabled, some of the windows move back until it goes idle again and the whole process repeats. This causes the desktop environment to move everything over to the secondary monitor.

The trouble is that whenever the new monitor goes to sleep (turns off the backlight), for example when I lock my computer, or if it is idle for a sufficient period of time, W10 seems to think that the monitor has been disconnected entirely and disables it. While actively using the computer everything is great for the most part.

My current setup is the new monitor connected by DisplayPort, and a secondary monitor connected by HDMI. I just got a brand spankin' new monitor (yay!), but am having trouble how W10 is working with it (boo!).