UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36

Steps to reproduce the problem:
I am trying out the experimental Web Bluetooth services on Chrome 66. First: the code works fine with the Windows Web Bluetooth polyfill, and on Mac OS, Android, and Chromebooks.

On Windows, it takes over several minutes to detect my BT devices (see below), regardless whether they are already paired with Windows or not. After selecting a device, BluetoothRemoteGATTServer.connect() never resolves.

What is the expected behavior?
The connect() call should resolve quickly.

What went wrong?
OS: Windows 1709 build 16299.192 (x64)
Chrome: 66.0.3359.139
Devices: Manufactured by www.tts-group.co.uk: Blue-Bot and InO-Bot. Both come with a Microchip Technology BM77 chip for BT connectivity (full spec is BM77SPP03MC2).

More info: I also tried a helper app that I wrote that uses the BT SPP interface available for Chrome apps. Often, the connect fails with an error message about trying to connect over an unreachable network.

Even more info: Removing and re-discoveringthe device in the Windows settings app helps. This is also true for Macs.

Even more info (unrelated): With Chrome 66, the helper app caused 2 bluescreens within the hour when trying to use the BT SPP connectivity. Seems that Chrome apps really are on the way out :)

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 66.0.3359.139  Channel: stable
OS Version: 10.0
Flash Version: