Every button press happens twice. Menus jump two entries at a time, a single tap opens and instantly confirms a dialog, and characters dodge when you only wanted to walk. Double input is the classic sign that your game is seeing two controllers where there should be one: the physical pad and the virtual Xbox controller that InputMapper creates from it. This guide helps you work out which of the three common causes you have, then fix it properly.
Double input is closely related to the exclusive mode failed error — when InputMapper cannot claim and hide the physical pad, double input is usually the result. Start there if you are seeing that warning, and use this guide to confirm the fix in your games.
How Double Input Happens
InputMapper reads your DualShock 4 or other supported controller and outputs a virtual Xbox 360 controller through ViGEmBus. That design only works if the original device is hidden. If the physical controller stays visible, a game can receive the same press from two different devices at the same moment. The game is not broken, and your controller is not faulty. Windows is simply presenting both devices, and the game is listening to both.
There are three distinct causes, and each has a different fix. First, the physical pad is not hidden at all. Second, Steam Input is mapping the controller on top of InputMapper’s mapping. Third, the game itself reads both XInput and DirectInput at the same time. Guessing wastes time, so spend two minutes on the triage below before changing settings.
Triage: Which Cause Do You Have?
Cause 1: The physical pad is not hidden
Disconnect from your game and open the Windows Game Controllers panel by running joy.cpl. With InputMapper running and your controller connected, look at the device list. If you can see both the physical DualShock 4 (often listed as a wireless controller) and the virtual Xbox 360 controller, the physical pad is not hidden. This is the most common cause, and the fix is the HidHide setup in the next section.
Cause 2: Steam Input is double-mapping
If double input only happens in Steam games, and especially if the doubling stops when you close Steam completely, Steam Input is the likely culprit. Steam’s built-in mapper can read the physical pad and translate it at the same time as InputMapper, producing two mapped outputs. The full walkthrough is in our guide to the InputMapper and Steam Input conflict, and the short version appears later in this guide.
Cause 3: The game reads both XInput and DirectInput
Some games, particularly older titles and some emulators, listen to XInput and DirectInput simultaneously by design. In those games the virtual Xbox pad and the physical pad both register even when everything else is configured correctly. The giveaway is that double input happens in one specific game while others are fine, and joy.cpl or other games show no problem. Hiding the physical pad with HidHide still solves this case, because there is then only one device left for the game to read.
The Main Fix: Hide the Physical Pad with HidHide
HidHide is the modern tool for this job. HidHide v1.5.230, released in May 2024 for Windows 10 and 11 on x64, hides a physical controller from every program except the ones you whitelist. It replaces the legacy HidGuardian and HidCerberus stack from 2016 to 2018, which is archived and should not be installed today. Our step-by-step HidHide guide has the full setup, and the summary below is enough to fix double input in most cases.
Step 1: Whitelist InputMapper
Install HidHide and open its configuration client. On the Applications tab, add InputMapper’s executable to the whitelist. This step is essential and the order matters: InputMapper must be allowed to see the physical controller, because it is the program that reads it and creates the virtual pad. If you cloak the device before whitelisting InputMapper, InputMapper will lose sight of your controller too. That outcome looks alarming but is easy to reverse by unticking the cloak, adding the whitelist entry, and cloaking again.
Step 2: Cloak the DualShock 4
On the Devices tab, find your physical controller and tick the option to hide it, then enable device hiding. From this moment, games and launchers can no longer see the physical pad at all. Only whitelisted applications, which in this setup means InputMapper, retain access. Restart InputMapper if it was already running so it picks up the new state cleanly, and reconnect the controller if prompted.
Step 3: Verify with joy.cpl
Open joy.cpl again. You should now see only the virtual Xbox 360 controller in the list for normal applications, while InputMapper still shows your physical controller in its own device list. Press a few buttons in the Game Controllers test screen and confirm each press registers once. Then launch the game that was doubling and test the menus, which is where double input is easiest to spot. One press should move one entry. If it does, the fix is complete and will survive reboots, because HidHide reapplies the cloak automatically.
If Steam Is the Cause
When the triage points at Steam, open Steam settings and turn off PlayStation Configuration Support, which is the classic switch that makes Steam grab PlayStation controllers. For individual games, open the game’s properties in your library, go to the Controller section, and set Steam Input to Forced Off so that game uses InputMapper’s virtual pad only. Also check Big Picture controller settings, because a configuration enabled there can apply even when you launch games from the desktop client.
Test with one game before changing your whole library. If Forced Off removes the doubling in that title, apply the same per-game setting to other affected titles. Remember that turning Steam Input off for a game means that game relies entirely on InputMapper, so keep InputMapper running before you launch it. The reverse situation, where Steam Input alone is the better tool, is covered in our comparison of InputMapper vs Steam Input.
If One Game Still Doubles
For a single stubborn game that reads both input paths, first confirm the HidHide cloak is active and joy.cpl shows only the virtual pad. If the game still doubles, check whether the game has its own controller settings that select a specific device, and point it at the Xbox 360 controller explicitly. Some games also store a device choice in their configuration from before your fix, so reselecting the controller inside the game can be necessary even after Windows is correct.
Also test the game with the controller connected by USB if you normally play over Bluetooth, and the other way around. A game that behaves differently per connection type is telling you the physical device is still visible on one path, which sends you back to the HidHide checks rather than to the game’s settings. Do not respond by installing additional mapping tools on top of InputMapper. Stacking mappers almost always makes double input worse, not better.
Keeping the Fix in Place
Once double input is gone, leave the setup alone. Keep InputMapper as your only mapper for this controller, keep HidHide’s whitelist limited to InputMapper and any other tool you deliberately use, and start InputMapper before your launchers. If you later add a new controller, remember that InputMapper supports the DualShock 4, DualShock 4 V2, Xbox 360, Xbox One, DualShock 3 via Magic-NS, and generic DirectInput and XInput devices, but not the DualSense or Switch Pro Controller. A new unsupported pad will need a different tool rather than more InputMapper settings. More fixes live in our troubleshooting hub, and general questions are answered in the InputMapper FAQ.
Frequently Asked Questions
Why is my controller pressing buttons twice in games?
Your game is seeing both the physical controller and the virtual Xbox controller created by InputMapper, so each press arrives twice. Hide the physical controller with HidHide, whitelisting InputMapper so it can still read the pad, and verify in joy.cpl that only the virtual controller is visible.
How do I check if my physical controller is hidden?
Run joy.cpl to open the Windows Game Controllers panel. With InputMapper running, you should see only the virtual Xbox 360 controller listed. If the physical DualShock 4 also appears, it is not hidden and games can read it directly.
Can Steam cause double input with InputMapper?
Yes. If Steam Input maps the controller at the same time as InputMapper, the game receives two mapped outputs. Turn off PlayStation Configuration Support in Steam settings, or set Steam Input to Forced Off for the affected game in its library properties.
Is HidGuardian still the right tool to hide my controller?
No. HidGuardian is a legacy project from 2016 to 2018 that has been archived. HidHide v1.5.230 is the modern successor: it hides the physical controller per application through a whitelist and is the recommended fix for double input on Windows 10 and 11.