Still Bluetooth Problems in Windows Creators Update - GattService.GetCharacteristicsForUuidAsync() returns 0 elements after reboot RRS feed

  • Question

  • Hi,

    as stated here:

    there have been several problems with bluetooth since the Windows Creators Update. Meanwhile registering an AppID helped to make our products work again.

    Then another update broke functionality again which was fixed in KB4032188 as far as I know.

    Now I face another issue with the Windows BLE-Stack:

    - After pairing a device (manual with PIN) we can use our software as expected until we reboot the PC. After rebooting the PC GattService.GetCharacteristicsForUuidAsync() returns 0 elements.

    - Calling GattService.GetAllCharacteristics() instead throws an System.UnautorisedAccessException (HRESULT: 0x80070005 (E_ACCESSDENIED))

    - After disconnecting the BLE device and do the pairing again all works fine again. Rebooting brings up the same problem over and over.

    This does happen to two different Laptops running Win10 (15063.0.amd64fre.rs2_release.170317-1834). Both are up-to-date (latest update KB4034674 - 09.08.2017) while a 3rd one runs normal without problems. We use WinRT APIs from desktop application.

    Our Setup: As BLE-Central we use a Asus BT400 USB donlge. Internal Bluetooth devices of the laptops are disabled. Periperal is a CC2541 based device.

    Not sure but it seems there are some pairing related problems in the last build (windows forgetting the key while rebooting?)

    Any help on this?



    • Edited by f_pabst Monday, August 14, 2017 12:51 PM PIN
    Monday, August 14, 2017 10:24 AM

All replies

  • Hi Frederik,
    Thanks for reaching out to us. It would greatly help our investigation if you could collect and send Bluetooth traces to us. Please start collecting trace when switching radio off to radio on and reproducing the issue.
    To submit a Feedback Hub report to reproduce the issue and submit Bluetooth logs, please follow these steps:
    1.      Search for “Feedback Hub” in Cortana search, then launch the app.
    2.      Navigate to Feedback in the left menu, then press + Add new feedback.
    3.      Select the Problem button, share any details you think are relevant, and choose an appropriate category and subcategory. (For proper Bluetooth logs to be captured it must be one of the Bluetooth context paths, e.g. Hardware, Devices, and Drivers -> Bluetooth – Discovery, Pairing, and Connectivity)
    4.      Important: If possible, reproduce the problem(s) after clicking Begin monitoring (or Start capture) near the end of the form; Stop monitoring when you’re done.
    5.      Once you’ve completed the form and monitoring, click Submit.
    6.      Click Continue using Feedback Hub.
    7.      Click My feedback at the top, then find the item you submitted (it may take a while to appear).
    8.      Open the item you submitted, then click Share.
    9.      Click Copy link, then paste the link here in your response.  (It will look like<unique link>.)
    Monday, August 14, 2017 4:33 PM
  • Hi Aruna,

    performed the steps:

    Hope it helps figuring it out.


    Tuesday, August 15, 2017 11:50 AM
  • Thanks for the traces, Frederik.
    Our team will investigate this issue and I shall keep you posted on the status. Please feel free to reach out if you have any other questions.

    Tuesday, August 15, 2017 5:06 PM
  • Hi,

    one month has passed - any news here?


    Tuesday, September 19, 2017 8:05 AM