I worked for 12 years for Microsoft in Technical Support. I often had occasion to work with the Legal Department. Your objection to Microsoft's attitude, while understandable, is a result of very strict contractual requirements. Simply put, Microsoft agrees to treat drivers as black boxes. If the driver had actual malfunctions, Technical Support would work with the vendor to fix the problem, but Prolifics chips aren't the first pirated hardware, and Microsoft has a strict hands-off policy on how vendors handle pirated hardware. Case #1 is clearly under the purview of the driver vendor, and @2 is a malfunction. As for Microsoft Support's attitude about who provides support, this is a combination of contracts and law.
=========================================================== Richard Van Fossan [email protected] (253) 230-2525 On Fri, Jul 4, 2025 at 1:18 PM Ceferino Lamb via Users < [email protected]> wrote: > My solution fixes all of that. I edited my registry to turn off all > automatic updates forever, also the system services which try to > restart auto updates. All my updates are manual. I prefer W10 sp1903 > or 1908. Yes a new exploit might get thru, but I run both firewall and > MalwareBytes, paid versions. > > When my workaround is no longer viable as in sunset of W10, I'm going > to linux with a Windows emulator. > > Tired of all the BS from MS, for decades now ... now they try to run > native AI that scans your screen and all keystrokes/mouse to "help" > you. > > On Tue, Jun 24, 2025 at 9:42 PM Terri Kennedy via Users > <[email protected]> wrote: > > > > Ken Hansen <[email protected]> wrote: > > > > > You realize the issue here is that criminals stole the design of > > > Prolific chips and sold copies, then the vendor coded their 'official' > > > driver to detect and refuse to work with the illegal copied chips, and > > > Microsoft, as a corporate policy, works to keep installed official > > > drivers up-to-date, right? > > > > > > This is a perfectly logical action by Microsoft, and any deviation > > > from running the most current official driver would be an > > > accommodation to support illegal copies of Prolific chips. > > > > [I apologize for turning this into a meta-discussion mostly unrelated > > to CHIRP, but feel that some facts need to be cleared up.] > > > > As I understand it, there are 2 issues here: > > > > 1) There are some fake chips which newer drives refuse to work with. > > > > 2) There are some legitimate Prolific parts that for some unknown > > reason, Prolific doesn't want to support on Windows 11. > > > > Case #2 is obviously not the user's fault. I'd argue that case #1 is > > also not the user's fault, unless the item they bought was described > > as "cable with fake Prolific chip". > > > > Punishing the end user for either seems unfair. Canon tried pulling > > trick #2 with their LiDE scanners, and VueScan showed that this was > > just a money grab by Canon (to sell entire new scanners users didn't > > need), and it provides its own scanner driver that is perfectly happy > > running those old scanners on new Windows versions. > > > > Microsoft just takes whatever drivers a hardware manufacturer pro- > > vides and bundles them into the monthly update. This has led to many > > problems in the past and will continue into the future, as they can > > just say "Go talk to the company that wrote the driver - you didn't > > by Windows directly from us, so you don't get any support from us". > > Besides, they're busy enough fixing their own bugs that break systems > > when updated. > > > > I also find it amusing that people are holding FTDI up as some ex- > > ample of a great company that doesn't do this - I guess the fact that > > FTDI intentionally bricked fake FTDI chips instead of just refusing > > to support them has faded from memory. Here's a refresher: > > > https://www.zdnet.com/article/ftdi-admits-to-bricking-innocent-users-chips-in-silent-update > > _______________________________________________ > > Users mailing list > > [email protected] > > > https://lists.chirpmyradio.com/postorius/lists/users.lists.chirpmyradio.com > > To unsubscribe, send an email to [email protected] > > To report this email as off-topic, please email > [email protected] > > List archives: > https://lists.chirpmyradio.com/hyperkitty/list/[email protected]/ > > > > -- > //CRL > Quis custodiet ipsos custodes? > _______________________________________________ > Users mailing list > [email protected] > https://lists.chirpmyradio.com/postorius/lists/users.lists.chirpmyradio.com > To unsubscribe, send an email to [email protected] > To report this email as off-topic, please email > [email protected] > List archives: > https://lists.chirpmyradio.com/hyperkitty/list/[email protected]/ _______________________________________________ Users mailing list [email protected] https://lists.chirpmyradio.com/postorius/lists/users.lists.chirpmyradio.com To unsubscribe, send an email to [email protected] To report this email as off-topic, please email [email protected] List archives: https://lists.chirpmyradio.com/hyperkitty/list/[email protected]/
