New detection engine that
Improves Zero-hour detection
Dynamically extends detection to mutating malware
Improved performance and faster scans
Complete redesign of the User Interface
Simplification of the Windows Security Center integration setting
Improved Web Protection component
Hi Asyn,
Well not totally sure, maybe a bit. Mbam has traditionally been a IMO ‘a bit’ higher on resources than some products, however with today’s machines and ample RAM I’ve never considered that to be an issue for the protection given.
The Threat Scan seems a little longer however from my understanding is more thorough than version V3.
I’ve read where some users or should I say past users have commented on resource use but I have not seen that to be the case in any real negative way. At least not on my systems.
Having said that, with weaker CPU and low RAM I could see that observation as valid.
Certainly wouldn’t run smoothly on my XP
OK, tbh, I’m not overly impressed. Slow scanning and still quite heavy on resources - I like the UI, though.
Personally, I’ll stick with EEK as second opinion scanner - it doesn’t need/use any resources at all (until run).
PS: Just to be fair, as this is an early beta, I’ll probably give the final version another try (once released).
A general rule for abbreviations would be not to abbreviate the first use and follow it with the abbreviation (EEE), etc. If you are only using it once no need to abbreviate it.
My reason for not depending on that second opinion and only running it very infrequently.
The good thing about EEK is that it’s a portable program and uses no resources unless you actually run it.
Thanks Asyn
Well all things being equal I guess you are right.
For me, I have plenty of resource with Ram and CPU that I don’t notice any lag or delay or heaviness on the Machine running Mbam