You're done for the night, so you reach over and switch off the side monitor, leaving the main one on. The instant you do, every window you'd laid out on that side screen stampedes back onto the main one — icons reshuffled, layout wrecked. You turned off one screen. Why did the whole desk just flip?
Here's the thing: your monitor isn't broken, and the cable isn't loose. The real explanation is more subtle than "broken" — Windows doesn't think you dimmed a screen. It thinks you abruptly disconnected the entire monitor from the machine. And that misunderstanding has been part of how DisplayPort works since 2006.
Stick with me and you'll see exactly how this disappearing act works — and why remoting into a machine with its screens off shows you a black void. Then you get three ready-made fixes: one Windows 11 setting, one monitor OSD toggle, one $10 gadget. Pick whichever fits, and it behaves again.
HDMI says "I'm off". DisplayPort says nothing at all.
Both cable standards have a hot-plug detect (HPD) line — the wire that tells the PC "a display is attached". The difference is what happens when the monitor goes to sleep or gets switched off:
- HDMI monitors typically keep the HPD line up. Windows knows the screen is still there, just dark. Topology untouched.
- DisplayPort monitors commonly drop HPD when they power down or enter deep sleep. To Windows, that is indistinguishable from you yanking the cable: the monitor isn't off, it's gone.
And when a monitor is gone, Windows does what it's supposed to do for an unplugged display: it re-arranges the desktop. Windows migrate to surviving screens, the resolution may change, and when the monitor wakes up and re-announces itself, everything re-enumerates — that black-flash dance you see when screens come back. Whether your DP monitor does this depends on the model and its firmware; some keep HPD alive, many don't, and some have an OSD option that decides.
The remote-access version of the problem
Now switch off all the monitors on a DP-only desktop and the machine believes it has no display hardware at all. Tools that stream the physical desktop — Parsec, Moonlight/Sunshine, some AnyDesk modes — suddenly have nothing to capture, or fall back to a tiny virtual panel. (Classic RDP is immune: it creates its own virtual display.) This is why the remote-gaming crowd buys HDMI dummy plugs — a $10 resistor pretending to be a monitor, keeping one "display" permanently attached.
The fix toolbox
- Windows 11's window-memory setting. Settings → System → Display → Multiple displays → enable "Remember window locations based on monitor connection". Microsoft added this specifically for the DP disappearing act: when the monitor re-appears, your windows go back where they were. It doesn't stop the disconnect; it cleans up after it.
- Check the monitor's OSD for "DisplayPort deep sleep". Many Dell, LG and BenQ models have a toggle (sometimes called DP power saving). Turning deep sleep off keeps HPD alive when the screen sleeps — the monitor stays "present" like an HDMI one. Costs a watt or two of standby power.
- For remote access: a dummy plug in a spare HDMI port, or RDP instead of capture-based tools. If the machine is headless-by-design, the dummy plug is the no-surprises option.
Where PowerDoze stands in this
PowerDoze's power modes can turn displays off on a timeout — that's a standard Windows display-off, and on well-behaved monitors it's exactly as reversible as it sounds. But if your DP monitor drops HPD on sleep, the window-scramble above happens on any display-off, whoever triggers it — Windows' own timeout, ours, or the power button on the monitor. No software can change how a monitor's firmware handles its HPD line. What we can do is tell you the fix exists: flip the Windows 11 setting, check the OSD, and multi-monitor DP setups behave again. (For the wider map of sleep settings and their quirks, see the complete guide to Windows sleep settings.)
The short version
DP monitor off ≈ DP monitor unplugged — that's the protocol, not a glitch. Remember-window-locations fixes the scramble, the OSD deep-sleep toggle prevents it, a dummy plug saves your remote sessions. Twenty minutes of setup, and the most annoying multi-monitor behavior on Windows is gone for good.