Of the first driver have been covered by the second. In the system actually did this is difficult, generally because the trails Theįirst actually works, and the second fails. Rather, two separate drivers eachīelieve that they own the packet, and each attempts to complete it. The easiest case, a driver actually attempted to complete its own packet We’re still seeking a solution with Prolific.īased on what we know so far, this does appear to be a driver problem that will require an updated driver package from Prolific.įor background, this is the low-level error/problem (copied out of !analyze -v of the dump)Ī driver has requested that an IRP be completed (IoCompleteRequest()), but PPS: In meantime, you can download the older driver ( v3.8.39.0 worked for me) and use it instead.Thanks for checking up on this. Only to pull the same shit again in 2016. PS: And yes, FTDI did say they saw the error of their ways back in 2014. I am hoping, but not holding my breath for either. I also hope that Prolific will see the error of their ways and stop bricking customer devices. I hope that Microsoft will rollback driver since it's their update that's causing issues for the customer. Their product is nothing special and there are many other manufacturers happy to take my money. Unless something changes, I won't buy a single Prolific cable ever again. Since I cannot verify their authenticity myself, buying any Prolific device is something that might bite me in the ass. What I do know is that Prolific is ready to play shenanigans with Microsoft update and brick my devices down the road. Why? Because there is no way that I, as a customer, can check if device is indeed original or not. I am never going to knowingly buy a Prolific device again. 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. The only person not out of money is probably the guy selling fakes in the first place. Manufacturer might be out of money (especially if they didn't know they're dealing with fakes). If I can ask for refund, the seller might be out of money.
![prolific pl2303 windows 10 driver error prolific pl2303 windows 10 driver error](https://i.ytimg.com/vi/kjtAU-kigD0/maxresdefault.jpg)
Money is long gone and so is the supplier of the fake chips. I paid the seller, he paid his supplied, his supplied paid the manufacturer and so on.
![prolific pl2303 windows 10 driver error prolific pl2303 windows 10 driver error](https://obd2-elm327.es/fotos/trucos/prolific2303-windows10/pl2303-error-windows10.png)
I bought device without knowing it has a fake chip in it. For me the concept of bricking device owned by an unsuspected user is a bridge too far. However, their beef should be with fake chip suppliers and not with the end customer. And I can see how they might be annoyed with fake chips using their drivers. Now, you might thing this is their right. PLEASE CONTACT YOUR SUPPLIER." Yes, it's the exact nonsense that FTDI pulled years ago - using Microsoft Windows Update mechanism for their authenticity enforcement. While the serial port did appear, I couldn't open it or send any data.Ī quick trip to Device Manager has shown a problem: " THIS IS NOT PROLIFIC PL2303. A few days ago I needed USB type-A serial device to do a quick loopback test and grabber the same, previously working, device. After finding a suitable device, I did what was needed and forgot about it for a while.
![prolific pl2303 windows 10 driver error prolific pl2303 windows 10 driver error](https://i.pinimg.com/originals/9e/1f/8d/9e1f8d7b4f718b3ed09a5df41a513754.jpg)
Story starts with me searching for 5V USB cable with a 3.3V signal. Yes, it's again time for a chip manufacturer to mess with your computer drivers.
![prolific pl2303 windows 10 driver error prolific pl2303 windows 10 driver error](https://www.avoiderrors.com/wp-content/uploads/2023/03/Download-and-Install-PL2303-Driver-for-Windows-11.jpg)
Well, it's been a while since the FTDI fuckup so I guess it was a time for another IC supplier to go bonkers.