You open InputMapper, connect your DualShock 4, and instead of a clean connection you get the warning that InputMapper failed to connect exclusively. The controller may still appear in the device list, it may even work in some menus, but games read double inputs, ignore the pad entirely, or behave as if two controllers are fighting for control. That exclusive mode error is one of the most common InputMapper problems, and it usually means something else reached the physical controller before InputMapper could hide it.
This guide works through the fixes in the order that solves the problem most often, starting with quick checks that take under a minute. If you are also seeing double inputs in games, see our double input fix as well.
What Exclusive Mode Actually Does
InputMapper takes a physical controller, most often a DualShock 4 or DualShock 4 V2, and presents it to Windows as a virtual Xbox 360 controller through the ViGEmBus driver. Games that expect an Xbox pad then work without any extra configuration. For that trick to work cleanly, the original physical controller has to be hidden from games. Otherwise the game sees both devices at once: the real DirectInput pad and the virtual XInput pad.
Exclusive mode is InputMapper’s attempt to claim the physical device for itself so other programs cannot read it directly. When it fails, InputMapper leaves the physical pad exposed, and any game that reads both input paths will double-register presses or pick the wrong device. Every step below is about removing whatever grabbed the controller first, or hiding it with a more modern tool.
Quick Check 1: Close Competing Apps First
The most frequent cause is another program opening the controller before InputMapper does. Steam is the best-known example, but game launchers, other controller tools, and even some web browsers with gamepad support can hold the device open. A controller can only be claimed exclusively by one program at a time, so whoever gets there first wins.
Close Steam completely, not just to the system tray. Do the same for other launchers you have running, and close browser tabs or windows if you have been testing your pad on a gamepad tester site. Disconnect any other controller software for the moment as well. Then restart InputMapper and reconnect the controller. In a large share of cases the error simply disappears, because nothing else is competing for the device anymore. Our dedicated guide to the InputMapper and Steam Input conflict explains the Steam side of this in more detail.
Quick Check 2: Start InputMapper Before Your Launchers
Order matters. If Steam or a launcher starts with Windows and grabs the controller at sign-in, InputMapper will lose the race every time, no matter how often you reconnect the pad. Get into the habit of starting InputMapper first, confirming the controller connects without the exclusive mode warning, and only then opening your launcher and game.
After a reboot, test this order once before changing deeper settings: fresh boot, InputMapper first, controller second, launcher third. Many users find the error never returns once the order is fixed.
Step 3: Toggle Exclusive Mode and Reconnect
If the error persists, open InputMapper’s settings and find the exclusive mode option. Turn it off, save, disconnect the controller, and close InputMapper. Then reopen InputMapper, turn exclusive mode back on, and reconnect the controller. Toggling the setting forces InputMapper to release any half-finished claim from the previous session and start the handshake again from a clean state.
While you are there, confirm you are connecting a supported controller. InputMapper officially supports the DualShock 4, DualShock 4 V2, Xbox 360 and Xbox One controllers, the DualShock 3 and PlayStation Move Navigation controller via a Magic-NS dongle, and generic DirectInput and XInput devices. The DualSense and the Switch Pro Controller are not supported by InputMapper, and no setting will make exclusive mode work reliably with them. If you have a DualSense, you will need a different tool that supports it.
Step 4: Restart the Bluetooth HID Device
When the controller is connected over Bluetooth, the problem is sometimes a stale Bluetooth HID state rather than a competing app. Windows can hold on to an old pairing session in which the device was already opened by another service, and InputMapper then fails its exclusive claim against that leftover session.
Try this sequence. Turn the controller off and remove it from Windows Bluetooth settings. Restart the Bluetooth support service or toggle Bluetooth off and on. Then pair the controller again as a fresh device and start InputMapper before anything else. You can also test with a wired micro-USB connection: if exclusive mode works over USB but fails over Bluetooth, you have narrowed the problem to the Bluetooth path. Our Bluetooth pairing guide walks through clean pairing step by step.
Step 5: Run InputMapper as Administrator
Claiming a device exclusively requires more access than simply reading its inputs. If InputMapper is running with standard permissions while another service with higher privileges holds the controller, the claim can fail. Right-click the InputMapper shortcut and choose Run as administrator, then reconnect the controller and check whether the warning is gone.
If running as administrator fixes it, you can set the shortcut to always run with elevated privileges. Treat this as a diagnostic as much as a fix: it tells you the conflict was about access, not about a broken driver. If it makes no difference, move on rather than stacking more permission changes on top.
Step 6: Check for Legacy HidGuardian Leftovers
Older InputMapper setups relied on HidGuardian and HidCerberus to hide the physical controller. That stack dates from a 2016 to 2018 research project and has been archived for years. InputMapper 1.7-era installs even included a HidCerberus service. When parts of that legacy stack are left behind, half-installed, or configured for a device you no longer use, they can interfere with exclusive mode instead of helping it.
Do not install HidGuardian today to chase this error, and do not delete driver files at random. Check whether the legacy components are present, note their state, and read our comparison of HidGuardian vs HidHide before changing anything. The modern replacement does the same hiding job in a supported way, which leads to the most reliable long-term fix.
The Modern Route: Hide the Controller with HidHide
If exclusive mode keeps failing on Windows 10 or Windows 11, the durable solution is to stop relying on InputMapper’s own exclusive claim and hide the physical controller with HidHide instead. HidHide v1.5.230, released in May 2024 for Windows 10 and 11 on x64 systems, hides the physical controller from everything except the applications you whitelist. You whitelist InputMapper, cloak the DualShock 4, and games then only ever see the virtual Xbox controller that InputMapper creates.
This approach sidesteps the race entirely, because the hiding happens at the driver level before any launcher can grab the pad. Our full HidHide guide covers installation and the whitelist setup step by step. Once HidHide is configured, you can usually leave InputMapper’s exclusive mode setting as it is and simply enjoy a single, clean controller in every game.
What Not to Do
Search results for this error are full of random registry hacks and scripts that delete device keys. Avoid them. A registry value copied from a forum post can hide the wrong device or break Bluetooth for other hardware. There is no verified registry edit required to fix exclusive mode in InputMapper. Likewise, do not install driver packs from unofficial sites or download HidGuardian from third-party mirrors. Work through the steps above in order, change one thing at a time, and test after each change. If none help, browse our troubleshooting section before considering a full reinstall.
Frequently Asked Questions
Why does InputMapper say it failed to connect exclusively?
Another program usually opened the physical controller first, so InputMapper could not claim it exclusively. Steam, game launchers, other controller tools, and browser gamepad pages are the most common culprits. Close them, start InputMapper before your launchers, and reconnect the controller.
Can I ignore the exclusive mode error?
You can, but games may then see both the physical controller and the virtual Xbox controller at once, causing double inputs or the wrong device being selected. It is better to fix the cause or hide the physical controller with HidHide so only the virtual pad is visible.
Does exclusive mode work on Windows 11?
InputMapper runs on Windows 11, but it was never officially supported there because the final build dates from May 2020. Exclusive mode is less reliable on modern Windows, which is why hiding the controller with HidHide is the recommended long-term approach.
Should I install HidGuardian to fix exclusive mode?
No. HidGuardian is a legacy, archived project from 2016 to 2018 and should not be installed on modern Windows 10 or 11 systems. Use HidHide instead, which is the maintained successor for hiding the physical controller per application.