Solved!
Go to SolutionNE
Northern Exile
4 Posts
0
1879
November 25th, 2021 05:00
Mysterious Bluetooth Problem - Advice Needed
Hello Community,
Apologies for this first-time post, I have lurked here for a while and found your advice and support a great help. Now I have a problem I can't solve:
I have an Optiplex 7010 running in i7 3770 and Win 10, nothing unconventional about it - apart from the fact that bluetooth has suddenly stopped working and although I can see the service is still running (via services.msc), nothing I can do will induce it to see my USB BT dongle. I've checked the dongle itself is still OK (it is), but no matter what I do I cannot get it to load in device manager. I've tried loading a separate driver for the device, that failed. Any advice would be a huge help as I need bluetooth connectivity every day - this is a real problem.
Thanks in advance
NE
Chino de Oro
11 Legend
•
8458 Posts
•
46451 Points
854
0
Posted November 25th, 2021 07:00
@Northern Exile , check to see if you may have turned on airplane mode by accident.
Northern Exile
4 Posts
846
0
Posted November 25th, 2021 08:00
@CdO Thanks for the reply, but this is a desktop PC (an MT) and doesn't actually have an airplane mode ......
Chino de Oro
11 Legend
•
8458 Posts
•
46451 Points
842
0
Posted November 25th, 2021 09:00
@Northern Exile , yes it does, on bottom right of your screen, click on the notification, you will see several tiles with description, expanse if needed.
Northern Exile
4 Posts
836
0
Posted November 25th, 2021 10:00
Ah, I see what you mean. Flight Mode actually wasn't added to my Quick Actions in the Action Centre, I only had three tiles active - I added it just to make sure it was turned off (it was). Thanks for the suggestion though
Northern Exile
4 Posts
822
0
Posted November 26th, 2021 04:00
Just thought I'd let you know that I have solved this. It seems that a recent driver update (CCleaner Pro) installed CSR Core Bluetooth 4.0 as the primary BT driver and this is apparently incompatible with Windows 10. It wasn't showing up as a Bluetooth device in Device Driver, but eventually I found it under USB Controllers (helpful eh?) and rolled it back to "generic bluetooth device", it came alive instantly.