Csr Bluetooth Chip Driver
Garcia Miller
I have a laptop running Windows 7. Recently bluetooth has been failing and I'm struggling to find out why.It could be the drivers so I'd like to update them, I believe the wifi/bluetooth chip is Intel.
The Intel site offers a couple of tools that scan the system and report back on the make and model number - but as far as I can tell all they do is check what driver is already installed, not the actual hardware.
In that case you can always search the internet with your laptop model number to find out what exactly is in there, or perhaps download the drivers from your laptop maker support webpage, perhaps old but most likely working drivers and this might help you get the model number recognized.
Rightclick on your computer symbol -> settings
Open the device manager and search for something like bluetooth device.
Rightclick again on that device and open the Details tab.
In the dropdown field choose device description... and there you got your device.
I recently did a clean install of Win 10 on a new hard drive, and I have been unable for the life of me to get my bluetooth card working. Windows doesn't detect it, and it doesn't show up in device manager as an unrecognized device.
When I install the bluetooth driver, the card appears under device manager (but not settings or the action center) until the computer is restarted. It seems that windows is "updating" the drivers and removing the (in its view) absent device. I've installed all the versions of driver available on the Dell support website, and on the Intel support website here.
Given that a number of other people on this forum (linked below) have what seems to be the same problem across a number of different computer manufacturers, I presume that this problem is unrelated to the manufacturer and instead either with Intel's firmware or Windows' device detection.
To answer the obvious questions, yes, I do a full uninstall of the existing driver and restart the computer before installing a new driver, and yes, I'm downloading the 64-bit version of the driver to match my system. The installer completes and doesn't give any error messages. I choose the 'complete' option when installing the driver package. And my UEFI does have an option in the boot settings to enable/disable the bluetooth card, but that's set to 'enable'.
This Intel support article suggests the existence of a wireless diagnostic utility, but after I installed the PROSet package I didn't see any such tool. For a 400MB install it appears to be a very limited program.(I clicked on 'custom' and installed everything listed.)
My situation is different from the other posters in this forum in that my laptop came with Windows and all drivers preinstalled, and on that install the bluetooth card works fine. It's only with this clean install that Windows doesn't recognize the bluetooth card. I haven't formatted that drive, so I'm able to swap out my new hard drive (an SSD) for the old one (an HDD) to check the setttings. The driver version on the HDD is 19.10.1635.483, which is currently available on Intel's site but not Dell's. (Yes, I've tried installing that version as well.)
I've done some reading about how to backup/extract installed drivers and will likely give that a shot, but I'm doubting it would make a difference since this issue seems unrelated to any particular specific driver version.
NOTE: Any links provided for third party tools or sites are offered for your convenience and should not be viewed as an endorsement by Intel of the content, products, or services offered there. We do not offer support for any third party tool mentioned here.
Those are all clever troubleshooting steps. I wasn't aware that the power settings allowed for adjusting of individual adapters, and I certainly wouldn't have guessed that booting quickly could be the source of the problem.
1. There was a UEFI ("BIOS") update available, and it seems intended to address exactly what you believed to be the problem (i.e. card not receiving enough power). "Fixes: Wlan and Bluetooth device show "None" with BIOS Setup Menu." I installed the update, but there was no change.
3. I checked the power settings, and the wireless adapter was already set to "maximum performance" on AC, which is how I've been using the computer. I set the on battery option to maximum performance as well, just to be sure.
(I did try uninstalling and reinstalling the latest Dell driver after going through all of these steps. I haven't yet gone through the process of fully uninstalling the wireless drivers as well before attempting a reinstall. I've seen that recommended on other threads but it seems unrelated to this issue. That said, I can do that if you think it's worth trying.)
On the other hand, if the bluetooth module is powered up enough for the UEFI to detect it, then it's powered up enough for windows to detect it as well, no? I don't understand why windows wouldn't recognize a device that it supports and the UEFI is aware of. The UEFI passes all hardware information on to windows, no? It should at least appear as "unknown device" or something to that effect.
I must say that at this point I'm stumped. My next step would be to acquire a second HDD and do a clean install of windows on it to see if the boot time really is the key factor or if the driver that came preinstalled on the original HDD had some kind of fairy dust in it that makes it and only it get the bluetooth card working .
Is there really no information to glean from digging through the properties listed for the bluetooth module (device manager --> bluetooth adapter --> right-click --> properties --> details --> list of 70+ attributes)? Interpreting them is far beyond my level of knowledge but perhaps they could be of use to your engineers.
Shortly after doing the clean install of windows, I installed a driver package called SCPToolkit to allows PS3 controllers to be read by windows as XBOX 360 controllers (since 360 controllers have much better support on windows). I wasn't aware of it at the time, but that driver package included a bluetooth driver to allow PS3 controllers to connect via bluetooth. Uninstalling that package and then and reinstalling the dell bluetooth driver resolved the problem. I've now restarted my computer 5 times just to be sure because I'm having trouble believing that the issue was something so small and something I completely overlooked. There must be a problem with that SCP package not properly supporting the wireless card I have. Not having bluetooth support for my PS3 controller isn't a big loss so I'll gladly give that up to have bluetooth working properly with everything else.
Anyways, my bluetooth module appears in device manager and settings and I've tested it by pairing it with my phone. Everything's working as it should. This is now an issue for the SCP people to solve and I'm not going to pursue this any further.
If you'd like, I can recreate the problem by installing that driver package again to provide you with the diagnostic results you requested. I did save them, but they were made after I uninstalled the SCP package so they won't show anything
- when the issue was present, installing the bluetooth driver caused a new group to appear in device manager: Bluetooth --> Intel Wireless Bluetooth. Now that everything's working, installing the bluetooth driver also produces 'Microsoft Bluetooth Enumerator' and 'Microsoft Bluetooth LE Enumerator', and under Network adapters 'Bluetooth Device (Personal Area Network)' and 'Bluetooth Device (RFCOMM Protocol TDI)'. I imagine those details would vary from system to system, but if there's only one new item in device manager after installing the bluetooth driver then there's likely a problem.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
The issue with the update is that it alters the code in a way that causes the system to fail to recognize the Bluetooth chip. Instead, the system sees an unknown device that is not communicating properly, resulting in a message indicating an error code 43.
If you open Device Manager (e.g. right click Windows Key -> Device Manager or from the Control Panel), you should now see that the Bluetooth section has reappeared and there are no Unknown USB devices in the USB section. This means that your Bluetooth is now working again.
"According to a thread on the Microsoft Community forum ( -us/windows/forum/all/bluetooth-disappered-from-device-manager-with/fd246f79-c31c-40a2-a0a1-5660e0e07cfc), some users have reported that the Bluetooth device has disappeared from their Device Manager after a Windows update. The thread includes several suggestions for resolving the issue, including running the hardware troubleshooter and reinstalling the Bluetooth driver."
Your subject title seems to refer to CCleaner's automatic update (which updates CCleaner itself and nothing else, so would not touch anything to do with Bluetooth), but the content is talking about Windows Update.
Looking for your licence key, expiry date or download link? Check here first: -lookup
To find out how we protect your privacy - read CCleaner's Data Factsheet.
What's new? Check the latest CCleaner for Windows release notes.
CCleaners automatic update feature (specifically regarding Bluetooth drivers) was the method I used to install the 'updated' bluetooth driver'. There was no warning that this function could lead to such a fail in the system.
Your subject title seems to refer to CCleaner's automatic update (which updates CCleaner itself and nothing else, so would not touch anything to do with Bluetooth), but the content is talking about Windows Update.
To clarify, I was referring to the Driver Updater (which I inferred was pretty automatic in itself). Also, the content is how to fix the problem, and I cite where I found the solution(s) so that other people could check my work in case it didn't work for them, as the solutions presented within the CCleaner forums will not work.
d3342ee215