Windows 10: Turning off monitor acts as a disconnect to the computer

Taken from previous post, but no solution 2022: https://answers.microsoft.com/en-us/windows/forum/all/turning-off-a-monitor-acts-like-disconnecting-it/c38febe1-4b3c-49b8-98ad-c0fcd0dbc5d0I have two monitors, both connected on DP.When I turn off my secondary monitor, nothing happens. That's good.When I turn off my primary monitor, something happens: Windows acts as though it was disconnected, and moves all windows and desktop icons over to the much smaller secondary monitor, messing up window sizes and icon placement.Turning off a monitor should not act like it's being disconnected. This happ

:)

 

Turning off a monitor acts like disconnecting it

I have two monitors, both connected on DP.

When I turn off my secondary monitor, nothing happens. That's good.

When I turn off my primary monitor, something happens: Windows acts as though it was disconnected, and moves all windows and desktop icons over to the much smaller secondary monitor, messing up window sizes and icon placement.

Turning off a monitor should not act like it's being disconnected. This happened with my previous primary monitor on DP as well. This does NOT happen when I connect either primary monitor (my old one, or the current one) on HDMI.

The solution is NOT to connect my primary monitor on HDMI, because that will disable high fps and HDR.

I'm running the latest Nvidia "game ready" GPU drivers and an up-to-date Windows 10 21H2. My system files are good, says SFC. No viruses or malware either. Just so I don't get that canned response again.

So the question, to be extra super clear: How do I make Windows, when turning off a primary monitor connected to DP, NOT act as if it was disconnected, but leave everything just as it is?

Please advice.

 

Turning off a monitor acts like disconnecting it

Sorry about the SFC commands, I didn't notice when you said you had already executed.

Let's clarify, you have two monitors, as soon as you manually and physically turn off the main monitor, the system understands as if you disconnected the monitor, so it makes your second monitor the main one, putting your entire desktop there, am I right?

System recovery keeping your files and applications solves most system problems, it's hard to say exactly what or how it started, what we know is that it's not normal behavior, and that's why I'd suggest some steps.

This is certainly linked to some kind of system incompatibility with the video drivers.

To clarify, we are just community users, not Microsoft employees.

I suggest that you test from a new user, and if it doesn't solve it, do the recovery keeping your applications and files, only the system image will be reinstalled.

Regards,

Claudeir

 

Display Turn Off in Power Options Causing USB Disconnection

Hello everyone, I'm encountering a peculiar issue related to the Power Options settings on my Windows machine (Version 22H2). Whenever Windows automatically turns off my display, it seems to inadvertently cause the devices connected to my USB hub to disconnect. Here's a more detailed description of the problem:

1. Display Turn Off Issue: After Windows turns off the display, my USB-connected devices disconnect.
2. Wake-Up Login Requirement: When I wake up the monitor with a mouse movement, I'm prompted to log back into Windows, as if the system had entered seep mode or logged off.

Steps I've Taken So Far:

• Set Power Options to never enter sleep mode.
• Disabled hibernation and USB selective suspend.
• Restored default power settings using "powercfg -restoredefaultschemes".
• Imported power options from "Default_Power_Plans.zip" found on this forum.
• Analyzed settings with PowerSettingExplorer, but nothing unusual was noted.
• Checked the event log and Sleep Study report ("pwrcfg -systemsleepdiagnostics") for any signs of the machine being put to sleep, but found none.

Interestingly, this problem does not occur when I manually turn off the monitor. It only happens when Windows does it automatically. Also, this issue is not isolated to one machine; it's happening on several, which leads me to believe it's not a hardware issue. I'm looking for any suggestions on how to further diagnose and resolve this issue. Your input would be greatly appreciated!