I finally got my Bluetooth adapter (a Kensington Bluetooth USB Adapter 2.0) working. Initially when I bought it, trying to install the factory supplied driver wouldn’t work. After a tiresome exchange with support, where they informed me that there was no Vista driver available, and they didn’t have any information about whether or not the driver would be developed.
Well, apparently they developed one (yay Kensington), but failed to inform people who had filed a request for it (Booh! Hiss!). However, when I tried to install it, everything seemed to work fine until a message box popped up informing me that the installation had failed. Digging through the Vista Temp directory, I found the installation log, with one Error message (the rest was fine): “ERROR Device plugged in, no MS stack”.
After trying to run the installation program with Administrative rights, and with UAC turned on and off, I was ready to give up. The funny thing was that the installation program just seemed to download the actual installation program, explode it, run the setup program in there, and delete it when it finished or failed. So, during a new attempt, I grabbed the directory that the installation program created. It has the platform specific files (in my case 64-bit), a setup program and some other stuff. Of course, the installation failed again, but at least I had the files now.
Update:The files are located in \Users\[you]\AppData\Local\Temp\BTW_6.0.1.6200.
When I pulled up the Device Manager in Vista, it showed the Bluetooth EDR dongle listed. I tried several different things (which I won’t mention, because they didn’t work), until I decided to Update the driver for the dongle. When Vista asked me for the driver, I pointed it to the driver directory within the exploded installation directory, and Vista was happier than a clam to install a bunch of devices (Kensington Bluetooth EDR Dongle with trace filter, Microsoft Bluetooth Enumerator, and two Bluetooth devices in the Network adapters group). Yay!
The next (and last) step in setting up the adapter with my Motorola RAZR was the easiest: go to Control Panel, Bluetooth Devices, and Add a new device. Make sure your phone is discoverable, and set up a passkey. Voila! The phone should now be connected.
Next thing on the list is trying to grab floAt’s Mobile Agent. I have an older version installed, and have already figured out that the only way floAt can talk to my phone seems to be to use the COM port (when you pull up Bluetooth Devices, click your phone, select Properties, and go to the Services tab, it will tell you which COM port the phone uses).
Related posts:
Thank you for posting this. I’ve been trying for several months off and on trying to get my Bluetooth adapter to work with Vista 64. This finally solved my problem!
Took me a while but I found the installation program directory.
Here goes nothing!
Can you give us all a hint as to where the files were extracted?
Nevermind, I found it. Thanks very much for this post! Here are the steps I followed to work around the error:
1) Uninstalled any WIDCOMM Bluetooth software
2) Ran the Kensington Bluetooth update utility (linked above)
3) During installation, files are placed here:
Users[you]AppDataLocalTempBTW_6.0.1.6200
4) Copy this folder to some other place
5) Run BTW.MSI in the “Win32″ folder
6) ???
7) Profit!
Nevermind, I found it. Thanks very much for this post! Here are the steps I followed to work around the error:
1) Uninstalled any WIDCOMM Bluetooth software
2) Ran the Kensington Bluetooth update utility (linked above)
3) During installation, files are placed here:
\Users\[you]\AppData\Local\Temp\BTW_6.0.1.6200
4) Copy this folder to some other place
5) Run BTW.MSI in the “Win32″ folder
6) ???
7) Profit!
Hey Jon/Ryan,
I’ve updated the post with the directory the files are extracted. Thanks for pointing it out!
Hey Jon/Ryan,
I’ve updated the post with the directory the files are extracted. Thanks for pointing it out!
That post was awesome!!! it works great for me!! Thanks a lot!!!
That post was awesome!!! it works great for me!! Thanks a lot!!!
Nice information. Worked great. That folder was hidden from me, but I clicked on Tools, Folder Options (in the Users Folder), the tab View and check the circle “Show Hidden Files or Folders”. I just got a new computer so that option of seeing those folders may be disabled. Luckily with the information provided here I knew I couldnt be any different that I was simply missing a folder. Thanks again.
Nice information. Worked great. That folder was hidden from me, but I clicked on Tools, Folder Options (in the Users Folder), the tab View and check the circle “Show Hidden Files or Folders”. I just got a new computer so that option of seeing those folders may be disabled. Luckily with the information provided here I knew I couldnt be any different that I was simply missing a folder. Thanks again.
Thanks so much! After hours of trying to get the stupid Vista version to install, I did a Google search about my problem and your page was at the top of the list. Next thing ya know, my bluetooth was up and running within minutes! Thanks again!!
Thanks so much! After hours of trying to get the stupid Vista version to install, I did a Google search about my problem and your page was at the top of the list. Next thing ya know, my bluetooth was up and running within minutes! Thanks again!!
To All,
Problem: Kensington 2.0 Adapter No Vista 64 Bit Drivers
Solution, Go here:http://global.msi.com.tw/index.php?func=downloaddetail&type=driver&maincat_no=131&prod_no=101
Download vista 64 bit and run Setup.exe then plug in adapter, then when install completes right click on bluetooth in tray and add device then turn on keyboard and reset keyboard.
No More headache……………….
Hey Dan,
Are the Kensington and the MSI products interchangeable, or are you just using the Microsoft Bluetooth stack from that page?
Cheers,
Ronald.
The MSI driver was moved but it worked on my 64 bit Vista also. http://www.msi.com/index.php?func=driverfile&dno=5286&i=0
The MSI driver was moved but it worked on my 64 bit Vista also. http://www.msi.com/index.php?func=driverfile&dno=5286&i=0