A second monitor that's black after sleep, a display that disappears and reshuffles all your windows, brightness that comes back wrong — these aren't one bug. Windows treats each connector differently when the PC sleeps: HDMI usually just power-saves, while DisplayPort, USB-C, and Thunderbolt often get removed from the system entirely and re-added on wake. Here's what's actually happening at each connection type, and the specific parts PowerDoze can restore — brightness and your desktop icon layout — versus the parts that are purely Windows' job.
Quick answer: Whether your monitor "won't wake" depends on the cable. HDMI monitors usually just go into power-save and come back; DisplayPort / USB-C (DP Alt Mode) / Thunderbolt monitors are frequently fully removed and re-added by Windows on sleep, so they act unplugged — windows move and brightness resets. That removal/re-add is Windows and the graphics driver, and no app can prevent it or force a monitor to reappear. What PowerDoze can do is restore each monitor's brightness reliably after it comes back (identifying screens by hardware identity, not port) and restore your desktop icon layout (Pro).
When Windows sleeps or turns off the display, it doesn't do the same thing to every monitor — the behavior comes from how each connector signals presence:
| Connection | How Windows treats it on sleep | What you typically see | What PowerDoze helps with |
|---|---|---|---|
| HDMI | Usually just power-save; stays enumerated | Screen goes dark, comes back; occasionally the monitor's input auto-switch leaves it black | Restores brightness on your return (away-dimming) and on reconnect/startup; icon layout if a disconnect did reshuffle (Pro) |
| DisplayPort (native) | Often fully removed on sleep, re-added on wake | Display "disappears," windows pile onto other screens, brightness back to default | Restores brightness after re-add (matched by EDID, not display number); icon layout (Pro) |
| USB-C (DP Alt Mode) | Same as DisplayPort — carries DP underneath, so removed/re-added | Same disappear/reshuffle as DisplayPort; may re-enumerate as a "new" display | Same as DisplayPort — brightness restore + icon layout (Pro) |
| Thunderbolt / dock | DP under the hood; the dock hop can add its own re-enumeration | Disappear/reshuffle; a dock can make the same monitor look "new" after wake | Brightness restore still keyed to EDID; a port/dock change can look like a new display (re-nudge the slider once) |
| Laptop internal panel | Sleeps with the system; brightness works differently than external monitors | Comes back with the system; brightness sometimes not where you left it | Restores the panel's brightness on wake, alongside externals |
| USB adapter (DisplayLink-type) | Indirect-display USB graphics, not DP Alt Mode | May not expose brightness control at all | Brightness control often unavailable (hardware/driver limit) — icon layout still applies (Pro) |
"What PowerDoze helps with" is always after Windows has brought the display back. It never keeps the monitor awake or forces detection.
On HDMI, sleep normally just puts the monitor into power-save. Windows keeps the display in its list, so your window layout usually survives and the screen comes back when Windows sends video again. When an HDMI monitor stays black after wake, it's most often the monitor's own input auto-switching (it jumped to another input and didn't jump back) or a slow HDMI handshake — cycling the monitor's input button, or unplugging and replugging the cable, brings it back. Because the display stayed known to Windows, HDMI rarely loses its brightness in the first place; when it does, PowerDoze re-applies your saved level on your return (its away-dimming restore) and on startup or a reconnect event.
DisplayPort's hot-plug signalling is exactly why DP monitors are the ones that "vanish." On sleep, Windows can remove the monitor from the system; on wake, it re-adds it as if you'd just plugged it in. That's what scatters your windows onto the remaining screen and can reset resolution — and it's also why brightness comes back at the monitor's default, since to Windows it's a freshly connected display. The internal number Windows assigns it can even change. None of that is preventable by an app, but PowerDoze re-identifies the monitor by its stable hardware identity (EDID) rather than by that number, so it re-applies your brightness to the right screen even after a renumber.
A USB-C monitor running DP Alt Mode is carrying DisplayPort over the USB-C connector — so as far as sleep behavior goes, treat it exactly like DisplayPort. It's prone to the same remove-on-sleep, re-add-on-wake disappearing act, and it may re-enumerate as a "new" display when it returns. Software brightness control usually works over DP Alt Mode just like native DisplayPort, so PowerDoze controls and restores it the same way. (This is different from a DisplayLink-type USB adapter — see below — which often has no way to control brightness at all.)
Thunderbolt carries DisplayPort underneath as well, so its sleep behavior matches DisplayPort — plus the dock or hub itself can add another layer of re-enumeration when the system wakes, occasionally making the same physical monitor look brand-new to Windows. PowerDoze still matches on EDID, so it restores brightness to the correct monitor across a wake. The one honest caveat: moving a monitor to a different port or dock can occasionally present it as a genuinely different display — if a monitor comes back at the wrong level after that kind of change, nudging its slider once re-applies and re-saves it instantly.
Your laptop's built-in screen sleeps and wakes with the system, and it controls brightness completely differently from an external monitor — it runs through the same system channel as your brightness function keys. PowerDoze reads and restores both kinds, so the built-in panel returns to your chosen level right alongside your external monitors — on your return (away-dimming), on startup, and on a display-change event — in one place, without you touching the brightness keys again.
The clearest way to set expectations is to split the problem into "the OS owns this" and "an app can help here":
| Behavior | Who controls it | Can PowerDoze change it? |
|---|---|---|
| Setting how long until an idle monitor sleeps (timeout) | Windows power plan | Yes (free) |
| Actively dimming brightness while you're away, before sleep | PowerDoze | Yes (Pro) |
| Actually putting the monitor into power-save / sleep | Windows + monitor firmware | No |
| DisplayPort/USB-C display removed on sleep, re-added on wake | Windows + graphics driver | No |
| Making a "missing" monitor be detected again | Windows + driver | No |
| Window positions / resolution after reconnect | Windows | No |
| Restoring each monitor's brightness after wake/reconnect | PowerDoze | Yes |
| Restoring desktop icon positions after a reshuffle | PowerDoze (Pro) | Yes |
In other words: PowerDoze doesn't fight Windows over when a monitor actually falls asleep or reconnects — it can't, and neither can anything else. What it does do: let you set how long until a monitor sleeps, actively dim brightness to save power while you're away, and — once Windows brings a monitor back — restore its brightness and your desktop icon layout.
Set a brightness level per monitor once — the laptop panel included, plus every external monitor. PowerDoze saves it against that monitor's stable hardware identity (EDID), not the port or the internal number Windows happens to assign it, and re-applies it automatically: on startup, and when Windows reports a display reconnecting or the layout changing. It also offers away dimming — it detects when you've stepped away and lowers real backlight to save power, then restores each monitor when you return or after a reboot. That away-restore path is the robust one: it verifies each monitor came back to the right level and keeps retrying across a slow-waking or briefly-disappeared external monitor instead of giving up on the first miss, so a DisplayPort screen that took a few seconds to re-appear still lands on your brightness rather than a default. Any monitor it can't yet match is brought up to a safe, readable level — never left stuck dark.
Honest note: This restores brightness only — not window positions, resolution, or refresh rate. External control needs the monitor itself to support software brightness adjustment, which most monitors of the last decade do, but some budget/older displays and DisplayLink-type USB adapters don't (those still need their physical buttons). Moving a monitor to a different port or dock can occasionally make it look like a new display — nudge its slider once to re-apply. Free, no account required.
When a DisplayPort/USB-C monitor drops on sleep, Windows reflows your desktop icons to fit the smaller space and doesn't put them back when the monitor returns. PowerDoze's Desktop Layout Guard snapshots your icon positions (periodically while all monitors are connected, and when you add/rename/delete desktop items), then restores them — matched by icon name — once your monitor count returns to the highest it's seen. It reads and writes positions the same way Windows Explorer itself does — no code injection, nothing that looks like malware to antivirus software.
Honest note: This restores desktop icon positions, not open window positions. It needs to be running to catch the disconnect; if it wasn't, press Save once after you've tidied up to set a fresh baseline. Desktop Layout Guard is a Pro feature (one-time purchase, not a subscription).
It depends on the connection. Over HDMI, the monitor usually just went into power-save mode and normally comes back when Windows sends video again — if it stays black, it's often the monitor's own input auto-switch or a slow handshake. Over DisplayPort, USB-C (DP Alt Mode), or Thunderbolt, Windows frequently removes the display from the system entirely on sleep and re-adds it on wake, so it behaves like it was unplugged and replugged: windows move, resolution can reset, and it can take a moment to reappear. This is Windows and graphics-driver behavior, not an app putting the monitor to sleep or waking it.
If it's on HDMI, the panel is likely in power-save and the signal or the monitor's input selection hasn't re-synced — cycling the monitor's input button or replugging the cable usually brings it back. If it's on DisplayPort or USB-C, Windows may have removed the display on sleep and is still re-adding it, so for a few seconds there's genuinely no display for Windows to draw to. Either way it's an OS/driver timing issue at the connection layer, not a setting you forgot.
DisplayPort (and USB-C DP Alt Mode and Thunderbolt, which carry DisplayPort underneath) support hot-plug detection that Windows acts on aggressively: on sleep it can fully remove the monitor and on wake re-add it as if newly connected. HDMI is generally treated more like a fixed connection that just power-saves, so the monitor stays roughly "known." That's why DisplayPort and USB-C setups are the ones where windows shuffle and the display briefly vanishes.
For staying put across sleep, HDMI is often less disruptive because Windows tends to leave the monitor enumerated and just power-saves it. DisplayPort, USB-C, and Thunderbolt give you higher bandwidth and daisy-chaining but, because Windows removes and re-adds them on sleep, they're more prone to the disappear/reshuffle behavior. Neither is broken — they're handled differently by the OS. PowerDoze behaves the same across all of them because it identifies each monitor by its EDID, not by which port it's on.
Windows doesn't save a brightness level for external monitors, and when a DisplayPort/USB-C display is removed and re-added on wake it comes back at the monitor's or driver's default. Nothing in Windows re-applies your chosen level. PowerDoze does: it re-applies your saved level on startup and when Windows reports a display reconnecting, and its away-dimming restores each monitor when you return — matching by stable EDID identity even when Windows renumbered the display, and (on the away-return path) retrying across a slow-waking monitor instead of giving up on the first miss.
No — and it doesn't claim to. PowerDoze can't keep a monitor awake, prevent it disconnecting on sleep, or force Windows to re-detect a display; that removal/re-add is entirely the OS and graphics driver. What it does is restore each monitor's brightness after the OS brings it back, and (Pro) restore your desktop icon layout after Windows reshuffles it. It does not restore window positions, resolution, or refresh rate on reconnect.
Some USB display adapters (DisplayLink-type docks and USB-to-HDMI/DVI adapters) use a different kind of technology that often doesn't let software control brightness at all — that control channel isn't there for the computer to reach. That's a hardware/driver limitation of that adapter type, not something an app can work around; those screens still need their physical buttons. It's different from a USB-C monitor running DP Alt Mode, which behaves like a normal DisplayPort connection and usually does let software adjust brightness.
Windows handles HDMI, DisplayPort, USB-C, and Thunderbolt differently on sleep — but you shouldn't have to re-fix brightness every time a monitor comes back. Set it once per monitor in PowerDoze and it re-applies itself. Free, no account required.
Download free for Windows 10/11See also: Set brightness per monitor that sticks · Fix desktop icons rearranging after a monitor unplug · Keep an external monitor on with the laptop lid closed · All features