Mouse jiggler for Windows 11: stopping the lock screen

Why the usual fixes are greyed out

On a managed laptop the screen timeout, the lock timer and the password-on-wake requirement all come from Group Policy or an MDM profile such as Intune. That is why the sliders under Settings > System > Power and Personalization > Lock screen are missing, disabled, or reset within minutes of you changing them — the value is being pushed down from a policy, not stored locally.

This is by design rather than a bug. Registry edits to the screen-saver timeout, and third-party "keep awake" utilities, tend to get reverted at the next policy refresh, which on most domains runs roughly every 90 minutes. Chasing the setting is a losing game, because the setting is simply not yours to own.

Power settings hold the screen, not the input

Even when the sliders are editable, power and lock-screen options only decide when the display dims or sleeps. That is a different question from whether the machine looks active. Trackers, and the presence dots in Teams or Slack, read the input stream — the time since your last keystroke or mouse event — so a lit screen with no input still counts as idle.

This is why "caffeine"-style tools that only stop the display from sleeping do nothing for your activity percentage or your presence status: they hold the monitor, not the clock that actually matters.

• Screen timeout — the display only.
• Lock and idle timers — input events.
• Presence and activity — time since the last input.

The three timers Windows 11 runs at once

On a work laptop three separate clocks can mark you "away", and they do not share a value. The display timeout dims the screen. The lock timer sends you to the sign-in screen after a set idle period. And above the operating system, your tracker or chat app runs its own idle threshold — often one to five minutes with no input.

Solving one leaves the others running. You can force the display to stay lit and still be marked away in Teams, because Teams never looked at the display — it looked at input. Any real fix has to feed the one signal all three timers read: input events.

Why a basic mouse jiggler stalls on Windows 11

The classic mouse jiggler nudges the pointer a single pixel on a fixed loop, and Windows 11 works against that in two ways. Enhanced pointer-precision settings can absorb a one-pixel move so it never registers as real motion, and inside a remote desktop or virtual session the tiny synthetic move may be filtered out before the tracker ever sees it.

Even when the motion does register, a dead-straight line repeating on an exact interval is the easiest possible pattern for a modern tracker to notice — the subject of the detection write-up in the related links. A jiggler that "works" on paper can still leave you marked idle, or leave a mechanical signature. This is where hardware dongles and simple scripts hit their ceiling.

• Single-pixel moves absorbed by pointer settings.
• Synthetic input filtered inside RDP or virtual machines.
• A fixed loop is the easiest pattern to spot.

What a presence app supplies instead

A presence app does not fight Group Policy; it supplies the events the timers are waiting for. Instead of one repeated twitch, it produces smooth, varied cursor paths, navigation keys in a living rhythm, occasional scrolling and the odd window switch — the ordinary texture of a person at a desk. No policy is touched and nothing is reconfigured; the machine simply stops going quiet.

The behaviour that matters most is restraint. It starts only when the computer is genuinely idle and hands control straight back the instant you move the mouse, so it never fights you while you are actually working.

• Starts only when the computer is idle.
• Gives control back at your first mouse move.
• Varied timing and paths, not a fixed loop.

Hardware mouse mover or software?

A hardware mouse mover — a USB dongle, or a phone on a slow turntable — has one advantage: it plugs in with no install, so it sidesteps a policy that blocks software. The trade-off is that it drives the pointer on a crude mechanical loop with no idea whether you are back at the desk, and that even, repetitive motion is exactly what a pattern-aware tracker flags.

A software presence app is the opposite trade: it needs to install, but it varies its behaviour, mixes mouse and keyboard, and steps aside the moment you return. On a machine where you can install ordinary apps, software wins on how natural the result looks; where you truly cannot install anything, a dongle is the only door left.

Where the limit still is

One honest limit remains. If your policy blocks installing software, that restriction holds — Reaction is an ordinary desktop app and installs like any other, so a locked-down machine that refuses new programs will refuse it too. It changes what the computer reports while you are away, not what your company permits.

Where Reaction fits

Reaction sits in one narrow place: the stretches when you step away from a Windows 11 machine but the session should stay alive — the coffee, the stretch, the school run. It keeps a natural, human-like level of presence within a range you set, using varied cursor motion, a living keyboard rhythm, occasional scrolling and window switches, and it starts only when the computer is genuinely idle and steps aside the moment you touch the mouse.

It cannot make low-input work look like high-input work while you are actually at the desk — that is a limit of how the timers work, not a feature to sell. What it does is stop a normal break from reading as an absence. Use it within your agreements; see the acceptable-use note below.