Posts Tagged ‘bluetooth driver’

After spending a lot of time and research in internet on bluetooth peripheral device driver, I found this post which was very useful and answered all the questions. Filtered content of the same post is added here.

This is How to Resolve the “Bluetooth Peripheral Device Doesn’t Have a Driver:”
This guide will be most useful for those with similar hardware configurations… and for those who have tried all the other nonsense to no avail.  Especially that oft-repeated “Just install Windows Mobile Device Manager.”

Step 1: Ignore 99% of what you think you’ve learned about this problem.

It will *most likely* boil down to a missing COM port.
Step 2: Definitely ignore the bit about installing the Windows Mobile Device Center
(Unless you have a Windows Mobile-based phone and/or have some other use for a Windows 7 flavor of Activesync.)
Step 3: Stop looking for a driver for something named a “Bluetooth Peripheral Device.”
There ain’t no such thing. If you watch the Bluetooth installation unfold, you’ll notice that all the components of Bluetooth start out as “Bluetooth Peripheral Device,” and then once Windows IDs each item, the appropriate driver is installed and the name changes from “Bluetooth Peripheral Device” to something like “Bluetooth Hands-free Audio” or “Bluetooth Remote Control” etc.
— — —
Unfortunately, most people reading this will have attempted one or more of the following:
1.) Installing that stupid Windows Mobile Device Center
2.) Installing any number of who-knows-what Bluetooth drivers from who-knows-where
3.) Running all sorts of third-party driver utilities
4.) Forcing various driver installations to run in Vista, XP, or Win98 mode
5.) Sacrificing countless animals
The end result is a plethora of totally unnecessary software and/or driver installations and/or updates… and a few dead animals.
— — —

With each machine I connected the following headsets: a Plantronics Voyager Legend, Motorola S9, Motorola S805 and Matrix AF62 as well as one Samsung S3 and one HTC Android.

1.) If you have done any of the fruitless steps mentioned above, get into control panel and delete everything you installed.  Kill any Broadcomm or Widcomm bluetooth entries. Delete any 3rd-party driver maintenance apps. Reboot to a clean machine.
2.) Locate and install any latest driver for the adapter depending on the vendor (like Broadcom)
3.) As you install one of the above drivers, you’ll see a notification regarding the installation of the various components.  Click on that pop-up and watch the progression.  You’ll see that each “Bluetooth Peripheral Device” gets a new name as the related driver is installed.  In my dozen+ tests, each & every item at this stage got the green checkmark of success.
4.) NOW attempt to pair the device of your choosing.  If that manufacturer provides separate drivers, do not install them yet, regardless of their instructions.  See how far Windows gets on its own.
5.) As soon as the pairing begins, you’ll see more notifications regarding the individual driver components.  Click on one of these and watch a similar progression… EXCEPT that you will have one “Bluetooth Peripheral Device” with the dreaded Red X and the complaint that no driver was found.
6.) Do not despair! This will happen the first time you pair any new Bluetooth device.
7.) Wait for the installation to complete.  Despite the dialog showing the list of Bluetooth components with the one red X, you probably have another window saying that the Bluetooth device paired perfectly.  But you and I know it didn’t. Confidently click to close that dialog.
8.) Go to Device Manager (through Control Panel, Computer properties) and you’ll spot that cursed Bluetooth Peripheral Device that is sitting there in the middle under “Other Devices.”
9.) Right-click on the Bluetooth Peripheral Device under “Other Devices” and choose “Update Driver” — then:
  Click on:
  a.) Browse my computer for driver Software
  b.) Let me pick from a list of device drivers on my computer
  c.) In the list of Common hardware types, choose:
        —>>>>   Ports (COM & LPT)  <<<<—
  d.) Under Manufacturer, choose Microsoft
  e.) Under Model, choose “Standard Serial over Bluetooth Link” & click ‘Next’
  f.)  When prompted with the Update Driver Warning, click ‘Yes’
  g.) Joyfully read the message that “Windows has successfully updated your driver software”
  h.) Read it again for the fun of it and click ‘Close’
   i.) To confirm that this mess is really fixed (assuming compatible hardware, etc.) Right-click on the Bluetooth device and choose “Troubleshoot” — there should be no problems reported.
10.) You should not have to reboot, but you MIGHT need to cycle the power of your Bluetooth device Off & Back on to let it reconnect again (NOT re-Pair… just re-Connect). Out of a dozen tests, I only had to do this once, and that was with a 3-year-old-Bluetooth headset.