Your bindings work in Notepad, the mouse moves on the desktop, and then the game starts and nothing happens. This is the single most reported AntiMicroX pattern, and it is the deep-dive companion to our cluster guide on how to fix AntiMicroX not working. That guide gives the overview; this post stays on one scenario — desktop works, game does not — and explains the three families of causes behind it: privilege level, window focus, and display or overlay behaviour. Understanding which family you are in saves hours of random reinstalling.
The elevation explanation, stated factually
Windows separates programs by integrity level through a mechanism called User Interface Privilege Isolation, or UIPI. A program running at a lower integrity level cannot send synthetic input to a window running at a higher level. If a game or its launcher is running elevated with administrator rights while AntiMicroX runs as a standard user, Windows will block AntiMicroX input to that game window — not because AntiMicroX is broken, but because that blocking is exactly what UIPI is designed to do. On the desktop, where everything runs at the same level, the same bindings work fine, which is why the pattern looks so confusing.
The factual fix is to match levels for that test: check whether the game or launcher is set to run as administrator, and understand that the mapper and the game need compatible privilege levels for input to pass. We do not advise setting AntiMicroX to always run as administrator as a permanent habit. Running everyday software elevated widens what any bug or malicious file could do through it. The safer approach is to first check whether the game actually needs elevation at all — many do not — and to lower the game back to standard level if that setting was added by habit, a compatibility tweak, or an old guide.
Focus: the game must actually be the active window
AntiMicroX sends keyboard and mouse output to the system, and that output goes to the window that has focus. If a launcher stays in front, a chat overlay holds focus, or the game launched behind another window, your inputs can land somewhere harmless and invisible. Test deliberately: start the game, click once inside its window, wait until you are on a menu or in a safe area, and only then test a binding you can see, such as a mapped key that opens a menu. Alt-tab behaviour matters too. Some games pause input handling when they lose focus and do not resume cleanly. If bindings work before your first alt-tab and fail afterwards, you have learned something specific — note it, and test a run where you do not alt-tab at all. Auto Profiles add a related subtlety: they switch profiles based on the active window. If focus detection picks the launcher instead of the game, you may be testing the wrong profile entirely. Temporarily select your game profile manually and retest before blaming the bindings.
Fullscreen, borderless and overlay causes
Display mode changes how a game receives mouse input. Some older engines in exclusive fullscreen handle the mouse in a way that discards or fights simulated movement, while borderless windowed mode lets the normal Windows input path work. If only mouse look fails while mapped keys work, switch the game to borderless or windowed fullscreen as a controlled test — that split result points at the display path, not at your whole setup. Overlays are the next suspect. Steam, Discord, GPU vendor overlays and recording tools inject their own hooks into the game window. Any one of them can change focus or intercept input.
Disable overlays one at a time for testing, starting with the platform overlay for the launcher you use. If you suspect Steam specifically, our guide to Steam Input conflicts covers the double-input and remapping side in depth. Also check whether the game has its own native controller support fighting you: a game that reads the pad directly while AntiMicroX also sends keys can produce doubled or contradictory actions. In that case, decide on one path — native support or mapping — rather than layering both.
A disciplined test order and honest limits
Work in this order and change one thing at a time. First, confirm the bindings work on the desktop with the exact profile you intend to use. Second, launch the game, give it focus, and test in a menu. Third, check elevation: is the game or its launcher running as administrator when AntiMicroX is not? Fourth, test borderless mode. Fifth, disable overlays for one run. Keep notes on which step changed the result, because that note is the diagnosis. If a title uses kernel-level anti-cheat that filters synthetic input, a mapper may simply have its input ignored in that title; that is a property of that protection system, not something a settings tweak in AntiMicroX can promise to bypass, and you should use the game’s native controller support there instead. Finally, make sure you are on a current build from the download page before concluding anything — old copies preserved from predecessor projects are a common source of strange, already-fixed behaviour.
A quick checklist before you change settings
Before editing any compatibility option, run this five-minute checklist and write down each result. One: with the exact profile loaded, do the bindings work in a text editor? Two: in the game menu, after clicking once inside the window, does a single safe binding work? Three: is the game, its launcher, or any helper process set to run as administrator? Four: does switching the game to borderless windowed mode change the result at all? Five: with every overlay disabled for one launch, does behaviour improve? Stop as soon as one step changes the outcome, because that step has identified the family of the cause — elevation, focus, or the display and overlay path. Changing five things at once feels faster, but it destroys the evidence you need, and it often leaves a permanent setting in place that was never necessary for your system.
Keep exploring
- General AntiMicroX troubleshooting guide — the cluster overview for all common faults.
- Download AntiMicroX 3.6.1 — official GitHub release channel with hash information.
