Share via

Microsoft Bluetooth Enumerator attempts to install wrong Bluetooth Peripheral Devices for CSR8510 A10

Anonymous
2016-02-26T08:11:23+00:00

This question is applicable to all Bluetooth adaptors that are based on the CSR8510 A10 chipset (eg Sitecom CN-524).

On different machines, I will have a different resulting behaviour of installing the drivers for this adaptor. Eg a Lenovo X240 laptop will install fine and a Lenovo T430s will NOT install fine. Both machines run Windows7 64 bit.

It's not an option to install the drivers that came with the dongle, as these are based on the CSR Harmony software suite, which prevents the Microsoft Bluetooth stack to be used. Which is what I want, and it has been shown to work.

When plugging in the adaptor, Windows will attempt to install a Generic Bluetooth Radio driver, which is fine.

I've been able to isolate the problem to the Microsoft Bluetooth Enumerator driver that is also automatically installed:

  • On the machine that fails to install correctly, this driver will attempt to install 3 Bluetooth Peripheral Devices (network adaptors): one for Bluetooth Hands-Free Audio, one for Bluetooth L2CAP Interface and one for Bluetooth Remote Control. These drivers fail to start (error code 10), which is to be expected as these drivers are not attempted to be installed on the computer that works fine.
  • On the machine that installs the adaptor correctly, these peripheral devices don't appear. Instead, drivers appear for Bluetooth Audio and Bluetooth Server.

I struggle to understand why there is a difference in behaviour between the two computers and I'd appreciate any tips that will help me in making the failing computer NOT attempt to install these failing drivers!

Thanks!

Windows for home | Previous Windows versions | 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

Answer accepted by question author

  1. Anonymous
    2016-03-06T22:36:52+00:00

    For any other person that might stumble upon this: I was able to resolve the issue.

    The problem seems to be that on some computers, the "WIDCOMM Bluetooth Software utility" is installed. This software utility might be branded specifically for your computer manufacturer, eg in my case it was called "Thinkvantage Bluetooth Software".

    Disabling the onboard Bluetooth adaptor doesn't fully remove all network adaptor drivers that are associated with this piece of hardware: the WIDCOMM Bluetooth Software utility adds a few network adapters of its own.

    When you then decide to use a Bluetooth adaptor from a different vendor, installing the drivers might fail when the chipset you're installing is not compatible with these network drivers that belonged to a different chipset.

    I realise the use case of this is not very typical, but it's highly confusing when it does happen!

    In order to resolve the issue, make sure you uninstall any Bluetooth software from other vendors before installing the drivers for your new Bluetooth adaptor.

    4 people found this answer helpful.
    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2016-02-27T05:37:06+00:00

    Hi Rene,

    Thank you for posting your query in Microsoft Community.

    A Code 10 error is generated in Device Manager in one of the following situations:

    • Device Manager can't start the device.
    • One of the drivers that the device needs does not start.
    • Device Manager has insufficient information to recognize the error that is bubbled up by the device driver.

    Note: In this situation, the Code 10 error can be a very generic message that indicates some kind of unspecified driver or device problem.

    The Code 10 error is mainly related to hardware and device driver issues or to compatibility issues between hardware drivers and additional software that is installed in Windows. Therefore, we recommend that you troubleshoot these issues by focusing on device drivers, on device configuration issues, and on hardware compatibility issues.

    Method 1: Restart your computer if you haven't done so already.

    There is always the chance that the error Code 10 you're seeing on a device was caused by some temporary problem in Device Manager or with the hardware. If so, a reboot might fix the Code 10 error.

    Method 2: Incompatible, outdated, or corrupted device drivers

    If you suspect that the Code 10 error is related to incompatible, outdated, or corrupted device drivers, try the following troubleshooting methods.

    Update the hardware's device driver through Windows Update.

    Update the device drivers from the vendor's website. Follow their installation or update instructions.

    • If the device was preinstalled on the computer, visit the computer manufacturer's website.
    • If the device was installed after the purchase of the computer, visit the device manufacturer's website.
    • If the device was preinstalled on the computer, and the computer manufacturer does not have an updated driver for the device, visit the device manufacturer's website.

    Note Make sure that the device drivers that are being installed are compatible with your current Windows version and platform.

    Method 3: Install the latest Windows service pack

    Microsoft often releases service packs and other patches for Windows, one of which might contain a fix for the Code 10 error.

    Service Pack: Often abbreviated as SP, a service pack is a collection of updates and fixes, called patches for an Operating System or a software program. Many of these patches are often released before the larger service pack, but the service pack allows for an easy, single installation.

    Patches: Software patches normally fix bugs but they can also be released to address security vulnerabilities and inconsistencies in a piece of software. Skipping over these important updates can leave your computer, phone, or other device open to malware attacks that the patch is intended to prevent.

    Method 4: Install the driver in compatibility mode

    a. Right click the driver installation file and select Properties then tap or click the Compatibility tab.

    b. Place a check in the Run this program in compatibility mode for: box.

    c. Tap or click the drop down box and select a previous operating system, then tap or click OK.

    d. Try installing the driver and check.

    Hope this information is helpful. Please feel free to reply in case you face any other issues with Windows in future.

    0 comments