Conflict between Malwarebytes 2.1.8.1057 and Avast 2015 10.3.2223.1143

[REDACTED]

I’d like to tell you about my latest “frustrations” in Windows-land, and this time between the products displayed in the subject.
 
My present OS: a fully updated Windows 7 Utimate Service Pack 1 and 64-bit Operating System.
 
My Malwarebytes packet: 2.1.8.1057, with the most recent updates.
 
For Antivirus I use Avast! Free.
 
I had no problems whatsoever between Malwarebytes 2.1.8.1057 (and previous releases) and Avast! Free dating before its latest release (2015 10.3.2223.1143).
 
But I do have them after I installed Avast’s latest release.

See, I regularly make an Acronis Drive Image, and before I start doing so, I chkdsk drive C:   [chkdsk c: /f /v]
You know, to chkdsk c:, one has to start up again. And so I did.
But alas! the chkdsk could not do its job, as some other installed program blocked this. And I was launched back to square one. Never in my computer life seen that happen before.
Tried this several times. Wasted effort!
Unfortunately enough the blocking program was not named.
So you go searching.
 
It so happened I unchecked some items in your Malwarebytes 2.18.1057 settings “Detection and Protection” : Advanced Heuristiscs and Archives.
Then I had Malwarebytes scan the computer.
Then I tried chkdsk again.
And lo and behold, it worked again!
 
As far as this 76-year-old can understand, there is a conflict between Malwarebytes' Heuristics and this Avast release.
Let me reiterate that this did not happen between Malwarebytes this and previous versions and Avast versions before their latest release.
I do not want to wag my finger at either Malwarebytes or Avast. Things like these can happen, I guess.
The question for me is: can this be fixed?

[DavidR]

I noticed my system locking up in several areas with 2.1.8.1057 Premium when browsing and also when using MS Excel.

I noticed this with the latest avast free beta 2015 10.3.2224 and I used my disk imaging software to restore my last disk image back to 2015 10.3.2223, but I was still encountering some lockups requiring a hard power shutdown.

Then I started looking at other areas, I didn't change the MBAM Premium settings (yesterday) I disabled it/stopped it from starting and I have been monitoring performance and so far there hasn't been a repeat.

So there appears to be some sort of conflict, which I didn't encounter with the previous avast free beta before the release of 2015 10.3.2223.

[REDACTED]

I’d like to tell you about my latest “frustrations” in Windows-land, and this time between the products displayed in the subject.
 
My present OS: a fully updated Windows 7 Utimate Service Pack 1 and 64-bit Operating System.
 
My Malwarebytes packet: 2.1.8.1057, with the most recent updates.
 
For Antivirus I use Avast! Free.
 
I had no problems whatsoever between Malwarebytes 2.1.8.1057 (and previous releases) and Avast! Free dating before its latest release (2015 10.3.2223.1143).
 
But I do have them after I installed Avast’s latest release.

See, I regularly make an Acronis Drive Image, and before I start doing so, I chkdsk drive C:   [chkdsk c: /f /v]
You know, to chkdsk c:, one has to start up again. And so I did.
But alas! the chkdsk could not do its job, as some other installed program blocked this. And I was launched back to square one. Never in my computer life seen that happen before.
Tried this several times. Wasted effort!
Unfortunately enough the blocking program was not named.
So you go searching.
 
It so happened I unchecked some items in your Malwarebytes 2.18.1057 settings “Detection and Protection” : Advanced Heuristiscs and Archives.
Then I had Malwarebytes scan the computer.
Then I tried chkdsk again.
And lo and behold, it worked again!
 
As far as this 76-year-old can understand, there is a conflict between Malwarebytes' Heuristics and this Avast release.
Let me reiterate that this did not happen between Malwarebytes this and previous versions and Avast versions before their latest release.
I do not want to wag my finger at either Malwarebytes or Avast. Things like these can happen, I guess.
The question for me is: can this be fixed?

Same problem here, chkdsk It does not work. Other problem, the folder C:\ProgramData\AVAST Software\Avast\ng\NgBase\Snapshots\Snapshot_{ef32f3a0-bd18-11e4-8e73-806e6f6e6963}.dat this folder is fragmented lot, on every boot, and you can not defragment, same at boot with Smart Defrag Pro 4.1 how to have the old version of Avast?

[glnz]

I just had a similar conflict between Avast Free and Malwarebytes Free.

See this post for details:

https://forum.avast.com/index.php?topic=174496.0

[schmidthouse]

You can bet Avast is aware.
Also being discussed on MBAM forum: https://forums.malwarebytes.org/index.php?/topic/171128-conflict-between-malwarebytes-2181057-and-avast-2015-10322231143/

[glnz]

schmidthouse - you seem to have an "in" with Avast.

Has Avast actually told you they're looking at this?

[schmidthouse]

schmidthouse - you seem to have an "in" with Avast.

Has Avast actually told you they're looking at this?

No in here. Just have been around Avast & Forum for some years.
Stuff like this (incompatibilities between Software installations) just doesn't go unnoticed for long.....I don't believe.
Whether or not a company chooses to resolve/fix the issue in their code is another question.

[REDACTED]

Being the one who started this topic, I'd like to tell you how I feel now.

First, there was a very nice mail I got from someone from Malwarebytes themselves. Alas , it did not help in the end.

Then I removed Avast completely, left Malwarebytes Premium on my computer, and installed a different AV product.
I wanted to install Avira, but was unsuccessful.
I tried AVG for a change. Not the one that is really my cup of tea, but... all problems solved. Still happy after two full days.
 
So the culprit seems to be Avast. And since it interferes with Malwarebytes, they perhaps contact one another..

Kind regards,

 

Ananda.

[REDACTED]

Same problem here, chkdsk It does not work. Other problem, the folder C:\ProgramData\AVAST Software\Avast\ng\NgBase\Snapshots\Snapshot_{ef32f3a0-bd18-11e4-8e73-806e6f6e6963}.dat this folder is fragmented lot, on every boot, and you can not defragment, same at boot with Smart Defrag Pro 4.1 how to have the old version of Avast?

Solved temporarily, uncheck Secure Virtual Machines. Ng fail since 10.3.2223

[bob3160]

Same problem here, chkdsk It does not work. Other problem, the folder C:\ProgramData\AVAST Software\Avast\ng\NgBase\Snapshots\Snapshot_{ef32f3a0-bd18-11e4-8e73-806e6f6e6963}.dat this folder is fragmented lot, on every boot, and you can not defragment, same at boot with Smart Defrag Pro 4.1 how to have the old version of Avast?

Solved temporarily, uncheck Secure Virtual Machines. Ng fail since 10.3.2223

Disable HTTPS scanning in avast:
https://forum.avast.com/index.php?topic=174332.msg1239891#msg1239891

[REDACTED]

No it does not work, what i tried in first.

The problem is with NG / Secure Virtual Machines.

[bob3160]

No it does not work, what i tried in first.

The problem is with NG / Secure Virtual Machines.

It works for me on Windows 10 and using the Chrome browser.

[REDACTED]

Since the 10.03.2223 version for improved compatibility with Windows 10, some people have had problems with Windows XP and then Windows 7.

I hope it will be resolved soon 

[REDACTED]

Does anyone know if Avast has addressed this and if the new BETA fixes ?
I've been traveling and not had chance to try so kind of holding on to older version until this is addressed.....AND I can get time to get to it.

[REDACTED]

Hi,

I emailed Malwarebytes and they sent me the following.  Which Avast installed, and now there does not seem to be a conflict any longer .. woo hoo!  Hope it works for you too:-) >>>

Some antivirus applications require exclusions to be defined for Malwarebytes Anti-Malware, so that they do not interfere with Malwarebytes operation. These are typically referred to as exclusions or ignore list entries.

The following is a list of Malwarebytes programs which should be placed on an Exclusion list if required. This list is specific to Malwarebytes Anti-Malware 2.0.

For 32-bit Windows Vista or Windows 7 or Windows XP:
C:\Program Files\Malwarebytes Anti-Malware\mbam.exe
C:\Program Files\Malwarebytes Anti-Malware\mbamdor.exe
C:\Program Files\Malwarebytes Anti-Malware\mbampt.exe
C:\Program Files\Malwarebytes Anti-Malware\mbamservice.exe
C:\Program Files\Malwarebytes Anti-Malware\mbamscheduler.exe

For 64 bit versions of Windows Vista or Windows 7 or Windows 8:

C:\Program Files (x86)\Malwarebytes Anti-Malware\mbam.exe
C:\Program Files (x86)\Malwarebytes Anti-Malware\mbamdor.exe
C:\Program Files (x86)\Malwarebytes Anti-Malware\mbampt.exe
C:\Program Files (x86)\Malwarebytes Anti-Malware\mbamservice.exe
C:\Program Files (x86)\Malwarebytes Anti-Malware\mbamscheduler.exe

For specific steps on how to add these files to your antivirus’ exclusion list, you will need to contact your antivirus provider directly for best results