According to a post from June 2015, [https://community.f-secure.com/t5/F-Secure-SAFE/Compatibility-of-Malwarebytes/td-p/69987], MalwareBytes [MWB] and F-Secure got along like the proverbial "two peas in a pod"
I'm guessing that is no longer the case? Currently, as I can see from other postings in the F-Secure forum, this may no longer be the case.
My installation of the current MWB program keeps indicating "cannot connect to update server!" Is it because it is conflicting with F-Secure? I haven't a clue. All I know is I have spent many hours recently trying to figure out why my installation of MWB is no longer working.
Sorry for my reply. Most likely you want to get official response from F-Secure (and it will be good indeed) or from other experienced users; And not just my suggestions.
But I just want to say that I tried (previously) to find something as list of "Software which compatible with F-Secure" - but such list was missing (or I did not find it); And there I mean official list from F-Secure (or under their official articles: website/knowledgebase/how-to/faq/notes or other); As their own view.
Except points that at installation (F-Secure solutions) there should be sidegrade-check and information if installed (detected) some not-compatible software; So - if there missing notification --> or there all good with other software installed under user's system; or sidegrade not work properly; or such software installed later;
But based on user's experience there was information that MBAM/F-Secure normally work together;
And usually official position of F-Secure was something like next:
Which also mostly like recommendation (than strong rule);
With my experience about MBAM and F-Secure - it was not really "quite good" already many years (and before large changes with MWB and not about all of their tools) - with all meanings (system impact, Malwarebytes impact; and F-Secure impact - but not directly);
So, I mean that answer for your ask maybe should be based on next meanings:
--> Does Malwarebytes still listed F-Secure under their compatibility list (if they have this one) or marked their software as compatible with other security software (including F-Secure)?
But basically - did you try to exclude all Malwarebytes folders (as first try) under F-Secure?
It possible by using "Main UI" and Real-time scanning Exclusion list;
Maybe this Knowledgebase/How-to can be helpful with this:
If there will be placed Malwarebytes folder (as result - their files) it should potentially excluded processes (by this files/used by this files) - because maybe troublepoints there with F-Secure scanning/analysing all suspicious (or not common) activities under system (maybe there delay and Malwarebytes goes be with mistake); I not read under community (with related topics Malwarebytes/F-Secure) if such steps helpful/useful or not;
Also based on your reply under another topic:
Also if there trouble with updating databases; Maybe there just "Malwarebytes servers" in somewhat reasons blocked (as suspicious/malicious-rated randomly; or if used restricted-content under F-Secure); Do you use Home solution of F-Secure? If yes - maybe you able to try re-check situation - does it will be helpful with updating Malwarebytes databases - when F-Secure disabled temporary (it should be possible from Main UI -> Tools -> Turn off all security features);
Sorry for my long reply.
I can't add any more to what I already said in the other thread. If you check the Malwarebytes forums, you will see that there are lots and lots of problems with the latest version, therefore as soon as they withdraw support for the 2.2 version, I will be uninstalling it.
Thank you for your reply. I have submitted a support ticket to MWB and am in the process of trying their different possible fixes. I will post here what I find out.
Spending hour upon hour sifting through a gigantic database [i.e., forums and "knowledge bases"] looking for a solution to my issue isn't my cup of tea, so if I can't find a solution to an issue after an hour or so, I give up and contact the support folks who may not like that but if it weren't for users like me they wouldn't have a job. The more complicated technology gets the more it will leave us old folks behind.
It would be interesting to hear what they come up with, so please feed back to us here. I suspect, however, that their solutions will involve disabling or modifying certain settings on the product which is not MWB, which compromises the security of the primary product, in this case, F-Secure, in order to get MWB to work.
I have been busy with other computer related items and totally spaced out posting a reply regarding the issue I was experiencing with the compatibility between MWB and F-Secure...! I never heard back from F-Secure, but I did get a reply and fix from MWB...
Basically, MWB sent me an email indicating which files need to be placed in the F-Secure "exclude" settings along with some other settings... After I completed all that MWB is now working side-by-side with F-Secure...!!
As soon as I fix the issue that popped up this morning with my Office 365 Outlook program I can email you the fix MWB sent me...
I'm very late to the party, but I agree with Simon. MBAM used to be a great product, but 3.0 is no longer usable with F-Secure, not to mention that it can only be uninstalled in Safe Mode, with or without their uninstallation tool. I was advised to disable a part of F-Secure, which I won't do. Another annoyance was that every few weeks, MBAM would stop protecting, sometimes forcing me to uninstall and reinstall, though this actually started with 2.x. In my opinion, when they enhanced it to serve as a stand-along anti-virus product, they made it incompatible with some anti-virus products, which makes sense when you think about it.
MWB sent me a list of files to include in the exclusion list. Once I added them to the exclusion list - on three computers - MWB works without getting the error message about not being able to connect to the update server.
MWB has been a good program inspite of this "glitch" in updating to the latest version.
Here is the list of files - the one for the 64-bit only, should be changed to: \mbae32.sys.
C:\Windows\System32\drivers\mbae64.sys (64-bit only)
Best of luck to you all...
Thanks for the update, and for the information. I still maintain, however, that if MWB are claiming their software is compatible with other AV products, steps like this shouldn't be necessary.