Your feedback is neither helpful nor productive. Allow me to shed some light on this.
Software development is a highly complex process. Imagine you are responsible for deploying a product written by hundreds of developers, comprising millions of lines of code, to hundreds of thousands of machines, all of which have a different set of group policies, permission levels, authentication schemes, domains, languages, themes, and run different versions and editions of Windows. Imagine that your users have chosen which Windows Updates to install and ignore and that you have to account for each combination. Imagine your product relies on many third-party components you did not write, such as dozens of Python packages, thousands of .NET components, several command shell extensions, and a near infinite number of display drivers, printer drivers, plus web protocols, security standards, and on top of that, uses shared DLLs used by other programs. Would you feel confident that you could test every possibility, and in such a short time as to notify your users of a possible problem?
Esri does a great job managing all that they can, but sending out an email to ALL of their customers to warn them NOT to install a security patch from Microsoft does not sound like a best practice to me. Many professionals don't even have control of this aspect, as it's managed by IT departments, security officers, and/or anti-virus software.
Faulting a developer these days is cowardly and ignorant of the many obstacles they face. They rely on users like you and me to report the problem, the conditions and actions which led to it, so that they can replicate it, and develop a fix as soon as possible.
