When a window opens on a disconnected monitor

Why does a program window open on a disconnected monitor?

The program saved its window position while the auxiliary display was connected, and it reopens the window at that saved spot even though the display is gone. A window parked on a second screen lands outside the laptop desktop when only one screen remains.

Most programs check whether the saved position lies on a display that still exists and fall back to the main screen when it does not. A program that applies the saved position unchanged places its window at coordinates the laptop cannot show. The symptoms are consistent: the process runs, the taskbar button is present, Alt+Tab lists the program, and the screen stays empty.

Nothing about this needs the missing display to be reconnected. The system menu of a window works even when the window sits off-screen, and that menu is the way back in.

How do you move an off-screen window with the keyboard?

Select the program with Alt+Tab, open its system menu with Alt+Space, press M for Move, tap an arrow key, then steer the window onto the laptop screen and press Enter. That is seven keystrokes and about a minute.

Run it in this order:

1. Look at the taskbar. A button for the program means a window exists to move. No button and no Alt+Tab entry means the program is closed, so start it once and continue.
2. Press Alt+Tab until the program is the active window.
3. Press Alt+Space. The system menu of that window opens, with Restore, Move, Size, Minimize, Maximize and Close, even though the window itself is off-screen.
4. Press M. Move is now active.
5. Press any arrow key once. The window attaches and follows your movement.
6. Tap or hold the arrow key pointing toward the laptop screen until the title bar slides into view.
7. Press Enter to drop the window, then position it fully on the laptop desktop with the mouse.

Practice the sequence once on a window you can see: Alt+Space opens the menu, M starts the move, an arrow key engages it, Enter places it. Thirty seconds of rehearsal means you are not learning the keys while a production window is stranded.

If the menu that appears belongs to another program, reselect with Alt+Tab and press Alt+Space again. For programs that ignore Alt+Space, Ctrl+Click in the window's upper-left corner opens the same menu in some applications.

Why is the Move command grayed out?

A maximized window has Move unavailable on its system menu, because a maximized window has no free position of its own. Press Alt+Space, then R for Restore, then Alt+Space and M again, and the floating window moves with the arrow keys.

Restore hands the window back its previous floating size, and a floating window has a position to change. Walk it onto the laptop with the arrow keys and press Enter. If the menu still refuses to offer Move after a Restore, reselect the window with Alt+Tab and repeat the sequence; a menu aimed at the wrong window helps nobody.

Example: you unplug a 21-inch monitor, where does the window go?

Take a laptop at 1920 x 1080 beside a 21-inch auxiliary screen at 1920 x 1080, with a 1200 px wide program window centered on the auxiliary screen. Unplug the monitor, and the window reopens at pixel x = 2280, wholly outside the visible 1920 px desktop.

The setup:

• Laptop display: 1920 x 1080 px, desktop columns x = 0 through x = 1919.
• Auxiliary monitor: 21-inch, 1920 x 1080 px, placed to the right, desktop columns x = 1920 through x = 3839.
• Program window: 1200 px wide, closed while centered on the auxiliary screen.

The arithmetic: centered on the auxiliary screen, the window's left edge sits at 1920 + (1920 − 1200) / 2 = 2280 px. The next morning the monitor is unplugged, the desktop is 1920 px wide, and the program reopens the window at x = 2280. That is 2280 − 1919 = 361 px past the last visible pixel column, so no part of the window shows and there is no edge for the mouse to grab.

The rescue in the same numbers: the window must travel at least 361 px left before its first column enters the laptop desktop, and 2280 − 719 = 1561 px left before the whole 1200 px width sits on it, left edge at 719 px and right edge at 719 + 1200 = 1919 px. Press Alt+Tab, Alt+Space, M, one tap of the left arrow, then hold the left arrow and watch the right edge of the laptop screen. The title bar enters view, most of the window follows, press Enter, and square it up with the mouse. The whole rescue is seven keystrokes to start the move plus the held arrow key, and it takes about a minute. Close the program now, with the window on the laptop, and tomorrow's launch opens there.

If this window had been maximized on the 21-inch screen, the menu offers no Move; run Alt+Space, R first, exactly as in the section above. These are example numbers: your resolution and window width change the distances, never the sequence.

What do the results tell you?

Each outcome names its own cause: a window that returns with Move had a stale saved position, a grayed Move means a maximized window, a window that reappears on the reconnected monitor was never lost, and nothing selectable at all means there is no window to move.

• Window returns with Move. The saved placement was the whole fault. Finish by closing the program on the laptop so the next launch uses that position.
• Move unavailable. The window is maximized. Restore with Alt+Space, R, then run the Move sequence again.
• Window shows on the auxiliary monitor when you reconnect it. Nothing was stranded; the program still has it placed there. Drag it onto the laptop while both displays work, close the program, then disconnect.
• No taskbar button and no Alt+Tab entry. The program is closed, or its window is not a movable document window. Launch it once; if the new window also opens off-screen, run the sequence on it.
• Windows still lists the second display after the cable is out. The display state is the problem, and the keyboard sequence moves one window; switch to laptop-only in display settings first, then place the window.

Keep two neighbouring faults separate. When the screen hardware itself goes dark, a shop-floor display that goes blank and freezes points to power first. And when a player's picture never appears on the second display at all, the fault is signal and input, which is a different diagnosis with its own first check.

How do you stop the window stranding again?

Close the program while its window sits wholly on the laptop display, then disconnect the auxiliary monitor, and the next launch opens on the laptop, because the program saves the last position its window held.

1. With both screens connected, bring the program window onto the laptop display, using the keyboard sequence if it is still stranded.
2. Place it fully inside the laptop desktop, clear of the boundary between the two screens.
3. Close the program.
4. Disconnect the auxiliary monitor.
5. Relaunch the program and confirm it opens on the laptop.

Recommendation: Rescue a stranded window with Alt+Tab, Alt+Space, M and the arrow keys, and from then on close the program on the laptop display before you disconnect the auxiliary monitor. That one habit prevents the recurrence, because the program saves the laptop position as its last one. If a launch still strands the window after a visibly closed exit, fix the display state in Windows first: a monitor the system still lists keeps its coordinates on the desktop, and windows will keep opening onto them.

How do you test the laptop-only launch?

Rehearse the exact transition that caused the trouble: both displays connected, the program closed with its window on the laptop, the auxiliary monitor unplugged, the program relaunched. The test passes only when the window is visible on the laptop with no keyboard rescue, about five minutes end to end.

A pass means the saved position now belongs to the laptop and the habit has taken hold. A failure has two branches, and reconnecting the auxiliary monitor tells them apart. A window sitting on the auxiliary monitor means the program saved that position once more: run the placement routine once more, close visibly, and retest. No window selectable anywhere means the fault is launch or display, and placement was beside the point; check that the program starts at all before touching display settings again.

Diagnose one failure cycle, correct once, retest. Relaunching again and again without changing where the window was closed leaves the saved position exactly where it was.

Questions