Hi guys,
I have a solution here, but this demands patience.

The problem is from Microsoft and basically from the BLE patch they introduced by fixing the CVE-2019-2102 vulnerability in 1903. The same vulnerability used to impact PSMoveService as well, but reportedly was patched by the developer somehow. Against all odds, I did not manage to also pair 2 PS3 Move controllers to a 2004 Windows 10 (although reportedly fixed).

Coming back to the GearVR controllers, the message you will get in the System Event log would be: “The device (device MAC) is trying to distribute an Identity Resolving Key that is already used by a paired device. The pairing was rejected, if the intent was to pair with this device, you may need to first delete the existing pairing information.” Perhaps Greg cannot solve it unless writing a BLE stack patch or to deactivate .

Basically, what I have done to have 2 Gear VR controllers in Win10 2004 is install 1809, pair all devices, then upgrade to 2004. I know, it sucks, but it works. Of course, when accidentally one of them is unpaired, I will have to reinstall everything. Once again, this happens only during pairing. It was a dick move by MS, but it is as it is.

Same applies to almost any BLE device pair like cheap VRBoxes. What I will be experimenting these days is for example GearVR + Daydream controller. But I think safest is to just go to PS Move controllers, if they are the same price.

IMHO the 6DOF hand tracking of GearVR + Kinect360 is horrible, especially when you have games where wrist moves are important (swords or boxing like Creed). I think PS Move controllers are better.

I was able to pair two GearVR controllers using Windows 10 build 2004 and got them working perfectly in Driver4VR without having to reinstall windows or somehow downgrade to 1809 (is that even possible?).

I too was frustrated that I could not use a second GearVR controller due to them both using the same Identity Resolving Key (thanks Samsung), but also knew that if you had previously paired them prior to updating to Windows 10 1903 that you were able to continue using them so there must be a way to get the latest build of Windows 10 to allow both to be paired.

The solution is to temporarily change the IKN for one controller so that Windows 10 fails to see the conflict and allow the second controller to be paired, you can then change the first controller’s IKN back and still operate both controllers independently.

I am happy to provide a detailed set of instructions, but I would like to check with Greg first if posting instructions involving modifying the registry is permitted on the forum. If those instructions are not welcome, the above paragraph should give anyone with a reasonable knowledge of the registry enough information to figure it out for themselves.

See the attached screenshot showing the two controllers in Driver4VR.

Rucio

I’m thinking to get gear vr controllers, so if you could also PM me how to do it, I would be very thankful.

Hi,
I’m also attempting to do dual gear VR controllers on windows 10 and am running into all the problems mentioned above etc.
I also would appreciate it if you could send those instructions on the IKN changing method. I got most the way there and found the devices but I don’t know specifically what ID to change.
Earlier I somehow got the second controller paired via another method but it’s not functional. Basically it isn’t recognized as the same kind of device that the original gear VR controller is and it’s kind of stuck in limbo. I can’t even remove it from my bluetooth settings anymore, if I try it says “Removal Failed”. I may need to remove it to sync the second one properly though so if anyone has insights on that I would be thankful.
Thanks in advance,

Okay I figured out how I had both paired but 1 not working at a time. Basically I had multiple Bluetooth receivers and I tried switching to another one, then pairing to the controller. Unfortunately it cause Issues with it not actually being paired and making the device unremovable when using the wrong Bluetooth receiver. So this method is a no go.

I ended up buying an Asus bt-500 for the pairing process and it made it much easier compared to my Bluetooth 4.0 UGreen receiver. It was $20 at best buy so I would recommend if anyone is having difficulties with the PAIRING OF ONE CONTROLLER.

I’m still having trouble trying to pair 2 Gear VR controllers and currently don’t have any other good options. I’m mostly there to finding the IRK (Identity Resolving Key or is it the IKN?) in regedit, I just need to know where the key specifically is. I would really appreciate having the instructions on changing the IRK (Identity Resolving Key or is it IKN?) in windows registry if anyone knows it?

Just private message us brother, we can do it on our own.

I don’t know about this forum but my discord contact username is alphachicken22#1515 .
The profile pic is the one with a golden “A” symbol on a white background.

Hey I’m trying to do this as well but can’t find the lkn… Please help!! Would be most greatly appreciated.

I was confused by Rucio’s reference to “IKN”, but here is how I got both controllers to work in 1909. I’m assuming he meant “IRK”. Heads up, this will mess with your computer’s registry and has the potential to break windows if done incorrectly. No one except yourself is responsible for anything that may go wrong.

* Connect one of the Gear VR controllers to Windows via the Bluetooth menu. Make a note of what the device name is, specifically the 4 letters and numbers inside the parenthesis. This should work without error.

* Regedit.exe as Administrator, navigate to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Keys. On the left, there will be a subkey (folder) under “Keys”, the name of this folder will be specific to each computer. Expand that folder with the downwards arrow. Now you should see a folder with the last 4 characters in the name matching the 4 characters in the Bluetooth menu. Open this folder.

* There is a entry with the name “IRK”. Click that and you’ll see the the attached screen. Replace the 01 at the start of each line with 02.

* Close out of Regedit and restart your computer.

You should now be able to pair the second controller without issues. You don’t need to worry about changing that value back, but you may need to remove both devices and repeat this process if you ever need to repair the controller.
See below for verification.

• This reply was modified 3 years, 2 months ago by danlopez1222.

Are you seeing the battery icon next to both controllers in the Bluetooth settings? When you open Driver4VR, and preview the device under tracker manager, they should go from “paired” to “connected”.

Off

Try explaining how you figured it out, it might help someone stuck in the same position as you.

I have some problem
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Keys