Multi-monitor setups are fantastic until a game launches on the wrong screen. You hit play and the action appears on your secondary panel — often the slower one — while your main gaming display shows the desktop. It is a small thing that ruins the moment every single time. The fix depends on how the game handles displays, so here is a full toolkit that covers fullscreen, borderless, and stubborn titles alike.
Set your primary display correctly
Most fullscreen games default to the Windows primary display, so make the right monitor primary. Open Settings, System, Display, click the monitor you game on, and check Make this my main display. This alone solves the majority of cases because launchers, fullscreen games, and the taskbar all follow the primary flag.
Use the in-game display selector
Many modern games expose a Display or Monitor dropdown in their video settings. If yours does, simply pick the correct monitor number. Not sure which is which? Windows can show large identifying numbers on each screen via the Identify button in Display settings, and games usually match that numbering.
Move borderless and windowed games
Borderless titles ignore the primary-display flag more often, but Windows has a shortcut: with the game window focused, press Win + Shift + Left or Right arrow to fling it to the adjacent monitor. For a windowed game, you can also just drag the title bar across. Once moved, the game usually remembers the position next launch.
| Game display mode | Best method |
|---|---|
| Exclusive fullscreen | Set the target monitor as Windows primary |
| Borderless windowed | Win + Shift + Arrow to shift screens |
| Windowed | Drag the window, or Win + Shift + Arrow |
| Has a monitor dropdown | Select the display in video settings |
Handle the stubborn cases
A few games hard-lock to a specific GPU output or remember an old monitor arrangement. If nothing sticks, delete or rename the game’s config file (often found in Documents or the AppData folder) so it regenerates with fresh display data. As a last resort, temporarily unplug the secondary monitor, launch the game so it binds to the only screen available, then reconnect the second display.
Watch out for refresh-rate mismatches
When a game jumps to the wrong monitor, it may also inherit that panel’s lower refresh rate. After moving the game, confirm in its settings that it is running at your gaming monitor’s full refresh — for example 144 Hz or 240 Hz — rather than defaulting to 60 Hz. This is an easy detail to miss once the picture is finally on the right screen.
Set monitor priority in your GPU software
Both NVIDIA and AMD control panels let you designate which display is treated as primary at the driver level, which some fullscreen games respect even when Windows does not. In the NVIDIA Control Panel this lives under Set up multiple displays, where you can right-click a monitor and make it primary; AMD offers the equivalent in its display section. Combining the driver-level primary setting with the Windows primary flag covers almost every game. For the rare title that stores its chosen display in a cloud save or registry key, a full uninstall of just its settings — not the whole game — forces a clean redetect. Once you find the combination that sticks for a particular game, it tends to stay put through future launches and even most updates.
FAQ
Why does my game always open on the second monitor?
That monitor is probably set as your Windows primary display, or the game saved an old window position. Set your gaming monitor as primary and, for borderless games, move the window once so it remembers.
Can I keep watching a video on my second screen while gaming fullscreen?
Yes. Run the game in borderless windowed mode on your main monitor; exclusive fullscreen can pause or dim the second display’s content, whereas borderless leaves the other screen fully interactive.
Bottom line
Getting a game onto the right monitor is mostly about the Windows primary-display flag and the Win + Shift + Arrow shortcut for borderless windows. Set your gaming screen as primary, use the in-game selector when it exists, and double-check the refresh rate followed the move.
