none
Fall Creators Update caues Bluetooth to stop working?

    Question

  • My notebook computer just installed the Fall Creators update and after the update installed my Bluetooth now doesn't work. Device manager shows this error "Windows has stopped this device because it has reported problems Code 43". Of the two suggestions I found online, the first was to uninstall and then choose "Scan for hardware changes" and allow the device to be reinstalled - this didn't work; the second is "get a newer driver".

    The driver currently installed is a genuine Atheros driver dated 5/18/2016, that's not that old and I don't think I need to tell anyone here that the biggest scams on the internet can be found on "driver update" websites so I trust nothing unless it's from the manufacturers website. But Qualcomm does not offer end user driver updates and the manufacturer does not have any newer drivers available.

    Anyone have any idea's on how to get this to work?
    Wednesday, January 03, 2018 12:19 AM

All replies

  • Open Settings > Update & Security > Troubleshoot > Bluetooth > Run the troubleshooter.

    Uninstall and reinstall the device via Device Manager. You should download and install the bluetooth driver either from the support site of the manufacturer or via windows update.

    Never download from any other third party driver support site.


    S.Sengupta,Microsoft MVP Windows and Devices for IT, Windows Insider MVP

    • Marked as answer by OldTimer1701 Wednesday, January 03, 2018 11:16 PM
    • Unmarked as answer by OldTimer1701 Monday, January 08, 2018 6:03 PM
    Wednesday, January 03, 2018 12:31 AM
  • Hi,

    When you get this error with USB devices it’s because one of the drivers controlling the device notified the operating system that the device failed in some manner. This can be because of corruption in one of the loaded drivers and the driver cache just needs to be flushed. Unplugging the computer sometimes doesn’t resolve the problem because the battery still holds power. To fix this, unplug all of your USB devices, then turn off the PC and take out the battery (This is assuming that you’re on a laptop), let the PC set for about 5 minutes, then put the battery back in and restart the PC. Next, plug your USB devices back in one at a time and make sure that they work.

    If this does not work or you’re on a desktop, follow the steps in this KB article

    Error: “USB Device not recognized” when you try to access a USB external hard drive.

    https://support.microsoft.com/en-gb/help/2654149/error-usb-device-not-recognized-when-you-try-to-access-a-usb-external

    Best Regards,

    Tao


    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, January 03, 2018 4:22 AM
    Moderator
  • The troubleshooter fixed the problem.
    Wednesday, January 03, 2018 11:16 PM
  • Actually, I spoke too soon. The troubleshooter gets the Bluetooth working again, but once I shutdown and restart the Bluetooth is again not working and I'm now having to run the troubleshooter each time I boot up in order to get the Bluetooth working.

    Any idea's how to permanently fix this problem?

    Monday, January 08, 2018 6:04 PM
  • I also have this issue, i have noticed it today but i think it started 3 days ago when i did the update, as my fitbit stopped syncing to the app on my computer. I tried speaking to Microsoft on their chat function about it, but they have failed to solve the issue. I have tried updating, but it was already up to date; uninstall reinstall, however that didnt work; repeatedly doing the above, also didnt work. Seems like something in the update must have really messed up the system.
    Monday, January 08, 2018 9:16 PM
  • LaCaKe:

    You can try the Bluetooth troubleshooter: Update & Security / on the left click Troubleshoot then from the list select Bluetooth.

    As I just posted this works for me but only for my current session, as soon as I shutdown and restart my Bluetooth is back to a non-working state and I have to run the troubleshooter again every time I turn the computer on.

    Very frustrating.

    Monday, January 08, 2018 10:32 PM
  • Hi,

    We haven’t heard from you for a couple of days, have you solved the problem?  

    Best Regards,

    Tao


    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, January 10, 2018 5:57 AM
    Moderator
  • Tao:

    As I posted on Monday January 8th, the issue is NOT resolved.

    While the Bluetooth troubleshooter "Reinstall's the Bluetooth Module" and seems to work for a while (see next paragraph) after shutdown and restart the Bluetooth is back to not working again and I have to run the troubleshooter every boot up in order to use the Bluetooth.

    Also if the Bluetooth is working after running the troubleshooter and I leave the notebook sitting for a couple hours the Bluetooth again stops working however when I run the troubleshooter this time is claims to fix a problem with the Bluetooth Radio and then the Bluetooth works again. First when plugged in the computer is set to never suspend or hibernate and all advanced power settings are set to not shut down any hardware while plugged in and these problems happen when plugged in as I rarely use the notebook on battery.

    Any suggestions on how to permanently fix this problem? Also it seems like other people are also reporting Bluetooth issues after installing the Fall Creators Update?

    Wednesday, January 10, 2018 5:59 PM
  • Tony:

    Still waiting for some help here?

    Also I've also noticed a number of times after running the troubleshooter and getting Bluetooth to work that is will suddenly stop working and when I run the troubleshooter again that it reports that it "Fixed the Bluetooth radio".

    I'm seeing lots of reports of Bluetooth problems after the Fall Creators Update but no solutions, what's being done to fix this since it's clearly a Windows problem?

    Tuesday, January 16, 2018 6:05 PM