Windows 10: Dualsense Wireless Controller not recognised

I recently bought a dualsense wireless controller and when i go to device manager it appears in bluetooth but its not in Sound, Video and game controllers how do i fix this problem?

:)

 

DualSense Wireless Controller

Problem solved

Steps I did to solve:

1. Use a cable to connect the controller to your device.

2. Go to Controller website to download the latest hardware for DualSense™ Wireless Controller and DualSense Edge™ Wireless Controller. And follow the step of it to update hardware.

3. Go to Sound Control Panel and find the speaker of the controller (heard that PS5 controller use sound to control vibration), right-click controller's speaker and press configure speaker. Make it Quadraphonic and go next, tick all two box and go next, press Finish.

Then I open my game again and it works perfectly.

 

DualSense Wireless Controller

Hi,

While connecting my PS5 controller to my pc (windows 10) it connects and sthe device shown as ' wireless controller' but the device shown as ' dualsense wireless controller' on my phone. And when connecting to pc, some feature of the controller such as vibration does not work. I wonder if there is a way to fix it.

I have tried to restart the controller, trouble shooting the bluetooth, cable connecting and it all not working.

Does windows 10 not support the dualsense wireless controller, do i need to get windows 11 to use the full function dualsense controller

Thank you

 

Dualsense controller not working over Bluetooth

Hello Martin.



Thank you for your suggestions.



I deleted all devices that are named Dualsense or Wireless controller from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Devices



Restarted a PC. But it is still there in the list.



BUT



After resetting the controller tried to add a bluetooth device again and now it showed up in the list so I paired it successfully, finally.

Maybe it resets Bluetooth MAC as well.. Maybe registry edits erased MAC from the memory and it now can be recognised as a new device, didn't test it enough. Either way one of that was a working fix.



Thank you!