MB3 and F-Secure [2 questions]

[RayStA]

MB3 is not compatible with F-Secure except when using F-Secure in compatibility mode (reduces security!).

[Windows 10 Home 64-bit; MB3 Premium; F-Secure SAFE; all fully updated ]

 

The most secure option would be F-Secure without compatibility mode + re-install MB3 at every boot but I am reluctant to take that route unless necessary.

 

Which of the following options would give the most overall security?
1. MB3 + F-Secure in compatibility mode OR
2. MBAM2 + MBAE + F-Secure without using compatibility mode

I still have two more machines running The latter option and would appreciate advice.

 

Is there an MB3 update to correct the F-Secure problem in prospect?

[Guest]

My opinion:

Option #2.

But if the support for MBAM2 will be closed on June, 8th, as already announced by MB, and the compatibility issue between MB3 and F-SecureI will not be solved I would chose a third option:

Deletion and abandoning of MB3.

I would have more confidence to a very well proved AV than to an at time still very buggy "replacement" of an AV.

If there ever will be an insoluble issue between my Norton Internet Security (NIS) and MB3, I will will stick to NIS most certainly.

There's even an option #4:

Use of your AV together with another, to your Av comptible anti-maleware software, for example Emisoft.

 

Addition: Sorry for the pretty harsh words above, but my reply is also a suggestion to MB to knuckle down for a well running, bug-free MB3 and for stopping to use so many customers as unvoluntary guinea pigs to test their "replacement" of an AV. 

:

 

Edited February 23, 2017 by GMork

[Aura]

Quote

There's even an option #4:

Use of your AV together with another, to your Av comptible anti-maleware software, for example Emisoft.

Emsisoft Anti-Malware is an Antivirus, and like any other Antivirus, it shouldn't run side by side with another one.

Quote

Is there an MB3 update to correct the F-Secure problem in prospect?

Since it is a known and reported issue, I'm sure Malwarebytes is working on it. Though the issue could be on F-Secure's side, since it's their program that stops Malwarebytes 3.0 from working.

[Telos]

5 hours ago, RayStA said:

MB3 is not compatible with F-Secure except when using F-Secure in compatibility mode (reduces security!).

 

Is there an MB3 update to correct the F-Secure problem in prospect?

There is an alternate workaround that doesn't fully cripple DeepGuard:

Also... please report this MBAM issue to F-Secure as a False Positive

https://www.f-secure.com/en/web/labs_global/submit-a-sample

Edited February 23, 2017 by Telos

[RayStA]

Prompted by a previous post I was preparing a message to F-Secure as follows:

"After each reboot Malwarebytes 3 fails to start. 
"The message is "Unable to start. Unable to connect the service."
"If the program is reinstalled Malwarebytes is perfectly happy - until the next reboot - so it is not mbam.exe that is the problem."

To ensure that I had the 'fails to start' message correct I unticked the F-Secure "run in compatibility mode" setting and re-booted.

The message did not appear!!!

O/e I found that MB3 was running with all protection 'On'.
       Also, in F-Secure SAFE Deepguard application permissions included:
              mbamservice.exe permission is 'allow' with type 'automatic'. 
[I can not remember whether or not that was present during my previous attempts at a resolution].

My previous thread on this problem was "INSTALLATION PROBLEM" 26th January to 12th February 2017 (I most easily find that by clicking on my name).

Since the end of that thread I have not conciously done anything that would affect the problem.
BUT something has changed to allow MB3 service to connect.  MB3, F-Secure SAFE, Windows (I find that always a good suspect), something else?

Whatever the reason ALL IS NOW WELL. I have made further checks by rebooting and by switching off and then, later, on.
F-Secure SAFE 'run in compatibility mode' is unticked and MB3 is running with all protection 'On'.

I might even now try MB3 on my laptop; it is still running 2.
I will report when I have done that.

Thank you all, though it was Telos prompting me to look at reporting to F-Secure that moved me in the right direction.

Ray.

[Telos]

Good to hear things are looking better for you @RayStA

DeepGuard has been an issue with 3 of my programs. In all cases F-Secure has been helpful in resolving the conflict.