none
Unable to connect some Bluetooth devices

    Question

  • I am currently in the process of deploying 30 new Win10 Toughbooks that all have to be able to pair with 10 portable LifePak defibrillators. Unfortunately, Win10 never pops the prompt for the PIN. LifePak support informed me that a lot of Bluetooth vendors are having this kind of trouble with Win10. My Samsung S4 pairs without any problem. LifePak's response has been to write an application that helps the device pair, but it has to be run as an admin, and would need to be run for all 10 devices on all 30 PCs.

    Has anybody else come across similar trouble pairing certain Bluetooth devices to Win10? I'm just about ready to give up on Win10 for these systems and downgrade to Win7, but I'd really like to stick with 10 if possible. Given that all of the LifePaks use the same pairing PIN, is there any possible way of ex/importing the pairings? If not, would it carry over if I do all of the pairings on my reference system and make a new image? I've tried ex/importing the keys in HKLM\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Keys to no avail. I'm on the latest 1607 build. I'm updating to Creators Build now to see if there's a fix there, but I don't have a lot of hope.

    Any ideas?

    Thanks in advance!

    Jon

    Thursday, April 13, 2017 1:43 PM

All replies

  • Win10 never pops the prompt for the PIN.

    Have you tried connecting without a PIN?  FWIW I think I may have a similar problem with the Screen Connection feature (Wi-Fi) Projecting to this PC.  There, the only case that has worked for me is  PIN off.  Fortunately it at least prompts with the name of the device.

    Otherwise, I would try some tracing but I don't really know which ones would be relevant

    PS>netsh trace show providers | select-string -pattern "BTH|Blue"
    
    {4B6EFB94-30EA-49A7-BB29-E9ED9DCE67DA}  WPD Bluetooth MTP Emumerator Driver Trace
    {04268430-D489-424D-B914-0CFF741D6684}  Microsoft-Windows-Bluetooth-MTPEnum
    {0602ECEF-6381-4BC0-AEDA-EB9BB919B276}  Microsoft-Windows-Bluetooth-Policy
    {33693E1D-246A-471B-83BE-3E75F47A832D}  Microsoft-Windows-BTH-BTHUSB
    {4AF188AC-E9C4-4C11-B07B-1FABC07DFEB2}  Microsoft-Windows-Bluetooth-BthLEPrepairing
    {53F6879F-9E16-4D1D-99B0-A6A67AB4AA40}  Microsoft-Windows-Bluetooth-HidBthLE
    {8A1F9517-3A8C-4A9E-A018-4F17A200F277}  Microsoft-Windows-BTH-BTHPORT
    {EB492407-201E-4281-8531-CDFB141CA69F}  Microsoft-Windows-Bluetooth-BthLEEnum
    

    Since you have a case where it is working you could have two traces for comparison without having to know exactly what either one was saying.

    Also, without access to the source or support documentation, I would probably be running ProcMon concurrently to try to supplement any such diagnostics that you are already aware of.  Doing that would at least help explain how each could be related (e.g. when filtering with Operation Is WriteFile and inferring which external record would have been written by each event.)

     

    Good luck



    Robert Aldwinckle
    ---

    Thursday, April 13, 2017 7:44 PM