GUI can't find Ganglion BLE on Windows 10 [obsolete]
Hello, I have a Windows 10 laptop with Bluetooth LE. Attached is a picture from Bluetooth parameters demonstrating the Bluetooth LE Enumerator. I can power up the Ganglion (blue LED D2 is blinking) but the computer does not find it. Could I please ask for your help? Thank you in advance.

Comments
The tutorial mentions the requirement of using a Bluetooth Low Energy (BLE, or Bluetooth 4.0) dongle from CSR (CSR 4.0). This is because Windows hardware is so variable, the built in BLE interface often does not meet the requirements of Ganglion communications.
http://docs.openbci.com/Tutorials/02-Ganglion_Getting Started_Guide#ganglion-getting-started-guide-downloadrun-the-openbci-gui-on-windows
Please follow the instructions there after you have obtained a CSR 4.0 dongle.
Regards,
William
(High-speed USB) and USB 3.0 (SuperSpeed USB). USB 2.0 ports on Acer
computers have a black tongue in the port, while USB 3.0 ports have a blue
tongue. For best performance, USB 3.0 devices should always be plugged
into USB 3.0 ports. Consult your device’s documentation to see which
standard it supports."
recommended to plug in the power
adapter".
I shall post again when I have the procedure refined, hopefully on Windows7 also.
Attempting to disable the CSR8510 while the hub is active upsets the PC and then it thinks it needs a reboot to install new hardware.
I hope this helps someone.
I am getting a code 412 error after reformatting my machine. I know the board/dongle work properly because I collected data few months ago (before reformatting) and when I boot into Ubuntu and use hcitool lescan it shows the ganglion. Currently I'm using the CSR8510 A10 but reading the comments above, it seems that I should be using a bled112. Is this accurate? I'm happy to purchase one if that's the case. I'm not sure what else to try, I've gone through everything on this discussion twice now and even more generic problem solving but I still always get this code on both the latest version of the GUI (both with the binary and via processing) and the September 2017 release which I was previously using.