Fix InputMapper Failed to Connect Exclusively

Fix InputMapper Failed to Connect Exclusively Website .png
Spread the love
5/5 - (1 vote)

InputMapper – It has been reported that the Exclusive Mode of InputMapper no longer works on Windows 10 after installing the Fall Creators Update or Anniversary Update. It has been reported that the Run DS4 exclusively feature no longer switches into Exclusive Mode. On older versions of InputMapper, the entry will appear in the Settings menu as Use Exclusive Mode.

How to fix the InputMapper Failed to Connect Exclusively error

As per feedback from different users, the problem occurs because of a modification in the way Windows manages HID devices once they’re linked.

As a result of the Anniversary and Creators updates, a process was introduced that opened all HID devices available, interfering with InputMapper’s ability to open the device exclusively. Due to the fact that this conflict occurs within kernel32.dll, it cannot be resolved by the developer.

This article provides you with a few troubleshooting guides for configuring a PS4 controller to your PC using InputMapper. Below you will find a collection of solutions other Windows 10 users have used to solve similar problems.

There has been confirmation that each of the methods below works from at least one user, so feel free to use whichever method suits your particular situation.

InputMapper HidGuardian Method 1

Developers behind InputMapper released a new standalone tool that filters drivers involved in Exclusive Mode, making it easier to achieve Exclusive Mode on Windows 10.

You can download InputMapper HidGuardian from this link (here) to ensure Windows does not interfere with the DS4 exclusive feature.

Make sure the service is running (by opening every .bat file as administrator) before starting InputMapper and that it remains open until you click the Run Ds4 exclusively button.

The method 2 is to re-enable the Bluetooth HID device

There is a problem with InputMapper due to a change in how the Bluetooth HID device interacts with the Dual Shock 4 controller. The error can be resolved by turning off all the involved applications and re-enabling the Bluetooth HID Device.

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

    • Close any application you are using to connect a PS controller to your PC, such as InputMapper, DS4Windows, SCP, or DS4Tool.
    • Your PS controller should not be connected to your PC.
    • To open Device Manager, use the shortcut Windows key + R, type “devmgmt.msc” in the run box, and hit Enter.
    • Locate the Bluetooth HID Device in Device Manager (usually under Human Interface Devices).
    • If your controller is connected via a wire, it could also be referred to as an HID-compliant controller.
    • Using the Action menu from the ribbon at the top, select Scan for Hardware Changes once the device has been located and disabled.
    • Right-click the Bluetooth HID Device again and select Enabled.
    • Start the required applications to connect the PS4 controller to your PC.
    • InputMapper should now work correctly.

Using the Dualshock Exclusive Mode Tool will also make the whole process a lot easier. Please note that you might have to repeat this procedure every time you reconnect your Dual Shock 4 controller. In this free donationware program, the steps listed above will be performed automatically, saving you precious gaming time.

Using and configuring HidGuardian’s Exclusive Mode

Make sure that you are logged in as an administrator if you wish to configure HidGuardian’s Exclusive mode. The methods are different for wired and Bluetooth controllers.

Bluetooth/wireless controllers:
  • For all Bluetooth and wireless connections, follow these steps.
  • Type ‘devmgmt.msc’ in the dialogue box after pressing Windows + R.
  • Select Properties by right-clicking on the Bluetooth driver listed in the Device Manager.
  • Choose the option of Hardware IDs from the drop-down menu available under the Details tab.
  • Replace “BTHENUM” in the first ID with “HID” in Notepad
  • If the Hardware ID is “BTHENUM_148F&PID_5370”, change it to “HID_148F&PID_5370”
  • Type “regedit” in the dialogue box after pressing Windows + R again.
Navigate to the following key in the Registry Editor:
  • Paste the modified ID we just created in the Affected Devices option.
  • Wired controllers:
  • Go to the ID section of the Driver in the device manager, as we did in the earlier solution.
  • Rather than copying only the first ID, copy the first three IDs to Notepad. We won’t change the IDs.
  • Paste all three IDs into the same registry entry as before.


Leave a Reply

Your email address will not be published. Required fields are marked *