Well, it's been a while since the FTDI fuckup so I guess it was a time for another IC supplier to go bonkers. Yes, it's again time for a chip manufacturer to mess with your computer drivers.
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.
PS: And yes, FTDI did say they saw the error of their ways back in 2014. Only to pull the same shit again in 2016. They learned nothing. Chances are neither will Prolific.
PPS: In meantime, you can download the older driver (v3.8.39.0 worked for me) and use it instead.
Alternatively, use a supply chain that doens’t play silly buggers with their drivers. Perhaps an OS that has available source to stop this kind of primative behavior. Linux ?
Erm, if you can go backward to an earlier driver, your chip isn’t “bricked”.
It’s pretty crappy of you to accuse Prolific of deliberately “bricking” chips when this could simply be a normal driver change that clones aren’t compatible with.
Are you really suggesting that Prolific should qualify their drivers against clones?
>Are you really suggesting that Prolific should qualify their drivers against clones?
do you smoke crack? where do you see this!
Prolific shill or social media intern detected
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?
And no, words “THIS IS NOT PROLIFIC PL2303. PLEASE CONTACT YOUR SUPPLIER” haven’t been added due to a normal driver change that clones aren’t compatible with. It was pure business decision.
I agree that Prolific cannot be expected to maintain drivers for their clones. But this change breaks stuff of the customer, not the clone manufacturer. By the time clone arrives into the hands of the customer, clone manufacturers got their money.
I agree with Anonymous, this isn’t “bricking”, this is “removing support for unknown chips”. A bit heavy handed, I agree. It would be better with big disclaimer and best effort to make it keep working. But who knows – perhaps this release did a lot of rewrites and refactoring so keeping the old code to support the clones was a big burden.
Hey, yes. It’s hillarious – I mean you happily buy a “good” product using a chip that you trust and got scammed.
So what’s the result? not buying it? having a dedicated trash can for sturdy, well working adapters so you never by mistake re-use them after finding you had a fake?
yesterday I appararently had grabbed an old one or another that turned out to be a fake (and i already buy them from more expensive brands to avoid that). It worked fine on my macbook while I worked.
Plugged it into the remote access box there so it’ll be ready for the next use.
Result? an inaccessible switch in a server rack in a basement of a museum on a mountaintop 100s of kilometers away. using the serial adapter instead of the built-in console for versatility? no, waste of money.
so can’t trust any prolific chip based product, will go get some high-end Moxa thing and it’ll serve noone at all.
The energy and waste is in that case really a product of the vendor and so the chip vendor ends up on the blacklist.