Fix Cursor Moving to Second Monitor in Counter-Strike 1.6

Last updated: June 16, 2026

Cursor escaping to your second monitor in Counter-Strike 1.6? Fix it with raw input, true fullscreen, Xbox Game Bar, and registry tweaks – real working fixes.

You’re mid-round, flick right, and the cursor escapes to your second monitor in Counter-Strike 1.6. The game minimizes or loses focus. Round over. This is a known dual-monitor problem on GoldSrc, and it has gotten worse on Windows 10 and 11. Several fixes exist for cs 1.6 cursor moving to second monitor – some permanent, some workarounds. Start from the top.

Why CS 1.6 can’t lock the cursor on dual monitors

CS 1.6 uses ClipCursor(), a Windows API call that confines the cursor to a defined rectangle on screen. In true exclusive fullscreen this works reliably because the game owns the entire display. The problem is GoldSrc’s fullscreen implementation is old and was never built with multi-monitor setups in mind. Windows 10 and 11 changed how fullscreen applications interact with the cursor clip region, and GoldSrc’s ClipCursor() call gets overridden – particularly after Xbox Game Bar is opened for the first time, or after certain Windows updates.

The result: the cursor clip releases mid-game, the cursor drifts to the second monitor, the game loses focus, and you die.

Enable raw input

Open the CS 1.6 console and run:

m_rawinput 1

Raw input bypasses Windows mouse processing and reads directly from the hardware device. This doesn’t technically lock the cursor to your screen, but for most players it keeps the cursor glued to the game’s input context and stops it from drifting, especially combined with true fullscreen. Note: m_rawinput only works on Steam – Non-Steam builds do not support it.

A small number of players report the opposite issue with raw input enabled – the cursor gets trapped inside a small rectangle and cannot aim outside that area. If that happens to you, set m_rawinput 0 and rely on the other fixes below instead.

Add the working value to autoexec.cfg to make it permanent:

Non-Steam: cstrike\autoexec.cfg
Steam: Steam\steamapps\common\Half-Life\cstrike\autoexec.cfg

Force true fullscreen

Windowed and borderless windowed mode don’t clip the cursor at all – it is free to move anywhere on the desktop. If you are running in either of those modes, switching to true exclusive fullscreen is the first real fix to try.

Steam launch options: right-click Counter-Strike, Properties, Launch Options:

-full

Non-Steam shortcut: right-click the hl.exe shortcut, Properties, add -full to the end of the Target field.

True exclusive fullscreen gives GoldSrc full control of the display and lets ClipCursor() do its job. On most setups this alone stops the cursor from escaping.

Disable Xbox Game Bar

This is the most common trigger on Windows 11. Opening Xbox Game Bar (Win + G) for the first time changes how Windows handles cursor confinement in fullscreen applications, and the change persists after you close it. Games that were fine before suddenly develop the escaping cursor issue after a single Game Bar open.

To disable it: Settings, Gaming, Xbox Game Bar, toggle off Enable Xbox Game Bar.

If it has already been opened and the problem is active, disabling it going forward helps but may not fully revert the existing state. The more thorough option is removing it via PowerShell (run as admin):

Get-AppxPackage *Microsoft.XboxGamingOverlay* | Remove-AppxPackage

Reboot after running this and test CS 1.6 before and after to confirm it was the cause.

Registry fix – MouseMonitorEscapeSpeed

Windows has a registry value that controls how aggressively the cursor is allowed to cross monitor boundaries. Setting it slows down cursor escape from a fullscreen application.

Press Win + R, type regedit, navigate to:

HKEY_CURRENT_USER\Control Panel\Desktop

Look for MouseMonitorEscapeSpeed. If it doesn’t exist, right-click in the right pane, select New, DWORD (32-bit) Value, and name it MouseMonitorEscapeSpeed. Double-click it and set the value to 1.

Reboot and test. This doesn’t fully prevent cursor escape in every case but significantly reduces how easily the cursor bleeds to the second monitor during fast mouse movement.

Arrange monitors diagonally in Windows Display Settings

A practical workaround that needs no software or registry edits. Windows respects monitor boundary placement – if your monitors are arranged so the shared edge is diagonal rather than straight across, the cursor needs to hit a precise diagonal angle to cross over, which almost never happens during normal gameplay movement.

Settings, System, Display, drag the monitor icons so they overlap diagonally instead of sitting edge-to-edge. Even a small offset makes cursor escape during fast horizontal flicks much less likely. It sounds like a hack because it is, but it works.

Use windowed borderless plus a cursor locker tool

If true fullscreen causes other problems – resolution switching on alt-tab, black screen issues, or incompatibility with your streaming setup – windowed borderless is the alternative. The cursor will escape in borderless without a locker, but a couple of lightweight, widely-used tools lock it to the primary display.

Dual Monitor Tools (free, open source) – download from SourceForge. After installing, open it, go to the Cursor section, set it to Sticky, and configure a hotkey to lock and unlock the cursor to the main screen. Press the hotkey before loading into a server. This is the most commonly recommended fix across multiple games with the same dual-monitor cursor problem, not just CS 1.6.

Cursor Locker – a simpler tool available on GitHub. Set it to lock to the foreground window title (hl or Counter-Strike), and it confines the cursor automatically whenever CS 1.6 has focus.

Both tools release the cursor when you alt-tab out, so you can use your second monitor normally between rounds.

Disable edge swiping via Group Policy

On Windows 11 Pro, a Group Policy setting controls cursor behavior at screen edges. Disabling it stops the cursor from snapping across to the adjacent monitor during fast movement.

Press Win + R, type gpedit.msc, navigate to:

Computer Configuration > Administrative Templates > Windows Components > Edge UI

Find Allow edge swiping, set it to Disabled, click Apply, and reboot. This reduces but doesn’t entirely eliminate cursor escape, but combined with raw input and fullscreen mode it is usually enough.

Note: gpedit.msc is only available on Windows 10/11 Pro, Education, and Enterprise. Home edition does not include it.

Set CS 1.6 as primary display application

If your second monitor is set as the primary display and CS 1.6 launches on the secondary one, cursor confinement can behave erratically. CS 1.6 should run on whichever monitor Windows considers primary.

Settings, System, Display, click your main gaming monitor, scroll down, and check Make this my main display.

Then launch CS 1.6 and confirm it opens on the primary monitor. If it keeps launching on the wrong screen, use the -full launch option and set the game resolution to match the primary monitor’s resolution exactly.

Dual monitor cursor issue after a Windows update

If this started right after a Windows update and nothing else changed, the update likely modified how Windows handles cursor clipping in fullscreen applications – this has happened with several Windows 11 feature updates. Options:

• Roll back the update – Settings, Windows Update, Update history, Uninstall updates, find the most recent one, uninstall, reboot
• Apply the Game Bar fix and registry tweak above – compensates for the changed behavior without requiring a rollback
• Wait for a follow-up Windows update – Microsoft has acknowledged similar cursor-clipping regressions as bugs in some builds before

Rolling back isn’t always practical, so the Game Bar disable plus the MouseMonitorEscapeSpeed registry value is usually the faster path.

CS 1.6 dual monitor cursor: what each fix addresses

Frequently asked questions

Why did this start happening suddenly when it worked fine before?

Three most likely causes: Xbox Game Bar was opened for the first time (Win + G), a Windows update changed cursor clipping behavior, or CS 1.6 switched from fullscreen to a windowed mode. Check which applies and start there.

Does the -full launch option actually force exclusive fullscreen in CS 1.6?

Yes, for CS 1.6 on GoldSrc. Unlike some newer games where fullscreen flags get mapped to borderless, GoldSrc honors -full and enters true exclusive fullscreen, where it owns the entire display output.

Will Dual Monitor Tools affect my second monitor while CS 1.6 isn’t running?

No. The cursor lock only applies when the hotkey is active. Tap the hotkey to lock before a match, tap it again to release when you want to use your second monitor. Many players bind it to something simple like Ctrl+Alt+F.

Raw input is already on and the cursor still escapes – what now?

Raw input helps but doesn’t fully solve it for everyone. Combine it with the -full launch option and the Game Bar disable. If those three together don’t fix it, try the MouseMonitorEscapeSpeed registry value or a cursor locker tool. If raw input is causing the opposite problem – the cursor trapped in a tiny box – turn it off and rely on the other fixes instead.

My second monitor goes black when CS 1.6 launches in fullscreen – is that related?

That is a separate issue caused by exclusive fullscreen taking over the display output and blanking secondary monitors – normal behavior on some setups. Running borderless windowed plus a cursor locker tool keeps both monitors active while still confining the cursor.

Cursor on second monitor in CS 1.6 – where to start

Raw input on (Steam only), fullscreen forced, Game Bar disabled. Those three changes together resolve it for most people with a dual monitor setup, no third-party tools needed.

If it came back after a Windows update, the registry fix and Game Bar removal are the fastest path back to normal. If you need borderless windowed for streaming or other reasons, get Dual Monitor Tools and set a lock hotkey – a short one-time setup and you won’t think about it again.