InputMapper worked on Windows 10, you upgraded to Windows 11, and now something is off: the controller is not detected, exclusive mode fails, inputs double, or the program behaves differently from one boot to the next. You are not imagining it. InputMapper’s final build dates from May 2020, before Windows 11 existed, so it runs on Windows 11 without ever having been officially supported there. This guide gets that combination working as reliably as it can — and is honest about when switching tools is the better answer.
Our dedicated Windows 11 hub collects the short version of these fixes. This post is the full walkthrough, in the order you should apply it after an upgrade.
Step 1: Rebuild the Driver Stack in the Right Order
A Windows upgrade can leave a driver stack that looks installed but is ordered or registered in a way InputMapper 1.7 no longer expects. The cleanest recovery is to rebuild the stack in order rather than patching it in place. The order that works is: InputMapper’s output driver first, any controller-hiding tool second, and InputMapper itself last.
Start with ViGEmBus, the driver InputMapper 1.7 uses to create its virtual Xbox 360 controller. If it is damaged or missing after the upgrade, follow our ViGEmBus install guide to install version 1.22.0 from GitHub releases and reboot. Next, if you use a hiding tool, make sure it is HidHide rather than the legacy stack (the next sections explain why). Finally, reinstall or repair InputMapper itself so its components register against the fresh drivers. Test after the rebuild with no launcher running before you change anything else.
Step 2: Recheck Detection and Profiles
After an upgrade, confirm the basics still hold. Windows should list your controller in the Game Controllers panel (joy.cpl), InputMapper should list the same controller in its device view, and your profile should load and start. InputMapper loads profiles from an online server, so allow it through your firewall if profile loading stalls after the upgrade; a fresh Windows 11 firewall profile can treat the program as new. It is also worth backing up your profiles once everything works again.
If the controller is not detected at all on Windows 11, do not assume the upgrade broke InputMapper specifically. Run through the cable, pairing, and Windows-visibility checks first; an upgrade is also when old cables and stale pairings choose to fail. Supported controllers remain the DualShock 4, DualShock 4 V2, Xbox 360, Xbox One, DualShock 3 via Magic-NS, and generic DirectInput and XInput devices.
Step 3: Exclusive Mode on Windows 11
Exclusive mode is the feature that suffers most on Windows 11. InputMapper tries to claim the physical controller so games only see the virtual pad, but modern Windows gives other programs — Steam above all — more chances to open the device first. The symptoms are the exclusive mode failed error or its quiet consequence, double input in games.
The quick mitigations still apply: close Steam and other launchers completely, start InputMapper before them, and run InputMapper as administrator for a test. If exclusive mode then works, your drivers are fine and the issue was contention. If it still fails on a clean boot order, stop fighting the setting and move to the modern hiding method below, which does not depend on InputMapper winning that race.
Step 4: Use HidHide, Not HidGuardian, on Windows 11
Older InputMapper setups hid the physical controller with HidGuardian and HidCerberus, a research stack from 2016 to 2018 that has long been archived. On Windows 11 that legacy stack is the wrong tool: it was never built or maintained for this version of Windows, and leftover components from a Windows 10 install are a common source of strange behaviour after an upgrade.
The modern successor is HidHide v1.5.230 (May 2024), built for Windows 10 and 11 on x64. It hides the physical controller from everything except whitelisted applications, so you whitelist InputMapper and games only ever see the virtual Xbox controller. Our HidHide guide gives the full setup and explains the differences if you are migrating from the legacy stack. If your Windows 11 problems involve hidden devices, double input, or exclusive mode, this migration is the single change most likely to settle all three at once.
Step 5: Check Steam’s Role Separately
Windows 11 upgrades often coincide with a fresh Steam install or reset Steam settings, which can quietly re-enable PlayStation Configuration Support. With that option on, Steam grabs PlayStation controllers itself and InputMapper’s output doubles or conflicts. Turn PlayStation Configuration Support off in Steam settings, or set Steam Input to Forced Off per game, and retest. Keep this diagnosis separate from the driver work above: if double input happens only in Steam games, it was never a Windows 11 driver problem. Our troubleshooting hub links the dedicated Steam conflict guide.
When to Switch Tools Instead
There is a point where loyalty to InputMapper costs more time than it saves, and Windows 11 is often where users reach it. InputMapper is closed-source freeware by DSDCS whose final build, 1.7.7452.13622, was built in May 2020. It will not receive Windows 11 fixes, new controller support, or updates of any kind.
Switch tools in these cases. If your controller is a DualSense, InputMapper never supported it in the first place — follow our DualSense on PC guide for working options. If you want a maintained mapper for a DualShock 4, the DS4Windows continuation, ds4windowsapp v3.5 from February 2026, is the actively developed route; the original Ryochan7 line ended at 3.3.3 in December 2023 and its repository is now gone. Our DS4Windows install guide will help you make the switch. And if you play mainly Steam games, Steam Input alone may cover your needs without any external mapper at all.
None of that means you must abandon InputMapper today. For a supported DualShock 4 with a clean ViGEmBus install and HidHide hiding the physical pad, InputMapper on Windows 11 is a perfectly workable setup. The honest summary is: rebuild the stack, hide with HidHide, keep Steam in check — and if your hardware or patience has moved on, move tools with it.
Frequently Asked Questions
Is InputMapper officially supported on Windows 11?
No. InputMapper runs on Windows 11, but its final build dates from May 2020, before Windows 11 existed, so it was never officially supported there. Most problems after an upgrade come from the driver stack, exclusive mode contention, or legacy hiding tools rather than the program itself.
What order should I reinstall drivers on Windows 11?
Install ViGEmBus 1.22.0 first and reboot, then set up HidHide if you hide your controller, then reinstall or repair InputMapper last. Test with no game launcher running before changing other settings, and allow InputMapper through the firewall so its online profiles can load.
Should I use HidGuardian or HidHide on Windows 11?
Use HidHide. HidGuardian is a legacy, archived stack from 2016 to 2018, while HidHide v1.5.230 is maintained for Windows 10 and 11 and hides the physical controller per application through a whitelist, which fixes most exclusive mode and double input problems.
When should I switch from InputMapper to another tool?
Switch if you use a DualSense, which InputMapper never supported, or if you want a maintained mapper for the DualShock 4. The DS4Windows continuation, ds4windowsapp v3.5, is actively developed, while InputMapper’s final build from May 2020 will receive no further updates.