Run-time error '0' and '440'

[jltympanum]

I have a Windows 10 computer on which is installed Malwarebytes Anti-Malware (Corporate) 1.80.2.1012.  Every few days it pops up a message "VBAccelerater SGrid II Control Run-Time error '0'" and behind it is another popup message "Malwarebytes Anti-Malware Run-time error '440' Automation Error".  The machine has to be rebooted to get MWB working again.  I have found by surfing a supposed fix for this problem which consists of applying regsvr32 to mbamext.dll, ssubtmr6.dll and vbalsgrid6.ocx.  However it applies to Windows 7.  So I ask:

  1.  Can anyone confirm that this is actually a correct fix for the problem?

  2.  Does this same fix apply to Windows 10 as well?

[djacobson]

This is most common on server's with long up times. How many scans are taking place between your up times? MBAM 1.x has limitations in how many scans can run, around 80-100, per uptime of the machine. The issue is due to the the desktop heap memory size. Reboots correct this as Windows no longer has tools to refresh desktop heap memory without restarting.

Edited August 29, 2018 by djacobson

[djacobson]

See this post for other items you should be aware of -