Qualcomm Atheros AR3012 Bluetooth not working in Windows 10

Anonymous

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

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

Answer accepted by question author

Anonymous

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

remove AR3012 & its drivers completely from 20H1, later let 20H1 detect it as Generic Bluetooth Radio.
download Qualcomm driver v10.0.1.15 from Microsoft Catalog website, install this driver via driver upgrade.
after v10.0.1.15 being installed, you might see additional device named in "Bluetooth LE" as the one in the Kirill's figure.
try to connect any BT device you couldn't connect after upgrading to 20H1, make sure the AR3012 really WORKS.
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.*

0 comments

206 additional answers

Anonymous

2020-11-23T23:01:05+00:00

Hi.

Tried method 1, didn't work.

Tried method 2, and the device completetly dissapeared from Device Manager and it's not showing up anymore, now I don't have bluetooth capability at all.
Was this answer helpful?

0 comments No comments
Caio G 11,930 Reputation points Independent Advisor

2020-11-23T22:06:26+00:00

Hi, Aleferca!

My name is Caio. I'm an Independent Advisor and I'll be glad to help you today.

Did you try updating and/or reinstalling your bluetooth card drivers? If no, please try doing it by following the steps below:

> Search for Device Manager on your Windows search bar and open it

> On the window that pops up, expand Bluetooth

> Right-click your bluetooth card and then click on Update driver

> Proceed the update and follow the given instructions

> Try putting your PC on sleep mode and check if the problem persists

If it doesn't fix, try reinstalling it:

> Locate your device on Device manager again

> Right-click it and select Uninstall driver

> Reboot your PC and let Windows install drivers again

> Check if the issue was solved

I hope this helps you! Please let me know if I can assist you more.

Best regards,

Caio G.

Independent Advisor
Was this answer helpful?

0 comments No comments
Anonymous

2020-11-23T21:59:15+00:00

I have a VAIO with Windows 10. The displayed information for bluetooth on Device Manager is a Qualcomm Atheros AR3012 (I have no idea if this is the correct bluetooth adapter or not).

For about 4 weeks now, every time I hybernate or put my computer to sleep, bluetooth stops working. It shows that it's on, shows me my paired devices, but it won't connect to or find any devices. It only works if I restart. The only thing that I have tried is the bluetooth troubleshoot but that didn't work.

Any help would be appreciated.
Was this answer helpful?

0 comments No comments
Anonymous

2020-11-16T11:13:20+00:00

I've downloaded 21.05.2015 10.0.1.0 version of the bluetooth driver from this link and it's working fine now. The old ones always better...

After a number of hours that I am ashamed to admit that MS has sucked from my life, I saw this post and did the same as you, but with version 11.08.2016 10.0.1.11, and my same exact problem was resolved. Like you said "The old ones always better..."

MANY, MANY, THANKS!!!!

After a year of uneventful operation, this issue just reoccurred for me, just after a Windows update.

I reloaded version 11.08.2016 10.0.1.11, and all is well again
Was this answer helpful?

0 comments No comments