I use MBAM weekly to check my system and when i hit update it finishes successfuly and says updated version 390 to 396 Update size is 33xx mb for example, then i check update the next day it says updated version 396 to 397 with the same size of update. It should be smaller than the previous update?? I can’t understand why this happens please can anybody explain this to me ?
I see my last update is 3275 and the current update is 3284 and as the definition file is small the whole file is refreshed so that old definitions are removed reducing false positives.
Small is a relative value, when on dial-up 3mb + on every update is a pain in the a**e.
About the same as only being shot in the head will a small .223 calibre bullet as opposed to .44 magnum bullet.
If avast can implement incremental updates whilst removing/correcting false positives and retaining database integrity, surely it can’t be beyond the collective wit of malwarebytes. Another pain in the rear is SAS which pull virtually the same stroke of huge updates, for what is essentially a small number of new signatures.
MBAM (and I think SAS works the same way) definitely updates by re-installing the entire malware database, updated version. Like many others, I’d be delighted if either or both products could someday come up with incremental updates like avast’s. I’d also like to see them clean up after themselves, since (on my system, at least) running Disk Cleanup after the updates shows they’ve left a total of 7+ megs behind in temp internet files.
I’ve got the free versions of both products (no resident protection), so don’t bother to update except just once a week shortly before scanning. What the heck, under the circumstances such updates will be at least roughly the same size as each daily update.
You’re welcome, now you know what you see is ‘normal’ but not in my option not ideal, I guess I’m spoilt with avast’s incremental updates being so ‘small’ ;D