PL2303 serial adapters

Jun 16, 2016 31 Replies

It's nothing to do with MS or W10. It's all to do with Prolific. Prolific no longer support the 2303. Existing drivers still work. On W10 you get the new driver by default which doesn't support the 2303 but does support the newer hardware. If you uninstall and install a older driver then that driver will get replaced by the latest driver during the next Windows Update.

It's Prolific's decision not to support their old devices (and counterfeits) on W10. If you have a beef, then take it up with Prolific.

I'm sure you can spin the fact that all sorts of bottom feeders in China were ripping off Prolific (and FTDI) by counterfeiting the devices and both company's reactions to this as MS's fault. Go on, you know you want to!

Actually, you couldn't be more wrong. I was quite unaware of this.

W J G

Not on the W10 Home editions. I think you can do more on W10 Pro but for effective management you need the Enterprise version. Enterprise is the version business should use as updates et al. are controlled by group policy.

I only found this out when doing a check for a customer. It's not a big issue for me as I can bill them for some new USB dongles.

The mandatory updates etc. is sort of crazy. The most annoying things is having to specify connections as metered so updates are not download over things like 4g/LTE connections.

On Sat, 18 Jun 2016 18:05:31 +0100, mm0fmf declaimed the following:

And then there is the threat of their "refresh W10"

formatting link

Which has the potential to wipe out any third-party applications (I understand it will even wipe out M$ Office installs)... If one accidentally lets it run one could be facing days or weeks of re-installing all one's needed applications (some of which had nasty install requirements to begin with... ever look at the devil's contract one has to fill out to get TI CCS6?). I'd have to reinstall IDEs for Sardine, TIVA [CCS], Visual Studio Express, BASIC Stamp, Propeller, MPLab... And that doesn't even cover the non-programming applications.

Wulfraed Dennis Lee Bieber AF6VN wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/

If you accidently do the wrong thing there's normally a consequence.

Yeh. You can blame that on Microsoft. Apparently on W10 you cannot opt out of updating drivers anymore. Or something like that.

That's all part of the new forced upgrade philosophy. It's not just the prolific stuff.

Rob.

I demand that Dennis Lee Bieber may or may not have written...

[snip]

formatting link

It's not entirely effective: it leaves Windows itself behind...

| _ | Darren Salt, using Debian GNU/Linux (and Android) | ( ) | | X | ASCII Ribbon campaign against HTML e-mail | / \ | You are in a maze of little twisting passages, all different.

I demand that Rob Doyle may or may not have written...

[snip; W10 updates]

I misread that as 'forced upgrade hostility'. Make of that what you will! ?

| _ | Darren Salt, using Debian GNU/Linux (and Android) | ( ) | | X | ASCII Ribbon campaign against HTML e-mail | / \ | "He taught us drawing, stretching, and fainting in coils."

Oi! Pack that in. I was just having my late night drinking chocolate :o

W J G

The reason is prefectly clear: The hardware of yesteryear is good enough to keep the users happy. There must be a mechanism to force them to buy new hardware, and escalate it to upgrading the whole shop.

-TV

There is a package here

formatting link

That forces the install of an old driver that works with older devices and sets a policy to stop it being force updated. Seems to work for me for some genuine older devices on W10.

Seems a bit high handed to block genuine older devices to spite the cloners. Some of these older devices could well be installed in

HTH

Chris K

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required