Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
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.