In my frantic efforts to solve the "bluetooth paired but not connected" problem, I seem to have removed the bluetooth driver altogther. How can I get it back? I'm running Build 19042.964. And has the bluetooth problem been solved yet? My search for a solution has only revealed a horde of people asking the same question and getting answers that didn't work.
I have Bluetooth mice working on a few Notebooks, no major problem unless I change the last one used to a different one, most are from Targus. I have read of VMs not loading drivers for the Bluetooth adapter [usually part of the Wireless adapter]. With difficult issues or no built-in BT adapter I use a USB dongle such as from IOGEAR.
- driver for what, exactly? Bluetooth support for your laptop, or for an external device?I seem to have removed the bluetooth driver altogether.
You have an (unspecified) model of an ACER laptop.
If you are referring to the laptop's bluetooth driver, then either
- restart- normally it would be installed on restart on compatible devices.
- try going to the driver download page for your Acer laptop (unspecified model).
If your (unspecified model) supports Win 10 you should find a driver there.
If your laptop is old and is not specified to support Win 10, I suppose it's possible this might explain your difficulty, although that would be unusual.
Feel free to post a screenshot of your device manager, if that is likely to help anyone understand better.
I wrote a long reply to this thread and submitted it, but now I can't find it. I hope someone can locate it, since it would be difficult for me to reconstruct it.
Hello @pwabrahams,
Many users on this forum have found great success with using the following . . .
> TenForums Post - Link to useful Post
> Bluetooth Command Line Tools - Website
I hope this helps.
First, I'll mention that my computer is an HP Pavilion laptop, not a Dell. I'm running a dual-boot system with Kubuntu 20.04. I've encountered the same "failure to connect paired device" on the Linux side, and 'm pretty sure the two are related.<br><br>The way this happened was that I tried uninstalling the Bluetooth driver in the hope of loading fresh copies of all the Bluetooth software. Before this attempt, Device Manager listed five items under Bluetooth; after doing the uninstall, removing a driver, and restarting, I had only four. I don't remember precisely what I uninstalled because I expected the restart to restore anything that was missing. The missing item was the third one, I believe; it came right after the Intel item and mentioned Broadcomm. I was trying to pair my headphones. which are from MPOW. Before the mishap, they showed up in the list of devices; now they don't.<br><br>On the Linux side, I get the same failure to connect. Interestingly, I sometimes get a momentary connection but then it drops out. I know that because I was running <strong>bluetoothctl</strong>. It actually showed the the headphones as paired and connected, but half a minute later it showed the adapter as "connected: no". The cause on the Linux side seemed to be in the kernel; I had made the recommended corrections to the contents of <strong>/lib/firmware/brcm,</strong> replacing one module and renaming another. but it didn't help.<br><br>I had a conversation with Bryan in Kinovo tech support, who knew a lot about the subject. Kinovo is the company that supplies the critical chip. It seems that the problem is due to some overly ambitious design, trying to cram both the Bluetooth functions and the wireless functions onto a single chip because they he so much in common. The solution requires separating the two functions by making some BIOS changes, but unfortunately the HP version of the BIOS lacks the necessary settings. Bryan explained that I would have to ask HP about how to solve this problem, but he couldn't call them himself because of company policy about calling other companies. I was unable to figure out how to wend my way through HP tech support to get an answer.<br><br>I did wonder why the items in Device Manager had both Intel drivers and Broadcomm drivers (the second and third items) for the same function, Now we know.<br><br>It might help in responding to this post to know where I"m coming from. I'm 85 years old and have been working with computers since I was 17. My knowledge of programming is both wide and deep, but my memory is failing and I'm nowhere as sharp as I used to be. And the field has changed enormously over my lifetime.
- - - Updated - - -
My previous post is hard to read because I wasn't logged in when I wrote it.
The way this happened was that I tried uninstalling the Bluetooth driver in the hope of loading fresh copies of all the Bluetooth software. Before this attempt, Device Manager listed five items under Bluetooth; after doing the uninstall, removing a driver, and restarting, I had only four. I don't remember precisely what I uninstalled because I expected the restart to restore anything that was missing. The missing item was the third one, I believe; it came right after the Intel item and mentioned Broadcomm. I was trying to pair my headphones. which are from MPOW. Before the mishap, they showed up in the list of devices; now they don't.
On the Linux side, I get the same failure to connect. Interestingly, I sometimes get a momentary connection but then it drops out. I know that because I was running bluetoothctl. It actually showed the the headphones as paired and connected, but half a minute later it showed the adapter as "connected: no". The cause on the Linux side seemed to be in the kernel; I had made the recommended corrections to the contents of lib/firmware/brcm, replacing one module and renaming another. but it didn't help.
I had a conversation with Bryan in Kinovo tech support, who knew a lot about the subject. Kinovo is the company that supplies the critical chip. It seems that the problem is due to some overly ambitious design, trying to cram both the Bluetooth functions and the wireless functions onto a single chip because they he so much in common. The solution requires separating the two functions by making some BIOS changes, but unfortunately the HP version of the BIOS lacks the necessary settings. Bryan explained that I would have to ask HP about how to solve this problem, but he couldn't call them himself because of company policy about calling other companies. I was unable to figure out how to wend my way through HP tech support to get an answer.
I did wonder why the items in Device Manager had both Intel drivers and Broadcomm drivers (the second and third items) for the same function, Now we know.
It might help in responding to this post to know where I"m coming from. I'm 85 years old and have been working with computers since I was 17. My knowledge of programming is both wide and deep, but my memory is failing and I'm nowhere as sharp as I used to be. And the field has changed enormously over my lifetime.- 2 Hours Ago
Quote