Avast 5 + MalwareBytes Pro = Conflict? --> More info needed.

[YoKenny]

The forum software is doing stupid things to ftp addresses, converting them to http addresses, so what Vlk tried to type was:

Code: [Select]

ftp://ftp.avast.com/incoming
Just press "Win+R", which will open the 'Run' dialog, and type:

Code: [Select]

explorer ftp://ftp.avast.com/incomingThis will open an explorer window, just drop the file inside of it and wait for the upload to finish.

This old dog has to learn some new tricks  

Gona watch the Superbowl now.

[BoerenkoolMetWorstEnJus]

I am trialling AIS, currently 5.0.396(started a clean install with .377) and I have no problems with MBAM Pro, I also have Eset Smart Security 4 which also works perfectly with MBAM Pro. I did notice that the MBAM icon only appears a while after all the other icons already have appeared so it probably put itself on delayed start-up. On the MBAM forum delayed start-up is also frequently given with problems with other AV software and MBAM doesn't always do it automatically so doing it manually might help some users here.

[Vlk]

YoKenny, thanks much for the dump. It is indeed interesting... Will be looking into it today.

Thanks
Vlk

[cakedoer2]

It seems to only happen on 32-bit systems.

I may try it out in the near future if the problem exists by then.

[Vlk]

It's like a classic conflict between two AV programs. Very typical. The only question is why it worked OK with avast v4.8 - but the stability with v4.8 must have been very fragile anyway (I can imagine system hanging pretty much randomly, even though maybe not too often).

I'll talk to Marcin (Malwarebytes' CEO) and discuss what we can do together.


Thanks so far
Vlk

[fblais]

Tried to upload a dump an hour ago but it failed.
I'm unable to connect to your FTP server since then.
Do you know if it's down or something?

[fblais]

Was able to login on the FTP server again, but I'm now getting an error about not being able to create a file...
WTF?
(incoming folder, of course)
I want to help, but I can't...
(attached error message)

[coolsilver]

Vlk,

Any connection with the removal of old Win9x/ME/2000 code that would have allowed a bit more flexibility? Hate to suggest it but maybe that was a bug of 4.8 where it wouldn't lock files or fight as much over resources which could cause a virus to act in the same manner bypassing the shields?

I really have no idea. But I suppose it worked ok because of those weird os calls and links.

64 bit working ok... I would guess it would be since MBAM protection may be 32 bit only and working due the thw WinSxS config and 32 bit emulation of programs in 64 bit windows.....


Just talking out of my rear... but if it helps thats my ideas

[Vlk]

I think it's a WinXP conflict only.

[fblais]

Was able to login on the FTP server again, but I'm now getting an error about not being able to create a file...
WTF?
(incoming folder, of course)
I want to help, but I can't...
(attached error message)

I was finally able to upload it, zipped with 7-zip this time, so the archive is named FrancoisBlais.7z.
The 7Z format also product a much smaller archive. (158MB instead 221MB for a 512MB dump)
Hope this helps!
I had to uninstall Avast 5 again.
Even with the latest DB update, it hanged the PC this morning.
(MBAM real-time had been delayed 2 minutes at boot-up and was running along with Avast 5 free at that time, and only the file agent was installed, and with file writing analysis only)

[Hopper15]

It's like a classic conflict between two AV programs. Very typical. The only question is why it worked OK with avast v4.8 - but the stability with v4.8 must have been very fragile anyway (I can imagine system hanging pretty much randomly, even though maybe not too often).

I'll talk to Marcin (Malwarebytes' CEO) and discuss what we can do together.


Thanks so far
Vlk

This didn't happen with my 4.8 at all.

[redvette84]

I am also using MWB and I also had issues with the pc locking up at times and/or Internet explorer not opening or being unresponsive. It was about 90% of startups. The only thing changed was the installation of version 5. Version 4.8 never gave me these issues. I have uninstalled 5 and returned to 4.8 for now. WinXp.

[fblais]

It's like a classic conflict between two AV programs. Very typical. The only question is why it worked OK with avast v4.8 - but the stability with v4.8 must have been very fragile anyway (I can imagine system hanging pretty much randomly, even though maybe not too often).

I'll talk to Marcin (Malwarebytes' CEO) and discuss what we can do together.


Thanks so far
Vlk

This didn't happen with my 4.8 at all.

Likewise.

[rdmaloyjr]

It's natural for two antispywarers to conflict.  Avast! has an antispyware module & mbam is one, so bang they're going to bang heads!

It seems to me that if you make them compatible you will weaken one or both.   How do they decide which blocks and/or quarantines which spyware/malware?

I think it best to have mbam and SAS on-demand.  Let avast! be the real-time on access antispyware/antimalware.

It's like a classic conflict between two AV programs. Very typical. The only question is why it worked OK with avast v4.8 - but the stability with v4.8 must have been very fragile anyway (I can imagine system hanging pretty much randomly, even though maybe not too often).

I'll talk to Marcin (Malwarebytes' CEO) and discuss what we can do together.


Thanks so far
Vlk

Like I said...

Antivirus, antispyware & antimalware are just about three peas in a pod.

[Hopper15]

Hopefully everything gets worked out. I don't want to move to Avira.