Qualcomm Atheros AR3012 Bluetooth not working in Windows 10

Anonymous
2016-07-18T04:46:58+00:00

Qualcomm Athereos AR3012 Bluetooth disabled by Windows 10  need driver or replacement hardware to look for

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2020-06-19T20:24:49+00:00

Here is how I made the AR3012 working again on Windows 10 20H1.

  1. remove AR3012 & its drivers completely from 20H1, later let 20H1 detect it as Generic Bluetooth Radio.
  2. download Qualcomm driver v10.0.1.15 from Microsoft Catalog website, install this driver via driver upgrade.
  3. after v10.0.1.15 being installed, you might see additional device named in "Bluetooth LE" as the one in the Kirill's figure.
  4. try to connect any BT device you couldn't connect after upgrading to 20H1, make sure the AR3012 really WORKS.
  5. then download any Qualcomm driver v10.0.3.x (as Kirill mentioned, the newest one is v10.0.3.22, or let Windows Update do it later), upgrade  the driver of AR3012 again with this one.

Notice: NEVER uninstall the v10.0.1.15 while/after upgrading to v10.0.3.x, or the AR3012 will fail again after reboot.

Microsoft Generic Bluetooth Driver -> Qualcomm BT driver v10.0.1.15 -> Qualcomm BT driver v10.0.3.x,

if you did followed the steps, your AR3012 should be working as usual, even after reboot. 

Qualcomm Atheros Communications - Bluetooth - 10.0.1.15 (x64)

Qualcomm Atheros Communications - Bluetooth - 10.0.3.22 (x64)

I guess the "Bluetooth LE" is the critical point of this issue.

(I DID hate the crappy W10...... what's M$ doing now? let users recall how windows unstable in 1990s? )

NOTE by MELERIX: by the way, as it is an older driver, it does not support the new Windows 10 shutdown mode called fast startup*, so every time you shut down Windows and then restart it, the device appears with an error, so you have to* disable the fast startup of Windows 10*, in the power options of the control panel.*

Was this answer helpful?

200+ people found this answer helpful.
0 comments No comments

206 additional answers

Sort by: Most helpful
  1. Anonymous
    2019-10-29T06:06:59+00:00

    Yesterday I moved from Windows 10 1903 to Windows 10 1909 by deleting everything on the hard drive. My Bluetooth headset, which was working properly before the format process, was no longer detected. I tried connecting again after making sure I had installed all the drivers and made all the Windows updates, but the result didn't change.

    I have erased and reinstalled the drivers for my wireless adapter from the device manager maybe 50 times, and finally managed to connect to my headset. After using it for 5-6 hours, I turned off the computer, and when I turned it back on, it didn't detect my headset. In the same way, I erased the driver and reinstalled it repeatedly, but this time it did not work. These are the solutions I've tried:

    1. I ran the "sfc / scannow" command. I did 100% scan and couldn't find anything.
    2. I uninstalled and reinstalled all drivers, including the audio driver.
    3. I updated all drivers with IOBIT Driver Booster.
    4. I installed the drivers that I downloaded from the official site of my computer.
    5. I shut down and restart all of the Bluetooth-related services from the "Services" section of Windows.

    None of the above solve my problem.

    My Bluetooth adapter: Qualcomm Atheros AR3012 Bluetooth 4.0,

    My Bluetooth headset: Xiaomi Airdots Earbuds TWS Bluetooth 5.0 Headset (works on my phone. So there's nothing wrong with the headset)

    I know that Wi-Fi and Bluetooth work on the same adapter. Wi-Fi is working fine. I've been trying to solve this problem for two days. Please help me.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-10-25T13:06:25+00:00

    Windows 10 1903 (updated to KB4517389) caused Bluetooth to fail on my Samsung laptop with Qualcomm Atheros AR3012 Bluetooth hardware.  No Bluetooth communication takes place, including detection of devices and connection to devices that were already paired before Windows 1903.  Bluetooth drivers were all the latest available, and Device Manager reports that Bluetooth hardware is working normally.

    Workaround: obtain old Atheros drivers from a web site.  Install driver level 10.0.1.11 (the latest is 10.0.3.19 and note that 10.0.1.14 does not work either).

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-10-06T14:51:54+00:00

    Hi, NuTTz

    My name is Marc, thanks for participating in the Microsoft Community, I'm an Independent Advisor and I'll be glad to help you today.

    Try to run the troubleshooter for Bluetooth. To do it, Go to Settings - Updates & Security - Troubleshoot. Click on Bluetooth under Find and fix other problems. Follow the on-screen instructions.

    Try to update the Bluetooth drivers

    https://support.microsoft.com/en-us/help/402844...

    Regards,

    Marc M.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2019-10-06T14:44:15+00:00

    ASUS X555UB Laptop has a AR3012 Bluetooth device with all the default drivers installed.  

    Problem is that all the bluetooth connections pair immediately and then fail to connect with the following error displayed instantly as if it didn't even try: "that didn't work make sure your bluetooth device is still discoverable"

    I have made peace with all other devices not connecting but really need the headset to connect.

    The problem is not with the headset as it works on other windows editions. I've not been able to connect since build 1709... now on build 1903.  Prior to that it all worked fine 

    Latest driver applied from Windows Update Catalog is 10.0.3.19

    I've tried everything including logging support call with ASUS support who simply refer to the latest driver

    Was this answer helpful?

    0 comments No comments