Fake/Copy-cat DS3 controller doesn't connect over Bluetooth

[Kanuan]

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 list

• Press Win + R to open the Windows Run tool
• On the Run Tool, type regedit and then press OK. Windows' registry editor should open
• Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BthPS3\Parameters
• On the right side, modify the SIXAXISSupportedNames entry
• Add the name Pro Controller to the list (best if you copy and paste the name there, it needs to be a exact match)
• Confirm the change and then close Windows Registry

Checking Windows Event Viewer

• Try connecting your controller wirelessly
• Press Win + X and then open the Event viewer on the appearing menu
• Expand the "Warning" section and then double click on the BTHUSB source entry:
  
• Check if there is a recent (look at the time) "warning" entry that has the same General description, 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

• If a warning with the same description exists then you are out of luck
• If the warning does not appear on Windows' event log then your controller is probably failing to connect for another reason and requires a BthPS3 tracing to determine exactly why. Reach us through the proper means so we can give you a hand

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?).

[nefarius]

Related important read.

[Kanuan]

Known unsupported controllers

PS III Double Shock Wireless Controller

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