I found myself in a situation in which the Windows implementation of Zwift become unresponsive while at the pairing screen. After playing around with it for a while, it appears to have something to do with the Beta Bluetooth Functionality while also having an Ant+ stick in a USB port.
I am able to reproduce the issue with the following steps:
- Insert an Ant+ stick into a USB port.
- Launch Zwift.
- Enable Beta Bluetooth Functionality.
- Exit and Relaunch Zwift.
- Immediately regret previous decisions. The app is now unresponsive.
- Unplug the Ant+ stick.
- Everything is now fine.
Note that the UI is (mostly) unresponsive. It will update once every 20 or 30 seconds, so it can take a while to respond to mouse clicks. My guess is it’s hanging while performing device discovery. If so, perhaps you should consider moving device discovery to it’s own thread instead of blocking the user interface thread (because an unresponsive UI is super annoying). The process is not CPU bound, only consuming about 10% CPU.
All software is up-to-date as of today (June 6, 2019): Zwift, Windows 10, Bluetooth Drivers. Also, the system is more than capable of running Zwift: 6 Core Intel Coffee Lake CPU, NVidia 1080ti GPU, NVME SSD primary storage.