Pl2303 Driver Free Download

[Desmond Hutchins]

Ihave a few handheld radios that I need to update the frequencies and when I connect to the USB, it fails to connect. In device manager and Ports it says - "Please install corresponding PL2303 driver to support Windows 11 and further OS"

Hello! You've posted your question in the Tech Community Discussion space, which is intended for discussion around the Tech Community website itself, not product questions. I'm moving your question to the Windows 11 space - please post Windows 11 questions here in the future.

Windows 11 update loaded Prolific PL2303 driver 3.8.40.0 and when I go to device manager it says "Please install corresponding PL2303 driver to support Windows 11 and further OS" This driver does not even attempt to communicate with my X10 CM11 hooked to my serial port. I had to go to Prolific website and load their current driver 3.6.81.357. (uninstall driver first) Serial to X10 device now working fine. Don't install Windows update for Prolific or it will change it back.

This should resolve the issues with the serial adapter not being detected after the first connection is closed as well as an issue with multiple serial adapters on the same computer. We have seen issues with cu and screen locking up with macOS Mojave and Catalina that are unrelated to the serial adapter driver and it appears to be a problem with some of the serial connection software. The lock ups were verified without the serial adapter driver installed on the system. Additionally Catalina includes built-in support for this adapter and the separate driver is no longer needed when upgrading to Catalina ( 10.15.3 ).

@azzido no problem, windows 11 always updates drivers if newer cones out if the software don't see the programer it's easy just removed the recent update driver by windows 11 and all will work perfect. The drivers I provide are from the pl2303 maker so the latest for Windows 11 and 10. Regards

For reference, I attache the 2 drivers that work for me to this message. Only one is needed, just that they have different install methods (one is .exe and the other is right click on the INF), if you run the .exe version and you already have another version of the driver it will ask you if you want to uninstall (which I usually do) and then run again the .exe to install the driver.

However, there are several different serial UART chipsets out there. FTDI is the most common, and so far as I know most Linux systems have this one available by default. Apparently the ATEN serial bridge is pl2303 instead of FTDI. What do you see from:

FYI, a serial UART is not a serial console. The CONFIG_USB_SERIAL_CONSOLE is unrelated to the normal operation of a serial UART. The serial console already exists on the J21 connector via an integrated UART.

The USB end itself is working as expected, and even the driver is working as expected. The problem is we need a way to tell the driver to use this device when it has been told the device is wrong. I had hoped that telling udev to load the right driver would be sufficient, but apparently the driver still knows the device is incorrect for that driver.

It really looks like the PC uses the pl2303 driver I had originally expected to work. However, it is the combination of vendor ID and product ID being looked up in a table which associates a vendor specific driver to a USB component. That table is updated periodically. I am suspicious that the table used on the Jetson is out of date compared to the table used on the PC:

I had originally flashed the TX1 using Jetpack 3.1 and that time I was forced to connect it via the USB cable from a host PC. I then realized I wanted the newer version and redid the process with Jetpack 3.3. This time I did not need the USB cable, as the TX1 appeared to be detected as connected to our local network.

I must admit, I have no idea how this dark magic with Docker really works, but like I said, I am beginning to suspect that there are larger forces at work here that I do not understand.

This means regardless of whether there is a bug in checking manufacturer ID when scanning the device or not that the combination of IDs would correctly find the device driver is associated with your device.

Thank you for some pretty remarkable detective work. We have decided to connect our serial devices directly through serial ports instead, but in the future I hope someone will find this thread and be helped by the information contained within. I certainly have been.

Hi,All.Im trying to upgrade to WIN7 and a 64bit machine. I have XPSP3 on a 32 bit and my PL2303 works fine. Searched the forum and internet, downloaded and tried to install but WIN7 doesnt ven find the driver with Windows upgrade. Found E1boxUS17 doesnt work, PL2303 driver installer doesnt have the installer wizard. Any link, THANKS.

Are you sure that it is not automatically recognized by Windows 7 ?

Are you very sure that it is not a counterfeit FTDI chip ?

Can you retrieve the PID and VID numbers of it (with Device Manager or in linux with 'lsusb') ?

Any "Arduino" with a PL2303 is non-genuine; there was never an official Arduino manufactured with that chip.

The question is whether the PL2303 is genuine (in which case it should work with built-in or Prolific-provided driver), or counterfeit (in which case, it may take more effort to find a driver that works.) I don't know how to tell, beyond the info in the link I posted earlier.

It is getting harder and harder to install drivers as we have progressed from Sierra to High Sierra to Mojave to Catalina to Big Sur to Monterey to Ventura. I need to install Prolific PL2303 in Ventura. It will create a serial port that I can use with a USB-C to micro-USB cable to see the console output of my internet gateway appliance.

Gatekeeper has gotten five iterations (I guess, 1. Mojave, 2. Catalina, 3. Big Sur, 4. Monterey, 5. Ventura) more restrictive in what can be installed where. I am just wondering, whether there are ways to bypass those restrictions.

As Malcolm mentioned already a USB-serial adapter is required. The chipset matters, as that will determine if the kernel supports it out of the box. I use a PL2303 device which works nicely for the few times I need to access network equipment via PuTTY.

Furthermore, the notes I have from manuf is that it may need a Prolific pl2303gc driver. There is a pl2303.ko on my system but I cannot load it with insmod or probemod. I hoped if I could load that driver I could make some progress.

The PL2303GC is a low cost and high performance USB-to-Serial Bridge Controller. The PL2303GC provides a convenient small-factor solution for connecting an RS232-like full-duplex asynchronous serial device to any USB host. Prolific provides highly...

If the device does not appear automatically, the CP210x driver module may need to be loaded manually, especially if the version of Linux being run is not recent. If the driver was provided with the Linux distribution, run modprobe cp210x as root or using sudo. If it had to be built manually, run insmod ./cp210x.ko assuming the module is in the current directory.

Story starts with me searching for 5V USB cable with a 3.3V signal. After finding a suitable device, I did what was needed and forgot about it for a while. A few days ago I needed USB type-A serial device to do a quick loopback test and grabber the same, previously working, device. While the serial port did appear, I couldn't open it or send any data.

A quick trip to Device Manager has shown a problem: "THIS IS NOT PROLIFIC PL2303. PLEASE CONTACT YOUR SUPPLIER." Yes, it's the exact nonsense that FTDI pulled years ago - using Microsoft Windows Update mechanism for their authenticity enforcement.

Now, you might thing this is their right. And I can see how they might be annoyed with fake chips using their drivers. However, their beef should be with fake chip suppliers and not with the end customer. For me the concept of bricking device owned by an unsuspected user is a bridge too far.

My case is probably the standard one. I bought device without knowing it has a fake chip in it. I paid the seller, he paid his supplied, his supplied paid the manufacturer and so on. Now my device stopped working. Money is long gone and so is the supplier of the fake chips. I might have lost that money. If I can ask for refund, the seller might be out of money. Manufacturer might be out of money (especially if they didn't know they're dealing with fakes). The only person not out of money is probably the guy selling fakes in the first place.

While Prolific might look at me as a potential new customer since I am in the market for a new cable, I believe that's the wrong assumption. I am never going to knowingly buy a Prolific device again. Why? Because there is no way that I, as a customer, can check if device is indeed original or not.

What I do know is that Prolific is ready to play shenanigans with Microsoft update and brick my devices down the road. Since I cannot verify their authenticity myself, buying any Prolific device is something that might bite me in the ass. Unless something changes, I won't buy a single Prolific cable ever again. Their product is nothing special and there are many other manufacturers happy to take my money.

I hope that Microsoft will rollback driver since it's their update that's causing issues for the customer. I also hope that Prolific will see the error of their ways and stop bricking customer devices. I am hoping, but not holding my breath for either.

It is bricked. Yes, you can go back to an earlier driver on Windows 10. What about the Windows 11? What if I need some fix from the future driver of my legit cable. Since I cannot have two drivers with the same VID/PID installed, I need to select which cable I like the most. What if they misdetect that chip is clone?

3a8082e126