What *is* ridiculous is not being given sufficient timely notice in order to be able to do so. It is not unreasonable that one might have to do this before installing a major version update to one's security suite. It's not just the "kinks" - it's the fact that NOT knowing when the version update is coming doesn't allow the user to take the usual proactive steps to avoid potential conflicts and errors (such as disabling or uninstalling other security apps). If it doesn't go smoothly, I will likely jump ship to a competitor that provides more of the features & configurability options that have been progressively stripped from McAfee. So I assume I will end up with a mess when this happens (crashes, hangups, errors, conflicts and even BSOD) until I *uninstall/cleanup* EVERYTHING (McAfee, MBAM, SAS, WinPatrol) and perform a clean installation from scratch.Īs such, I'm really not looking forward to it. I will have no way to know when it arrives until I am prompted for a reboot AFTER installation.īy that point in the process, it will be too late to perform proactive steps. I don't know what will happen when/if I receive the 2010 updates. OTOH, I am (thankfully) still running the OEM "2009" "Dell" versions of the McAfee Security Center. And the new, paid version allows users to program "flash" scans which run every time the definitions update, typically several times daily (as opposed to only once daily updates with McAfee). Moreover, the real-time IP protection from MBAM is a welcome addition to the McAfee firewall - it has blocked many malicious IPs, thereby possibly preventing infections, and allowing me to manually add those ranges to the "banned IPs" in the McAfee FW. With some, one needs to do a little tweaking of one's firewall settings to be sure the MBAM files are excluded/allowed.īut I haven't had any problems with that on the McAfee systems (Webroot on my laptop has been a little dicier). MBAM is *not* an anti-virus and is designed to work alongside the major suites/firewalls/AVs. (With XP, one has to make a minor registry tweak, OR disable the MBAM load at startup, OR use WinPatrol to set MBAM for a delayed start.) ![]() With Vista and Win7, MBAM automatically loads a minute or 2 after Windows starts, by which time McAfee is loaded and running. 1.46 I thought I would try it - it works fine. However, with the latest MBAM update to v. I've been running MBAM Pro on all 3 systems (2 of which run "2009" McAfee) since January.Īs a "precaution" against startup conflicts, I had been disabling MBAM's active protection start at boot-up (opting instead to manually start the service a minute or 2 later).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |