Reply to thread

Message

<blockquote data-quote="ForgottenSeer 95367" data-source="post: 998551">Microsoft Security is already aware and has been regarding this infection mechanism for years. The reason(s) they have not fixed it is known only to them, but a storyline that Microsoft is screwing over users deliberately or otherwise makes for great clickbait.How often does the home user execute .cpl or .msi files? Microsoft cares primarily about enterprise, and with wsus and manual Windows updates via SCCM and other methods rampant in enterprise, Microsoft is not about to do something that interferes with .msi (or .msp) file installs, even if that means some infections are going to happen. Perhaps the fact that enterprise can block .msi via Group Policy or other methods is good enough for Microsoft. People forget that Microsoft develops Windows as a one-fits-all-image where considerations for enterprise always take top priority. There could be some other off-the-wall reason Microsoft won&#039;t do anything about it after all these years. So unless someone at Microsoft steps forward and gives the reason(s) for its inactions, then it is guesswork.</blockquote>

[QUOTE="ForgottenSeer 95367, post: 998551"] Microsoft Security is already aware and has been regarding this infection mechanism for years. The reason(s) they have not fixed it is known only to them, but a storyline that Microsoft is screwing over users deliberately or otherwise makes for great clickbait. How often does the home user execute .cpl or .msi files? Microsoft cares primarily about enterprise, and with wsus and manual Windows updates via SCCM and other methods rampant in enterprise, Microsoft is not about to do something that interferes with .msi (or .msp) file installs, even if that means some infections are going to happen. Perhaps the fact that enterprise can block .msi via Group Policy or other methods is good enough for Microsoft. People forget that Microsoft develops Windows as a one-fits-all-image where considerations for enterprise always take top priority. There could be some other off-the-wall reason Microsoft won't do anything about it after all these years. So unless someone at Microsoft steps forward and gives the reason(s) for its inactions, then it is guesswork. [/QUOTE]

Verification