Good on them, I guess.
This kind of thing can never be removed from Windows because somewhere there is a Fortune 500 company whose entire IT infrastructure is precariously balanced such that it relies on this obscure feature â or some other equally rickety legacy Win32/16 API crap â and if it ever goes away their business will collapse and theyâll sue Microsoft for a billion dollars.
Those systems are running frozen versions of Windows, theyâre not being updated. Microsoft could introduce a patch for Windows 10 and 11 that removes the vulnerability and people running old software on XP would still be able to run it. Or, at the very least, make it disabled by default but let advanced users and sysadmins re-enable the vulnerable code.
Thatâs what they did with SMB 1.0, for instance. Itâs disabled on any modern Windows install, even though a lot of universities and companies still have infrastructure based on it. If you browse the âadvanced system featuresâ options you can re-enable it manually, with the knowledge that youâre voluntarily opening up your system to well known dangerous exploits in exchange for backwards compatibility.
EDIT: So further reading thatâs exactly what theyâre doing. The drivers arenât loaded by default on Windows 10 and 11, they need to be enabled after plugging a legacy device type requiring it.
What are you talking about? Microsoft constatntly removes and adds features to their software and OS, no one can sue them for it.
Yeah, windows 10/11 has broken a ton of stuff. I have to use RS232 plugs for programming controllers at work, and I had to buy new usb-RS232 cables for all our computers because windows 11 broke support for all the older cables. Iâve also had a lot of programs break.
Itâs really frustrating to be trying to troubleshoot if an old controller is working or not, and not know if you canât connect to it because itâs fried or if some new windows update is preventing the connection/software from working.
Those cables more than likely were using clone chips and for whatever reason Microsoft decided to back completely banning them when identified.
Youâll probably know if your old one is a fake chip because itâll say ânot a prolificâŚâ which isnât just a reboot and edit to allow unsigned drivers, itâs dead.
Whatâs worse, itâs absolutely impossible to tell if the cable you bought has the fake chip since legitimate stores and legitimate cable makers bought them so the loser is people.
Works fine on Mac and Linux though. Naturally.