Posted  by  admin

Prolific Usb To Serial Driver Code 10

Prolific Usb To Serial Driver Code 10 Average ratng: 6,5/10 9007 votes

I also download the driver listed (AMD64_X86-en-20357822_453c563f64689a47c9be3972b95db24900db3798.cab)above from Microsoft and manually added it. You must remove the Svk2pl.inf from the.cab, disable the device, select the.inf file. After you are done the will show up as Gigaware USB to Serial Cable (COMx) x=port. If you move the connection to another USB port you have to make the same change or you will still have the problem. The device works great now. I used the PL203CheckChipVersion.exe to verify my chip version, I am using PL-2303 XA / HXA chip. This tool will not work if you are receiving the (Code 10) error.

In the Search box, enter the model type of your Prolific USB to Serial and click go. Select the link for driver downloads and follow the on-screen instructions to download the most recent driver. Be sure to choose only the driver that is compatible with your Windows version. Home » Prolific USB-to-Serial Comm Port (COM3) Use the links on this page to download the latest version of Prolific USB-to-Serial Comm Port (COM3) drivers. All drivers available for download have been scanned by antivirus program.

As a resolution to this, the solution is to roll back the driver to a 2007 version. And, the instructions can be found on the Miklor web site – At this site, follow the directions to reverse the driver from a newer version to the legacy version and you’ll once again be able to program your radio using the Chirp software.

In this process, Driver Doctor will scan for your PC until downloading the outdated or incompatible drivers on Windows 10, including the prolific USB to Serial driver. Cummins insite 8.3 download.

Installing the same software on a workplace network, with possibly dozens or more networked computers, is an entirely different matter. Certainly there are noteworthy websites with documented / packaged fixes that can be tested if not done so already. Description of the Fix Fixing the driver issue (Code 10) can be achieved in four steps. With the Prolific USB adaptor fitted to the target computer, uninstall the Windows Prolific driver from Device Manager for that USB port. With the Prolific USB adaptor fitted in the same port, i nstall the Prolific driver version applicable to the Prolific hardware used. This step may require some experimentation with earlier Prolific driver versions. Version 3.3.2.102 worked for both my Windows 10 installations.

Putty is constatly giving an error „Unable to open connection”. In addition in the device propperties I found an error This device cannot start. (Code 10) A device which does not exist was specified. Error code 10. A quick investigation gave an unpleasant anwser – PL2303 chips are fake!

Plug in one (1) of your USB-To-Serial adapters and click “Continue”. When it finishes, Reboot your computer.

Or you may get no error at all, but your device will still not work. If your adapter was working prior to going to Windows Update, you can 'roll back' to the previous installed driver and all will be well once again. However if you didn't have a previous driver installed that worked - you'll have to go through the process of removing any PL-2303 driver installation programs, the actual driver files, and the information (.INF) file, BEFORE you are able to successfully install the correct driver. (What worsens this issue is that there are many 'Prolific Driver Removal Tools' that do not work properly.) And Windows 8, 8.1 and Window 10 are set by default to automatically update your drivers without your permission or even notifying you of the update. So no matter how many times you remove the driver files and reboot - the next time you insert the USB-To-Serial adapter, Windows installs the newest non-working version again. Only 64-bit driver I have ever found that works with all the 'Prolific' adapters is Version 3.3.2.102. Below installer program will remove all of the incompatible drivers — make a change so that Windows can never update the driver without your approval — and install the Version 3.3.2.102 compatible drivers.