This is a classic bug with hidhide not configured properly Ħ in applications tab you should have hidhidecliend.exe and DS4windows.exeħ in devices tab put a lock on sony interactive entertainment BUT sony COMPUTER is fine or xbox 360. I just tested and it doesn't seem to work for me with DS4Windows enabled to map to xbox 360 the second one disconnects So that's how it worked for me hope it works for you too, and also if you can just copy paste my answer on the threads above in order to help more people as i don't have accounts on those websites. I suspected the issue to be the intel card not recognizing the controllers being individual and independent so what i did was going to control pannel then device and printers (it may not be the same name, i'm sry i don't have my pc at hand) then you select the wireless controlers ( you should have one at least) and you go the window bluetooth there you should be able to double click on Wireless Controller and change its name to whatever you want (it is a way to show the card that you're not trying to connect the same controller again and again) once you change that you click on apply and you can try to reconnect your other controller / it may be the same procedure for many controllers you only have to renamme more i guess. Hey guys, i may have found a solution to our problem. 01:19:00: Associate X360 Controller in slot #1 for input DualSense controller #1 01:19:00: Plugging in virtual X360 Controller 01:18:14: Controller 2 was removed or lost connection 01:18:14: Unplugging virtual X360 Controller 01:18:14: Disassociate X360 Controller from slot #2 for input DualSense controller #2 01:02:49: Controller 1 was removed or lost connection

01:02:49: Unplugging virtual X360 Controller 01:02:49: Disassociate X360 Controller from slot #1 for input DS4 v.2 controller #1 01:02:49: Gamepad data write connection is lost. 01:02:46: Controller 2 is using Profile 'Default'. 01:02:46: Associate X360 Controller in slot #2 for input DualSense controller #2 01:02:46: Plugging in virtual X360 Controller 00:47:16: Controller 1 is using Profile 'Default'. 00:47:16: Associate X360 Controller in slot #1 for input DS4 v.2 controller #1 00:47:16: Plugging in virtual X360 Controller Read the DualSenseWindows.00:47:16: The gamepad DS4 v.2 (BT) uses custom feature set (MonitorAudio).Download the DualSenseWindows_VX.X.zip file from the latest release found at the Release Page.Consider checking out our Road-map for further information.

The library is still in active development and will be extended with additional features soon.

Setting the player indication LEDs and the microphone LED.

Controlling the RGB color of the lightbar.

Controlling the adaptive triggers (3 Types of effects) and reading back the users force while active.

Using the haptic feedback for default rumbleing.

Reading the Accelerometer and Gyroscope.

Reading the analog sticks and analog triggers.

Reading all button input from the controller.

The library may not work as intended! Features ❗ Warning: The current release state is still a preview release. This API will help you using the DualSense controller in your windows C++ Applications / Projects. Windows API for the PS5 DualSense controller.

Ds4windows github