Comment by solarkraft
1 day ago
I am saying that people here seem to be appealing to Microsoft as an authority that should be interested in stopping this, perhaps because they are morally superior or concerned about their reputation. They are not.
1 day ago
I am saying that people here seem to be appealing to Microsoft as an authority that should be interested in stopping this, perhaps because they are morally superior or concerned about their reputation. They are not.
No, Microsoft inflicted this upon themselves. They introduced driver vetoing long ago specifically for this purpose (at the cost of certain amount of user freedom), and have established the criteria for it, but barely ever enforce most of these criteria that aren't related to hard OS stability (and sometimes even those that are related), because that might upset the vendors.
No, Microsoft should be stopping this because Microsoft is doing it, and it is wrong. HDMI does not, to my knowledge, provide a mechanism for loading code: it's Microsoft software looking the product model up in a Microsoft database, downloading the appropriate malware, and executing it with elevated privileges (bypassing UAC).