Just to let you know, your example runs on Creators Update right now, but will stall if anyone tries to call BluetoothLEDevice.FromBluetoothAddressAsync. This is due to a security bug in the Bluetooth APIs. See
https://social.msdn.microsoft.com/Forums/en-US/58da3fdb-a0e1-4161-8af3-778b6839f4e1/bluetooth-bluetoothledevicefromidasync-does-not-complete-on-10015063?forum=wdk#ef927009-676c-47bb-8201-8a80d2323a7f
for more info.
Creating an AppId in the registry for the executable name fixes it.
Just to let you know, your example runs on Creators Update right now, but will stall if anyone tries to call BluetoothLEDevice.FromBluetoothAddressAsync. This is due to a security bug in the Bluetooth APIs. See
https://social.msdn.microsoft.com/Forums/en-US/58da3fdb-a0e1-4161-8af3-778b6839f4e1/bluetooth-bluetoothledevicefromidasync-does-not-complete-on-10015063?forum=wdk#ef927009-676c-47bb-8201-8a80d2323a7f
for more info.
Creating an AppId in the registry for the executable name fixes it.