A tiny replacement for Logitech Options+ on Windows. One ~50 KB program, no installer, about 30 MB of memory.
Not made by or affiliated with Logitech.
- Download
MxLite.zipfrom Releases and unzip it to a folder, for exampleC:\Tools\MxLite. - Quit or uninstall Logi Options+ first. Otherwise every click does its action twice.
- Double-click
MxLite.exe. A mouse icon appears in the tray next to the clock. Double-click it for Settings.
- The button under the scroll wheel
- Click: Task View (see all open windows).
- Hold + move the mouse: switch virtual desktops (configurable).
- Hold + move further: jump 2 or more desktops in one hold (Settings: "Move further to jump 2 or more desktops").
- A quick sweep (press, flick, let go) always moves only 1 desktop, however far the mouse travels. Extra desktops need the button held for at least 400 ms (Settings: "Hold before 2nd jump").
- Changed your mind mid-hold? Move back one swipe length and it jumps the other way.
- The two thumb side buttons (optional, off by default)
- Rear = previous desktop, front = next desktop (configurable).
- Or leave them as normal browser back/forward.
- Dragging a window? Hold it with the left button, then switch desktops with a thumb button or the wheel-button swipe. The window comes along. Works for a Chrome tab you are pulling out, too. Settings: "Drag a window along" (on by default). Windows 10 1809 to 22H2 only for now; on Windows 11 the switch happens without the window (Contributing: the interface ids differ per build, see MScholtes/VirtualDesktop).
- The scroll wheel's auto free-spin (ratchety normally, spins free on a hard flick) keeps working. That part lives inside the mouse itself. MxLite can also set how hard a flick it needs.
The rule: the mouse needs BOTH of these.
- A scroll wheel that switches by itself from click-click to free-spin when you flick it hard. Logitech calls this "SmartShift".
- A small button just below or behind the scroll wheel.
MxLite asks the mouse at startup whether it has both. If it does not, MxLite keeps searching and the tray tooltip says "searching for mouse...". Nothing breaks.
| Mouse family | Works? | Why |
|---|---|---|
| MX Anywhere 3, MX Anywhere 3S, MX Master, MX Master 2S, MX Master 3, MX Master 3S (incl. "for Mac" versions) | Expected to work | Same hardware: SmartShift wheel and the button under/behind the wheel. |
| MX Master 4 | Unknown | Newer model. Please open an issue with your mxlite.log if you try it. |
| MX Anywhere 2, MX Anywhere 2S | No | Free-spin is switched by hand, not SmartShift. |
| MX Vertical, MX Ergo, Lift, Pebble, M-series (M185, M330, M720...) | No | No SmartShift wheel. |
| G-series gaming mice | No | Different wheel and software (G HUB). |
| Any non-Logitech mouse | No | MxLite only speaks Logitech's protocol. |
On the "Expected to work" mice, the two thumb side buttons can also be used (Settings, off by default).
Check yours: open mxlite.log next to the exe. A working mouse shows Gesture button active on <your mouse name>.
Works over Bluetooth or the Logi Bolt / Unifying USB receiver. Needs Windows 10 or 11 (64-bit). Nothing else to install.
- Put the folder anywhere. Do not run it from inside the zip.
- Quit or uninstall Logi Options+.
- Double-click
MxLite.exe, then double-click the tray icon to open Settings. Every change applies instantly. - In Settings, tick "Start MxLite with Windows" so it is always on. (Run some apps "as administrator"? Use
install-elevated.cmdinstead, see below.)
Start Menu (optional): run add-startmenu.cmd once and MxLite shows up in the Start Menu.
Settings live in mxlite.ini next to the exe. The Settings window writes it; editing by hand is fine too.
| Key | Meaning |
|---|---|
click, left, right, up, down |
Keys sent by the wheel button: click and hold+move in each direction. Example: Ctrl+Win+Right. Empty = nothing. |
gesture_distance |
Mouse movement needed for the first desktop (default 300). |
repeat |
1 = keep moving to jump several desktops in one hold. 0 = one per hold. |
extra_distance |
With repeat = 1: extra movement for each further desktop (default 450). 300 + 450: 300 = 1 desktop, 750 = 2, 1200 = 3. |
multi_hold_ms |
With repeat = 1: milliseconds after the press before a 2nd desktop (or a turn-back) can happen (default 400). Movement before that is ignored, so a quick sweep moves 1 desktop. 0 = no wait. Settings: "Hold before 2nd jump". |
side_buttons |
1 = thumb buttons send back / forward below. 0 = normal browser back/forward. |
back, forward |
Keys for the rear and front thumb buttons (default Ctrl+Win+Left / Ctrl+Win+Right). |
drag_follow |
1 = a window you hold with the left button moves to the new desktop with you (default). 0 = it stays behind. Only for keys that are exactly Ctrl+Win+Left / Ctrl+Win+Right. Settings: "Drag a window along". |
smartshift |
auto = leave the wheel as the mouse has it. 1-50 = lower spins free on a gentle flick, higher needs a hard flick. |
Key names: Ctrl Shift Alt Win A-Z 0-9 F1-F24 Left Right Up Down Tab Space Enter Esc PgUp PgDn Home End PlayPause NextTrack PrevTrack VolUp VolDown Mute BrowserBack BrowserFwd PrtSc.
MxLite does two things at startup, nothing to set up:
- Runs at HIGH process priority, so the mouse button keeps responding when the CPU is maxed out.
- Pins its ~30 MB of memory in RAM, so Windows does not push it to disk when memory runs low (Logi Options+ does the same).
To check it worked, look for this line near the top of mxlite.log:
priority=High, working set pinned (32 MB hard min).
If it says pin FAILED (rare, e.g. locked-down work PCs), MxLite still runs; it only loses this extra protection.
- Wheel suddenly glides with no click-click, and pressing the wheel does not bring it back? The mouse is stuck in permanent free-spin. That mode is stored inside the mouse, so restarting does not clear it. In Settings, set "Scroll wheel free-spin" to Custom (try 30). That writes ratchet mode back and the notches return at once. Nothing is broken and it is not the battery.
- Button stops responding (rare): turn the mouse off and on. MxLite reconnects within a few seconds.
- Keys do nothing while an "as administrator" app has focus: a Windows security rule (UIPI), not a bug. See the next section.
mxlite.log(next to the exe) shows what the mouse sent. Useful if something misbehaves.
Windows drops keystrokes simulated by a NORMAL program while an ELEVATED ("run as administrator") window has focus. Your real keyboard is never affected. If some of your apps run elevated (VPN clients, some game tools), desktop switching feels dead while one of them is the active window, and nothing in mxlite.log looks wrong.
Fix: run install-elevated.cmd once.
- It creates a Task Scheduler task that starts MxLite as administrator when you log on. One UAC prompt during setup, none at boot.
- It removes the normal Startup-folder shortcut so MxLite does not start twice. Leave "Start MxLite with Windows" unticked.
- Undo any time with
uninstall-elevated.cmd.
- If you used
install-elevated.cmd, rununinstall-elevated.cmdfirst. - Untick "Start MxLite with Windows" in Settings.
- Right-click the tray icon -> Exit MxLite, then delete the folder.
- Turn the mouse off and on once; the buttons are back to factory behaviour. Nothing else is left behind.
No SDK needed: build.cmd uses the C# compiler that ships with Windows (.NET Framework 4.x).
build.cmd
It writes MxLite.exe next to MxLite.cs. Start with MxLite.exe --debug for a console with live log output.
MxLite talks to the mouse directly over Logitech's HID++ 2.0 protocol (features 0x1B04 reprogrammable controls and 0x2110/0x2111 SmartShift).
Pull requests that bring these features to other mice are welcome. Where to start in MxLite.cs:
| Part | What it does |
|---|---|
FindMouse |
Finds a Logitech HID++ 2.0 device that has feature 0x1B04 (reprogrammable buttons) AND 0x2110/0x2111 (SmartShift). |
ApplyDivert / ApplySideDivert |
Tells the mouse to send a button to MxLite instead of Windows. Button IDs: GESTURE_CID 0x00C4, BACK_CID 0x0053, FWD_CID 0x0056. |
HandleEvent |
The gesture logic: click vs. hold+move, multi-desktop jumps, turn-back, side buttons. It only needs "button down/up" and "mouse moved dx, dy", so a new input source can feed it. |
Logitech mice in the "No" rows (MX Vertical, MX Ergo, Lift, MX Anywhere 2S, G-series...). Most of them still speak HID++ 2.0 and have feature 0x1B04. Steps:
- Make SmartShift optional in
FindMouse(today a mouse without 0x2110/0x2111 is skipped) and skipApplySmartShiftwhen it is missing. - List the mouse's buttons: 0x1B04 function 0 gives the count, function 1 gives each button's ID and flags. Pick a button whose flags say it can be diverted, and make the ID a setting instead of the fixed
GESTURE_CID. - Hold+move needs the "raw XY" flag on that button. Without it, read movement from a low-level mouse hook (next paragraph) while the button is held.
- G-series: G HUB's onboard profiles can remap buttons too; quit G HUB while testing.
Non-Logitech mice (any brand). They do not speak HID++. Use a Windows low-level mouse hook (SetWindowsHookEx with WH_MOUSE_LL) instead:
- It sees the middle button, the two side buttons (
XBUTTON1/XBUTTON2) and all movement for any mouse. - Swallow the chosen button (return 1 from the hook) and feed press, release and dx/dy into the same gesture logic as
HandleEvent. - Limit: the hook only sees the 5 standard buttons. Extra buttons that only the maker's software knows about need that maker's protocol.
Testing without a mouse. HandleEvent can be fed fake reports through reflection. Bind harmless keys (F20-F24) in the config so a test run does not switch your real desktops, then read the Sent: lines in mxlite.log.
In your pull request, please name the mouse you tested and paste the mxlite.log lines that show it was found.
MIT, see LICENSE.