Well, the thing is, this little mistake is not the root of the problem (I think). The problem is there is no fail safe what so ever. This 'little' mistake proofs (in my eyes) that the way MB is setup is faulty. How can a little mistake in a protection update result in:
- crashed pc's
- loss of data (in my case loss of all unsaved data)
- corrupted data (in my case veracrypt volumes were affected)
- loss of time (took me an hour to figure it out and not to mention the time I have to spend to re-do all the work I lost)
And not to mention the fact that this affected all MB users, most of them with no IT skills what so ever. They will see their pc crash and reboot every couple of minutes and have no idea what the hell is going on. The fact that such a 'little' mistake can have these kind of results makes me think twice about trusting this program ever again. Mistakes are made everywhere, not one program is 100% safe, but I have never ever seen such a little mistake turn into such a disaster (which I think is fair to call it that considering all the thing mentioned above).
Doesn't matter how soon they identified, reported and 'fixed' it. Fact is: it happened. And what will happen when they make the same mistake or an even bigger one?