Just an FYI, same problem here. ESET NOD32 188.8.131.52 and MBAM 184.108.40.2060.
This problem did not exist a few days ago...which is when I updated MBAM to the newer version on 2 computers. Then last night Microsoft Update ran, rebooted the computers and they both locked up. When I disabled MBAM, the both fired right up. Others computers that are running the older version of MBAM have no problems.
I can create a ticket if necessary...but this is obviously not a single computer issues. FWIW, one of my affected systems is Windows 7 64 bit and the other is Windows XP.
Posted 13 February 2013 - 10:59 PM
Posted 14 February 2013 - 03:22 AM
Yes creating a ticket will be necessary as every system is different. In the vast majority of cases it is due to infection or exclusions for antivirus not setup properly. Don't forget that both our product and your antivirus and your Microsoft updates are always evolving and trying to stop and prevent infections and sometimes all these changes do cause conflicts as well.
Posted 14 February 2013 - 04:17 PM
Other than setting exclusions in MBAM for scanning ESET, the user needs to set "allow" status for all MBAM service and every executable files for any operations on "target applications" in the ESET's HIPS manual rules. Try go to Windows safe mode to the MBAM service to be not running at start up first in order for user to load the Windows for the above settings to be done. Then, the user can reactive the MBAM service for the following start up. The computer should be running a bit more smooth soon. Sometimes, start-up beiing frozen could be due to ESET and MBAM database updating during Windows loading. In such a case, reboot Windows at safe mode and then restart at normal mode.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users