replicant

Porthos, thanks for that. I should've been more explicit in my post. You are right about SMB's and the business version.

Acting as a counterbalance here, I'm a Premium subscriber and am happy that MB added more features in 3.x. I too have recommended MBAM to my clients, who typically are not power users, so the more protection, the better. Thanks for improving an already great product. Also, the fact that I no longer have to pitch/install a separate AV is terrific. That makes things less cumbersome for me, and more cost-effective for the small businesses that I work with (which is music to an SMB owner who thinks the "free" is the right price for software). That said, the OP makes a valid point; adding new features should also come with an easy way to disable/enable them. Am happy that MB is taking care of that as well.

I am running MBAM 3.0.6.1469, and this morning, updated to Avast! Anti-virus version 17.1.2286 (build 17.1.3394.30). Updating Avast! seems to have done the trick, because after restarting, MBAM loaded properly, as expected. Then Avast! came up, also working fine. It appears that if MBAM starts before the AV, things are ok. If, like me, you're running MBAM with Avast! side-by-side, you may wish to see if the latest update of the AV product helps. I notice that in their new release, there's an option to have the AV services not start until other system services have started. I don't have that option enabled, but it may be worth looking at that as well. By the way, I also have the MBAM program path added to the Avast! list of exclusions. Good luck, replicant