7 replies to this topic

[Buddel]

Dear all,

Are there any known conflicts between Kaspersky Internet Suite (KIS 9) and MBAM (real-time protection enabled)? Thanks a lot for your replies in advance.

Best regards,
Buddel

[exile360]

Greetings Buddel .

Nope, no known conflicts between them, perhaps with one minor exception, occasionally when a new version of MBAM is downloaded via the built in updater (a new version of MBAM, not just definitions), Kaspersky often detects it as a trojan because of it's heuristics. KL has been notified by many users about the issue, but unless they completely rewrite the code for their heuristic detection engine there isn't much that can be done, so in these cases, just tell Kaspersky to ignore the detection.

[Buddel]

Thanks a lot for your detailed reply. OK, I will tell Kaspersky to leave MBAM alone, so there shouldn't be any conflicts.

[exile360]

Yup, their realtime modules play very nicely, like I said, it's just when a new verision is downloaded automatically for installation (and saved to a temp location by MBAM's updater) that KIS freaks out. Someday they might (hopefully) whitelist it somehow so it doesn't get detected any more.

[Buddel]

I really hope adding MBAM to the KIS ignore list will help. I'm new to KIS, so it will probably take some time to find out how to tell Kaspersky to leave MBAM alone (if it is possible).

[exile360]

Well, adding your other security programs (like MBAM) to Kaspersky's trusted list will certainly help ensure you won't see any conflicts, but that detection thing I've been referring to is a completely seperate issue. It doesn't detect it as part of MBAM (because technically it's not), it just detects the installer, for example, the current version of MBAM is 1.35, so lets say you're using your computer one day and 1.36 gets released. MBAM will automatically download the new version (1.36) using it's autoupdater and save the installer for 1.36 to a temporary location so it can install it and then just delete the installer when it's done. Once the updater downloads the installer, Kaspersky immediately detects the installer as containing a trojan (I believe it's because of how the installer has to work, needing to start a service on reboot for the realtime protection to be active). All you have to do is tell KIS to ignore it and add it to exclusions and you'll be good (until 1.37 is released of course ).

[Buddel]

Now I understand. Again, thanks very much for your help. Much appreciated (as always).

[exile360]

You're very welcome . You should have a very well protected system between MBAM and KIS.