Fix: InputMapper Failed to Connect Exclusively

A lot of users have reported that the Exclusive Mode of InputMapper no longer works on Windows 10 after the Windows 10 Fall Creators Update or Anniversary Update is applied. As per various user reports, the Run DS4 exclusively feature no longer makes the switch to Exclusive Mode. On older InputMapper versions, the entry will appear as Use Exclusive Mode inside the Settings menu.

What Causes the InputMapper Failed to Connect Exclusively  error

After investigating the issue and looking at various user reports, it’s clear that the issue occurs due to a change in how Windows deals with HID devices once they are connected.

Both the Anniversary and the Creators updates introduced a process that opens every HID device available, thus getting in the way of InputMapper’s ability to open the device exclusively. This conflict is impossible to solve by the developer since it takes place within kernel32.dll.

How to Fix the InputMapper Failed to Connect Exclusively Error

If you’re struggling to configure a PS4 controller to your PC via InputMapper, this article will provide you with a few troubleshooting guides. Below you have a collection of methods that other Windows 10 users in a similar situation have used to get the issue resolved.

All of the methods featured below are confirmed to work by at least one user, so feel free to use whichever method is more convenient to your particular scenario. Let’s begin!

Method 1: Using InputMapper HidGuardian

The developer behind InputMapper released a new standalone tool that launches a service capable of filtering those involved drivers, making it easier to achieve Exclusive Mode on Windows 10.

This little tool is designed to be used with the parent application InputMapper. It essentially ensures that Windows doesn’t interfere with the DS4 exclusive feature. You can download InputMapper HidGuardian from this link (here).

To use it, run the service (by opening every .bat file as administrator) before starting InputMapper and make sure it remains open until you click the Run Ds4 exclusively button.

Method 2: Re-Enabling the Bluetooth HID Device

Some users have discovered that InputMapper is malfunctioning due to a change in the way that the Bluetooth HID device interacts with the associated Dual Shock 4 controller. As it turns out, re-enabling the Bluetooth HID Device while all the involved applications are turned off will fix resolve this error.

Here’s a quick guide on how to do this:

1. Make sure that every application that you might be using to connect a PS controller to your PC is closed. This includes InputMapper, DS4Windows, SCP or the DS4Tool.
2. Make sure that your PS controller is not connected to your PC.
3. Press Windows key + R to open up a Run box. Next, type “devmgmt.msc” and press Enter to open up Device Manager.
4. Inside Device Manager, look for Bluetooth HID Device (usually located inside Human Interface Devices drop-down menu).
   Note: The device might also be named HID-Compliant game controller if you’re using a wired controller.
5. Once the device is located, right-click on it and choose Disable. With the service-disabled, use the Action menu from the ribbon at the top to click on Scan for Hardware changes.

   

6. After the list is refreshed, right-click on the Bluetooth HID Device again and choose Enabled.
7. Launch the required applications to connect the PS4 controller to your PC. InputMapper should function properly now.

Keep in mind that you might have to repeat this procedure every time you reconnect your Dual Shock 4 controller. You can also make the whole process a lot easier by using the Dualshock Exclusive Mode Tool. This free donationware program will do the steps enumerated above automatically saving you precious gaming time.

Method 3: Using and Configuring HidGuardian’s Exclusive Mode

Another method that we can use is to configure HidGuardian’s Exclusive mode. The methods are different for wired and Bluetooth controllers. Make sure that you are logged in as an administrator. You can always revert the changes later on.

For Bluetooth/Wireless Controllers:

Follow these steps for all types of Bluetooth and Wireless connections.

1. Press Windows + R, type ‘devmgmt.msc‘ in the dialogue box, and press Enter.

   

2. Now locate the Bluetooth driver from the Device Manager, right-click on it, and select Properties.
3. Select Details section from the tabs and select Hardware IDs from the drop-down present.

   

4. Copy the first ID to a Notepad and replace “BTHENUM” in the ID with “HID”
   (For example, if the Hardware ID is “BTHENUM_148F&PID_5370” Change it to “HID_148F&PID_5370”)
5. Press Windows + R again, type “regedit” in the dialogue box, and press Enter.
6. Once in the Registry Editor, navigate to the following key:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidGuardian\Parameters

7. Double-click on the Affected Devices option and paste the modified ID we just created there.

For Wired Controllers:

1. Navigate to the device manager as we did in the earlier solution and go to the ID section of the Driver.
2. Now instead of copying the first ID only, copy the first three IDs to Notepad. We will not change the IDs in this case.
3. Navigate to the same registry entry as of previously and paste all the three IDs to the Affected Devices.