How I Got It To Work With Win7 - or - Finally The Damn Thing Works On My ASUS And Win7
923557
Like a hundred or so others here reporting that this item would not work with Win7, I also was ready to dig the box out of the trash and send it back to Amazon.

Started out by just plugging it in like I would with most devices.  After waiting 10 mins or so for Windows fruitless searching I cancelled that.
Since I'm installing on an ASUS net-book, I dug out the USB CD/DVD  drive, hooked it up and inserted the CD that came with the unit.  Well this seemed to take forever for extraction and installation.
Let me note here that I had the unit plugged in. Short of it is that the installation just would not take - error filled.
Next I deleted the installed drivers, etc., removed the unit and then reinstalled from the CD.  Again - no dice.  I could find the adapter in the device manager with an error that Win7 could not start it.
So at this point I am looking for the box.
Then I decided on one more shot, and here is what I did.

1. Remove all attempts of any previous installation.
2. Remove dongle from whatever you are using.
3. Google on over to the Kinivo download page, follow the links and download the latest drivers.
4. DO NOT run from a memory stick if downloaded using a different device - place the driver file directly on the hard-drive.
5. Execute program.  Let it do it's thing and near the end, if Windows pops up and says it's looking for updates - cancel it.
6. You are done only when you see the install program tell you it's done and wants to reboot.  Let it reboot.
7. After rebooting - I then plugged in the dongle.  Windows did it's thing again of installing drivers.  When it was complete - the dongle was found under the device manager with no errors.
8. Using control panel, under devices, I clicked add a bluetooth device - and it found my item instantly.

So hope this helps some of you.  I am now a happy camper.  Debated the 3 or 4 star thing: although it works fine now, it was certainly a pain and waste of time getting it installed - so a two star  deduction for that.

Good luck!
3513833
I have tried every piece of instruction on the website and forums.. I can not get this darn thing to work on my windows 10!!!
1715927
It's a massive pain in the ass to get installed and working correctly (On Win 8.1). I had to use a weird combination of installing two driver versions. Once I got it figured out though, it works well. The hardware is decent and I have used it several times on various projects so far. Good purchase
4346933
I popped this adapter into an HP d5000t running Windows 7 Ultimate 64-bit (recently upgraded from Vista Ultimate 64-bit). My impression was that this would auto-configure on Windows 7, without the use of the supplied driver CD. Almost. One device entry, "Marvell 91xx Config Device", failed to configure. In Device Manager, I selected the entry, chose "Update Driver Software...", popped in the installation CD and pointed the update at it. Problem solved. Since the install, I've been running a number of diagnostic and benchmarking tests on a drive mounted in a Thermaltake BlacX eSATA external "enclosure" without incident. I'm quite satisfied with the device.
1075644
It wasn't recognized by my system (Windows 7 Ultimate x64), but after inserting the included mini-CD and installing the drivers, it works fine. I do wish the installation CD had a routine to check if it was the latest driver and if not to download and install the latest. I gave it 5 stars because they followed up the sale with an email to tell me about the warranty, etc. Not many other vendors follow-up their sales with thanks and encourage their customers to respond if there are any problems.
4887028
You know, I hated this at first (while using Windows 7...could never figure out the drivers) but I'm glad I waited until I tried it on Fedora and for whatever reason it works perfectly on there once I "yum install" the bluetooth drivers. And with a few more package installs, I'm able to use the wiimote on fedora now and actually get into gaming.

Oh yeah and I'm using a Lenovo, that may make a difference why it'd work on Linux vs Windows...
1441442
Doesn't work with Windows 8... I should have looked into it further
3448456
The only issue was getting the drivers to install correctly with Windows 8.1. I would post the steps that I used, but I tried several methods and I cannot say for certain which method worked for me.
4124044
Can't get it to work with windows ME. Description says it supports windowsi ME.. can't find a driver for it either. any luck out there?
648642
Got it to work after a little search...these are the instructions that i got to work on WIndows 7 64 bit

1. Device manager

2. Right Click on 'Unknown Device' or remove the drivers first so that it appears as Unknown Device.

3. Click Update Driver Software

4. Browse Computer for Driver Software, DO NOT CLICK AUTOMATIC UPDATE.

5. Click on 'Let me pick from a list of Device Drivers on my computer'

6. IMPORTANT, go down to 'Microsoft Common Controller For Windows Class'. Highlight and click next.

7. This list varies by machine and i cannot be 100% sure but you should have a bunch of drivers in this list referring to your receiver, i actually have to use the 'XBOX 360 Controller For Windows Version: 2.1.0.1349 [13/08/2009]' driver to make it function and find my controller. (Getting this to appear requires that you first install this official microsoft Xbox 360 Accessories Software 1.2, [...]
3936872
I only hope that the HW works well,
The Windows 10 included has drivers problemas, is in loop all the time (just a moment message), the support did not know how to solve it, once I could access but the windows has configured a User "defaultuser0" which the seller does not know the key,
The CD with the drivers included is damaged and does not work.
The solution was to format and install windows 8.1,
699664
I'm using Win7Pro x64.  When it works, it works.  However, incompatibility issues can make this version of Windows a nightmare if you have legacy USB and audio gear from previous editions -- including Vista.

Unlike previous editions, what I'm seeing with Win7 x64 is a very slow adoption rate by OEM manufacturers. In the past, they were all in a hurry to jump on the bandwagon.  I guess this time, everyone it tired of the game and holding off for as long as possible before supporting this new version of Windows.  Frankly, it looks like the same nightmare Vista users endured.

I wish I had held off this version of Windows until 2011. If what you have works, don't break it with an upgrade until you can go to the store and Win 7 support on most all the gadget boxes.
3989106
Clairty if outstanding - if it only worked with Vista correcly.  Have downloaded drivers from everywhere with no consistent success.  Works fine with XP.
879030
Hey you guys, I didn't buy this from amazon, but I encountered the same issues you all have before this worked, so I figured I'd drop by and let you know of my experience:

Having read many reviews right here on Amazon, I was afraid to buy this cable (from different store), so I made sure to ask specifically "Is it compatible with Windows 8/8.1?", and I was reassured it was. So I purchased the cable and had it sent to the office to test it. It even came with a drivers cd which seemed great at first.

The first thing I noticed was the box, it noted compatibility up until Windows 7, this was the first "oh oh". Long story short, I couldn't make the cable work by myself, even though I went directly to the Sabrent webpage and tried to download new and (presumably) updated drivers. I went into many forums and downloaded drivers from many other places, and still nothing worked. On the Device Manager I kept seeing the cable with a yellow triangle next to it and some error (10), most likely meaning the system couldn't recognize the drivers.

I complained with the seller, and he agreed to install the cable himself through Team Viewer, and just this morning he did and now the cable is working fine. Today was his second attempt because the first time I had to interrupt him. The first time he did seem a bit lost and was doing pretty much the same thing I was, so I would assume he discovered something prior to this morning's attempt.

To keep it short, he pasted a folder in my laptop with new drivers that according to him contained "updated drivers".And that seemed to solve the issue, he simply reinstalled them.

IMPORTANT

**Sabrent sells different models of this cable, and they all look the same on the outside. You need to pay attention to which one you're buying. My box said SBT-USC1M, which is listed on the Sabrent webpage as compatible up to Windows 7. This added to my skepticism and frustration with this product, but either way I encourage you to check this yourself and do some research before purchasing any of these cables.

***The new installer that worked is identified like this: PL2303_Prolific_DriverInstaller_v1.10.0

While the ones I had and didn't work were: PL2303_Prolific_DriverInstaller_v1.6.0; PL2303_Prolific_DriverInstaller_v1.9.0.

*Additionally, the chip in my cable is identified as: PL2303 XA / HXA - which to best of my  knowledge and my very quick research is incompatible with Windows 8/8.1, yet my cable is working right now. So I can only guess my source is mistaken or I'm quoting it wrong, point is, the cable is working.

**When the seller reinstalled the driver he went manually into Device Manager and picked the latest version - I can only presume he did this because I previously had installed several older version which the system might be picking up.

If I had to buy Serial to USB cable again I would buy an ATEN one, which you can try to find here on Amazon, or their webpage. I never had any problems with those cables, but given my location a Sabrent was the best I could find.

So, to sum up, my Sabrent SBT-USC1M Serial to USB cable is working fine now, after a small headache. Though the cable is functional now, if I were you and had a chance, I would stick to the ATEN one. I work with VFDs that communicate only though serial port and have used these for a while and so far I trust them. Their cables seem sturdier than Sabrent's, and most importantly, I need had to go through this kind of headaches with ATEN, while with the Sabrent I feel like at some point something is going to happen again...

Well, sorry this took me so long. I hope this helps you.
419271
After just about killing myself trying to get this adapter to work on Windows Vista, Windows 7, and now windows 8 64 bit, the answer is pretty simple. I got terrible receptions and dropped connections every 5 minutes or so until I found this fix. Search for wnda310064bit and download the V2 driver there. You will have to uninstall the adapter from device manager first, then plug it in and the Netgear wizard will start. Click on don't agree (why anyone should agree to anything Netgear wants them to is beyond me). Unzip the file you downloaded and go to the folder, then right click on bcmwlhigh6.inf and select install. That's it, works just fine, reception is greatly improved and it doesn't drop connections anymore. If you can't get it to work on your Win 7 (I couldn't at first), you have to boot with F8 (boot options) and select disable driver signature enforcement. This dumbs it down to a lower driver set which isn't as good at getting a signal and will occasionally drop connections. Installing Win 8 and following the steps here fixed this for me. As others have said, if you have V1 of this adapter, throw it away and get something else (I wouldn't recommend this one either).
1071027
I did have some trouble with the drivers (I have windows 7), I contacted X-Rite, they sent me a link to a download and it worked perfectly.
393398
This works great for me on Windows7-64. The drivers are downloaded from Windows Update, so you don't need a disk (but make sure you have Internet connectivity the first time!). The driver is from "wch.cn" (not the usual Prolific or FTDI chipset), and is surprisingly signed by Microsoft. I've tested it from 9600 to 115200 baud with no problems. As you can tell from the pictures, there's only a D+ and D- line and no "reference" line. This means it's fine for testing, but shouldn't be part of anything you ship to a customer. In short, it works and it's a great price.