Hl 340 Driver Windows 10
Hl 340 Driver Windows 7
I am trying to install a Prolific PL2303 USB-to-Serial port 1ft. Adapter cable.
This particular one made by Sabrent. It seems that lots of people don't have any issues, and they have XP, Vista, and Win7 drivers available for it. I downloaded the latest Vista driver installer from the Prolific website (, 12/2/2009). The driver says it installed. I then do a reboot. After system is up, I plugged in the cable. Windows detects I inserted the USB and displays the searching for drivers dialog.
Odd I thought. I click to watch the status and it ends with the message: 'Prolific USB to serial comm port (COM4) - Failed' In device manager it shows a question mark next to it. If it's a Vista driver, why would it fail? What can I do to get this to install? I also have another Vista machine that I tried it on, just to see if it was that machine or what.
It failed too!? Thanks for the quick reply. I wasn't installing as the 'Run As Admin' link at first, even though my account has Admin rights. But yes, then I started doing that, no change.
However, I'm happy to say I found the problem! After posting this, I did a search in these forums and came across ONE other post that had lots of feedback.someone in that one posted a link to drivers which I had not tried.
The thread is here:. The Vista drivers from cooldrives did the trick! I have no idea of the lineage of this driver package but they worked. And they worked when the ones on the included CD did not; when the ones from the Sabrent website did not, and when the ones from the Prolific website did not.
I think I just discovered the answer to my own problem based on your feedback. While digging up the information for my response to your questions, I discovered the specific com port that Windows had assigned to the Arduino (USB-SERIAL CH340 (COM11)). I selected that specific Com port in the Arduino program.and behold, it connected and is working just fine! Thank you for your willingness to help - it turns out that Windows already had the driver installed and the error was prominently located somewhere between the keyboard and deskchair.:).