Experience with MB 3.0x...

[dont_touch_my_buffer]

I have experience with a few different versions of Malwarebytes, 3.0, 3.05, 3.06 and various preview builds. With the exception of one case, unable to install newer version, the only issue had been with all versions is the real time web protection. It would not start, nor could it be enabled manually.

Yes, in each cases, I did go through the "standard procedure" to try fixing the issues. This includes uninstall MB, run the "MBAN clean" and FRST64 as admin, install/re-install MB, exempt Malwarebytes executables and drivers from AV scanning, etc. The web protection would work, sometimes even for couple of days, but inevitably the web protection would not start.

So, with the last version currently on the system, I've got tired of going through the "standard procedure" and decided that my system can live for another day without it. After all, it has number of other security layers that can mitigate the risk for accessing the web. So, it's been running like that for over a week and couple of interesting observation about the web protection.

Firing up the system in the morning had been showing different results:

• Web protection starts with the system
• Web protection does not start, but standard UID can start it manually
• Web protection does not start, but admin account can start it
• Web protection does not start and no account can start it
• Web protection does not start, cannot be started by any account, stopping AV allows starting it up

As of today, the web protection started with the system, which it did not do yesterday, nor did I started manually. This is not the first time that this has taken place during the last week or so, happened couple days ego as well.

The system did not change during this time-frame, except for the daily updates for both MB and the separate AV. While I understand that the AV can interfere with MB, in my view, it would do it all the times. The more likely scenario is that the MB updates are breaking the web protections.

Malwarebytes receives daily updates for:

   "controllers_version" : "1.0.50",
   "db_version" : "2017.02.02.04",
   "dbcls_pkg_version" : "1.0.1158",
   "installer_version" : "3.0.6",

Yes, I am aware that this is not the current version, just don't feel like running it again...

Each time the updates are incorrect and/or has not been applied correctly, the web protection is off. Conversely, if the updates are fine, the web protection starts with the system. Is there a way to disable updates for times when the web protection starts?