I have setup Windows 7 (64-bit) with ESET 4 and Malwarebytes Pro (v 1.60.xx onwards). In order to delay the MBAM Service by 20 secs (to avoid potential conflict with ESET at start-up) I do the following:
1. Change the start-up type for service "mbamservice.exe" to Automatic, from Automatic (Delayed Start).
2. Add a new DWORD Value "delayguistart" and set it to 20 at the Registry key:
This works great, however, I notice that the MBAM service can revert back to Automatic (Delayed Start). This leads to a much longer start-up (1-2 mins) and hence a delay in protection when online.
I have just isolated one thing that causes this change of the start-up type (back to delayed start). If I start the scanner and click onto the “scheduler settings” tab, without doing any changes even, I notice that the service is reset to delayed start. Why does this happen?
Secondly, I believe that updating the program version may also change the MBAM Service start-up back to delayed start. Can you confirm this? I isolate this by turning off the “program update” options within the “updater settings” tab.
Finally, I think I have noticed it change without the above 2 steps occurring. Are you aware of the regular identity updates triggering this action? Are you aware of anything else doing it?
It would be great if the user-chosen start-up type was never reset by the program. This would allow the program to start protecting the PC at the desired, shorter delay time and not after 1-2 mins.
Thanks in advance