Guide · Windows 10 & 11 · Updated October 2026
Windows move to the wrong monitor after sleep
Your monitor goes to sleep, and every window that lived on it is suddenly stacked on another screen. Windows didn’t lose them – for a moment it genuinely believed that monitor was gone, and moved everything somewhere visible. It just never moves them back.
What actually happens
Windows keeps every display in one large virtual coordinate space. Your second screen might occupy the region starting at x = 1920, and a window sitting there has coordinates inside that region.
When a display leaves the desktop, that region stops existing. Any window still positioned there would be invisible and unreachable, so the window manager pulls it back onto a surviving display – normally the primary one. That behaviour is deliberate and it is the right call: an unreachable window is worse than a misplaced one.
The part that hurts is the return trip. When the display comes back, the region reappears – but nothing restores the windows to it. Windows keeps no per-window record of where each one used to be, so the pile stays piled.
Why it happens to some setups and not others
The usual trigger is not sleep itself. It is that the monitor stops reporting its presence to the graphics card, which is electrically indistinguishable from someone pulling the cable out. This is where the cable matters more than anything else:
- DisplayPort uses a Hot Plug Detect line. On a great many monitors, entering standby drops that line – so the GPU is told the display was disconnected, and Windows rebuilds the desktop without it.
- HDMI generally keeps its presence signal alive through standby. The display stays part of the topology, and windows stay where they are.
That single difference explains the most common version of this complaint – “it happens on my main monitor but never on the TV I use as a second screen”. The TV is on HDMI.
Other things that produce the same effect: undocking a laptop or a USB-C/Thunderbolt dock renegotiating on wake, a KVM switch handing the display to another computer, a graphics driver update or a driver crash and recovery, and a monitor that briefly loses its input signal.
The fixes, cheapest first
Turn on Windows 11’s built-in memory
Go to Settings → System → Display → Multiple displays and enable Remember window locations based on monitor connection. Enable Minimize windows when a monitor is disconnected as well – minimized windows survive the collapse without being relocated. Windows then stores an arrangement per monitor configuration and replays it when that configuration comes back.
Limits: Windows 11 only. It remembers exactly one arrangement per configuration, misses windows whose app repositions them on its own, and frequently loses the race when the reconnect and the wake happen at the same moment.
Stop the monitor from disappearing
Attack the cause rather than the symptom. Connect the affected monitor over HDMI instead of DisplayPort if it supports your resolution and refresh rate there; switch the monitor to another input instead of powering it off when you step away; or, on monitors that offer it, set the DisplayPort version to 1.2 instead of 1.4 in the on-screen menu – on a number of panels this changes how standby is handled.
Limits: HDMI may cap you below your panel’s full refresh rate, and not every monitor exposes a DisplayPort version setting.
Hold the connection open in hardware
A display emulator dongle (also sold as an EDID emulator or headless display adapter) sits on the port and keeps presenting a display to the graphics card no matter what the monitor does. As far as Windows is concerned, the screen never left.
Limits: costs money, occupies a port, and matching the emulated resolution to your monitor takes a little care.
Docks and KVMs: firmware, then wiring
If a dock or KVM is in the chain, update its firmware before anything else – display renegotiation on wake is one of the most commonly patched behaviours in that category. Where you can, connect the main monitor straight to the graphics card and leave secondary screens on the dock.
Limits: defeats some of the point of a one-cable dock.
Last resort: clear the cached display configurations
Windows caches every display topology it has seen under
HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration. When one of those entries goes stale, monitors can come back with the wrong resolution or in the wrong order. Deleting the subkeys forces Windows to detect everything fresh.Limits: this discards all saved display arrangements, including the ones fix 1 relies on. Export the key first (right-click → Export) and set a restore point.
Why doesn’t Windows simply put them back?
Because a window’s position belongs to the application, not to the operating system. Windows can ask an app to move a window, but it has never kept a durable record of where every window belongs – and many applications overwrite whatever position they are given with one they saved themselves.
The setting in fix 1 is Microsoft’s answer to exactly this, and within its limits it works. What it deliberately does not offer is named layouts: one arrangement for focused work, another for a meeting, a third for when the laptop is on its own.
Where DeskScene comes in
DeskScene remembers – and puts them back
DeskScene takes a snapshot of your windows every few minutes and right before sleep. When a monitor drops out and comes back, it waits until the setup is stable and restores the last snapshot of that setup – automatically. Or save your arrangements as named scenes and bring any of them back with a click, a hotkey or deskscene --load "Deep Work".
It runs entirely on your PC, needs no account and stores its scenes as plain JSON.
15-day free trial, then €9.99 once. No subscription.