Jump to content

Gagome

Members
  • Content Count

    4
  • Joined

  • Last visited

About Gagome

  • Rank
    New Member
  1. Hello Porthos & LiquidTension, Yes, I have already followed the advice from Porthos and I have deleted the downloaded new installer. And now I no longer get the prompts to install the new version. I just wanted to wait a day to find out if it really is working before I provide feedback. The now open question is: are you able to fix the issue with ProxyCap?
  2. I have installed version 3.6.1 but now I get several times during a day a prompt to upgrade to a new version. But I have set in Malwarebytes Settings Application Updates to Off. Why do I get the prompt then? This is really getting to be annoying. What can I do to avoid those prompts? I guess this is a bug in version 3.6.1. True, I hope you can fix the problem in 3.7.1 to make it work together with ProxyCap. But currently getting the prompts several times during a day is really annoying.
  3. Hello, ProxyCap is needed and I will not uninstall it. I hope you find a solution. From where can I download the previous installer of MB 3.6.1? Thanks.
  4. Hello, I got prompted to update to MB 3.7.1. After the installation completed successfully I didn't see the MB icon in the notification area. I am running Windows 10 Pro 1803 x64. I checked Event Viewer and found: Faulting application name: mbamservice.exe, version: 3.2.0.765, time stamp: 0x5c508d96 Faulting module name: MwacLib.dll, version: 3.1.0.535, time stamp: 0x5c4b9e72 Exception code: 0xc0000005 Fault offset: 0x000000000000d95c Faulting process id: 0x2a10 Faulting application start time: 0x01d4c546b98e792a Faulting application path: C:\Program Files\Malwarebytes\Anti-Malware\mbamservice.exe Faulting module path: C:\PROGRAM FILES\MALWAREBYTES\ANTI-MALWARE\MwacLib.dll Report Id: d6317523-d568-4827-a747-06c3d1de023c Faulting package full name: Faulting package-relative application ID: Then I downloaded mb-support-1.3.1.553.exe and did run it. It tried to repair MB. I had to do a reboot too. But after my PC started I found the same messages in Event Viewer. I collected all log data. You will find all attached. I have now the same problem on my second device which is too Win10 Pro 1803 x64. Maybe there is a bug in MB 3.7.1? Can you please look into this? Thanks. mbst-clean-results.txt mbst-grab-results.zip
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.