That's not the case here. Updates going back as far as what, March?, with no indication that the update included this, were involved here. What I'm saying is

That's not the case here. Updates going back as far as what, March?, with no indication that the update included this, were involved here. What I'm saying is that whether you, or an automated update process are performing the update... You still are susceptible. Unless, as I said, your idea is to block updates completely, which is... not really viable. What should these companies have done better for the update side? Sure, there were other controls that could have limited the effectiveness of this once the update was in place, but I'm not seeing anything that would block the update itself.