New
#31
I was also hit by that "Bad DB update" on one of my systems that caused problems.
MBAM did acknowledge and fix it quickly (imho), less than 1 hour as I remember.
I think that last FP Bad DB Update caused so many problems, they put new procedures in place to prevent further problems like that.
I haven't seen a "Bad DB Update" like that one, since then ...
IMHO, something like this can happen with ANY AV or AM update.
It made me re-think, to back off my scheduled checks for the latest definitions so often ...
If I check every two hours instead of every hour, I have less chance of getting a bad update, that is corrected within the hour ...