This device cannot start. (Code 10).

Question

Prolific USB - to- serial comm port (Com 8), the device manager shows an yellow exclamation mark. I checked for update driver but it shows the driver for this device is up todate.

This device cannot start. (Code 10), this error shows when I connect U232-P9 USB to serial converter cable. I used this converter in the same OS (win 7) previous time.

After reinstalling  windows 7 I got everything fine except this error for this cable only.

Please help me.

Answer 1

Hi Alim_77,

Follow the methods listed below:

Method 1: Firstly, Open the Hardware and Devices troubleshooter to run the automated troubleshooting services.

Open the Hardware and Devices troubleshooter

http://windows.microsoft.com/en-us/windows7/Open-the-Hardware-and-Devices-troubleshooter

Method 2: Refer the following knowledgebase article for instructions on fixing code 10-related error messages:

Description of Code 10-related errors that Device Manager generates in Windows-based computers

http://support.microsoft.com/kb/943104

Answer 2

maybe you are using a device with an older PL2303 chip, for example PL2303HX/HXA, and that is why the new driver from Prolific website does not work, in that case you have to use the older driver version, for example this ones:

http://www.miklor.com/COM/UV_Drivers.php#install these drivers works fine with older PL2303HX/HXA chip and in Window 7/8/8.1/10.

Answer 3

Uploaded the driver just in case here: http://www.4shared.com/zip/YkaMNwiU/AU0002B.html

P.S. You may have to enable unsigned drivers in system policies (search Web for that, too large to cover here and separate topic explained in many other articles).

P.P.S. I've used XP version for Win 7 32bit, better try that first for Win 7 64bit.

Answer 4

I have had the same problem. Changing the driver fixed the problem. I just needed to...... DOWNGRADE the driver to version "4.0.100.1190" dated "03 August 2005". Yes, downgrade.

I have tried the latest version, and after meddling with policies and allowing unsigned drivers, it still worked with errors (data partially changed with random bytes, etc) and only downgrading the driver had finally solved the problem.

I have a copy of these, try to reach me not later than late October 2013 if you have had trouble locating the driver of given version.

By the way, I have Win 7 Pro 32bit on my Dev machine, did not try this on 64bit OS version. Should probably work...

Answer 5

Any other idea´s `

Got the same problem, tried all this, no luck..