Concretesalad

I am seeing the same thing on a few machines this morning, as well.

No rollbacks as the update overwrites. Maybe MB can change that and archive the last 10-20 updates on our local builds so we can rollback in scenarios like this.

Why can't you repackage previous WORKING update and redistribute?

Actually, something similar to this happened a month or so ago. And when things like this happen that take people away from their actual lives as well as disrupt workflow, there is a good reason for frustration. I am supposed to be at a wedding right now, and... I'm not there.

OK... I am supposed to be at my daughters wedding. Instead, I am here at work dealing with another MB false positive fiasco. As head of IT I cannot just blithely assume that this IS a false positive, even though that is more than likely what it is. Is there any reason why the previous update cannot be repackaged and sent out as a later rev until MB staff can figure out who scheduled the pooch screw?