Here is an example of handling a situation better:
Cisco put out a bad Firepower patch bundle (6.2.3.8) on Jan 2, 2019 that causes Firepower to stop processing traffic after it has been up for a few hours if a specific protection (HTTP file inspection) is enabled.
By Jan 8, 2019, patch 6.2.3.8 was recalled, a bug report was published with specifics of the problem, how to identify it happening, and two workarounds (disable HTTP file inspection, or roll back to the previous update).
On Jan 9, 2019, there were Reddit discussions talking about the issue and referencing the bug report: https://www.reddit.com/r/networking/comments/aeb4gx/dont_install_cisco_ftd_6238_p1_file_policy_bug/
On Jan 10, 2019, patch 6.2.3.9 was released with the fix.
On Jan 14, 2019, a proactive notification went out to anyone who had downloaded 6.2.3.8 advising them of the defect:
While this notice wouldn't necessarily go to everyone impacted - only the person who downloaded the code would receive it, and that person might not even work for the affected customer - word of the defect spread quickly among people who needed to know about it.
This was for a "Severity: 1 Catastrophic" problem affecting a small portion of the userbase.
MBAM's customer base is different and communication techniques must necessarily be different, but the key difference here is ownership of the problem and a timely effort at customer notification. In Cisco's case, no automatic update would have pushed 6.2.3.8, so admins were generally aware that they applied an update and afterwards there were problems - which is what makes the problematic MBAM 1.0.508 automatic update so insidious. One day things are working, and the next day they aren't.
Nothing on the affected machines even remotely hinted at an MBAM update being the problem. Only trial and error troubleshooting, or some lucky google searches, pointed most of us to this forum.
If you want to erode trust in your product by your userbase, this was a great way to do it. Many of us are influencers - people who convince our customers, colleagues, relatives, and friends to buy your software. Consider how many are reevaluating this decision. It's not a good look.