Closed Kanuan closed 2 years ago
Besides the amazon one Nef linked above, this DUALSHOCH
controller from... Wantech Electronics? I think, seems to also use unsecured connections via BT, meaning it also is unsupported by Windows/BthPS3
Closed so it disappears from the open issues list but keeping it pinned.
Keep in mind: this is a really specific, rare issue and chances are that if your controller is not connecting by Bluetooth it's probably for another reason. If the issue described here ends up not being your case, have a look in our Bluetooth connection troubleshooting section.
The issue
Most fake DS3 controllers work fine over Bluetooth... Most. Some reeeally rare copy-cats controllers don't use encrypted connections on bluetooth. Because Windows sees this as a security hazard it immediately drops the device when it tries to connect. This is something that DsHidMini and BthPS3 can't fix, the only option is to use the controller wired.
Known controllers with this issue
DS3 copy-cat identified as Pro Controller. We have discovered that there are other controllers with different appearances/shells that suffer from the same issue.
How to check
Before trying this, follow the How to Install article's Troubleshooting section to be 100% sure DsHidMini is correctly installed, BthPS3 is working, the controller is correctly paired to the current Bluetooth Host address and everything indicates the controller should be connecting, then:
Adding the
Pro Controller
to the list of supported devices on BthPS3 listWin + R
to open the WindowsRun
toolRun
Tool, typeregedit
and then pressOK
. Windows' registry editor should openHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BthPS3\Parameters
SIXAXISSupportedNames
entryPro Controller
to the list (best if you copy and paste the name there, it needs to be a exact match)Checking Windows Event Viewer
Win + X
and then open theEvent viewer
on the appearing menuBTHUSB
source entry:Windows rejected a device connection because the device didn't establish encryption prior to the service level connection
, as shown in the image below:Results
Working around the issue (TL,DR: You can't)
The only way is fully replacing the whole Windows' Bluetooth Stack with another KMDF bluetooth stack that checks and accepts in-coming, unsecure DS3 connections. This driver does not exist and probably never will since it's a enormous amount of work for little to no benefit (how many people have this Pro Controller DS3 copy-cat?).