Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Mo0nwalker on January 15, 2011, 01:08:00 PM
-
To minimize the time use? Or would it conflict or give some bad result?
-
Not 100% sure but i would think that each would have a better chance of detecting the nasties by running individually, if you ran them together you wouldnt want to get lockup's.
-
To minimize the time use? Or would it conflict or give some bad result?
Run one after the other...!!
asyn
-
To minimize the time use? Or would it conflict or give some bad result?
By trying to run them concurrently you are likely to actually slow the overall scan duration, as avast's real-time scanner will be at work also as it scans what MBAM opens for scanning. So you will get duplication of scanning, etc. this will also increase resource use CPU and RAM which could add to the overall time of the avast on-demand scan and MBAM scan.
I used to advocate pausing the avast resident scanner when running third party scans to avoid this duplication of scan, increased use of resources, extending the overall scan duration and the possibly conflict between the two scanners. I have systems which are powerful enough and have enough resources for it not to be an issue, but I still tend not to run simultaneous scans.
One thing you didn't mention is if you are using the free or Pro version of MBAM, as this could add another level of complexity to the question ?
-
To minimize the time use?
and for your weekly or daily scan you only have to use quick scan, and that should not take long
-
Hi,
I am having the exact same and related questions, so I hope that its alright to add my questions here. I only refer to the freeware (on-demand scanner) version of MBAM.
I used to advocate pausing the avast resident scanner when running third party scans to avoid this duplication of scan, increased use of resources, extending the overall scan duration and the possibly conflict between the two scanners.
I can 100% confirm your statement that Avast is scanning everything while MBAM scans. Is this double scanning specific to Avast or would any AV-software do that? Does this behavior have any negative effects on my system? I saw that there is a high CPU usage of both mbam.exe and avastsvc.exe with this double scanning, but it fluctuated and was ok in the end. Scan time of MBAM did not increase significantly.
To sum up: do I have to/should I deactive Avast or certain components while scanning with MBAM? (Didnt have to do this with other AV-software before)
Thanks to all!
-
I can 100% confirm your statement that Avast is scanning everything while MBAM scans. Is this double scanning specific to Avast or would any AV-software do that? Does this behavior have any negative effects on my system? I saw that there is a high CPU usage of both mbam.exe and avastsvc.exe with this double scanning, but it fluctuated and was ok in the end. Scan time of MBAM did not increase significantly.
To sum up: do I have to/should I deactive Avast or certain components while scanning with MBAM? (Didnt have to do this with other AV-software before)
Any good AV-software would do that.
I have MBAM Pro and have not had to deactivate avast! while the morning Quick scan runs nor the Flash scan runs on MBAM updates.
-
To prevent Avast from scanning everything while MBAM scans, you should exclude MBAM in Avast Settings - Exclusions:
How to exclude Malwarebytes' Anti-Malware (MBAM) from Avast! 5.x:
------------------------------------------------------------------------
Add these Exclusions to Avast as appropriate to your version of Windows
------------------------------------------------------------------------
* Open Avast! and click on Settings - Exclusions:
* Copy and paste the file path text below (one line at a time) into the "enter path" box.
Select the entries below, as appropriate to your version of Windows:
Click OK when done.
For Windows XP:
C:\Program Files\Malwarebytes' Anti-Malware\mbam.exe
C:\Program Files\Malwarebytes' Anti-Malware\mbamgui.exe
C:\Program Files\Malwarebytes' Anti-Malware\mbamservice.exe
C:\Program Files\Malwarebytes' Anti-Malware\mbam.dll
C:\Program Files\Malwarebytes' Anti-Malware\mbamext.dll
C:\Documents and Settings\All Users\Application Data\Malwarebytes\Malwarebytes' Anti-Malware\rules.ref
C:\Windows\System32\drivers\mbam.sys
C:\Windows\System32\drivers\mbamswissarmy.sys
C:\Program Files\Malwarebytes' Anti-Malware\*
C:\Documents and Settings\All Users\Application Data\Malwarebytes\*
For Windows Vista and Windows 7 32 bit:
C:\Program Files\Malwarebytes' Anti-Malware\mbam.exe
C:\Program Files\Malwarebytes' Anti-Malware\mbamgui.exe
C:\Program Files\Malwarebytes' Anti-Malware\mbamservice.exe
C:\Program Files\Malwarebytes' Anti-Malware\mbam.dll
C:\Program Files\Malwarebytes' Anti-Malware\mbamext.dll
C:\ProgramData\Malwarebytes\Malwarebytes' Anti-Malware\rules.ref
C:\Windows\System32\drivers\mbam.sys
C:\Windows\System32\drivers\mbamswissarmy.sys
C:\Program Files\Malwarebytes' Anti-Malware\*
C:\ProgramData\Malwarebytes\*
For 64 bit versions of Windows Vista and Windows 7:
C:\Program Files (x86)\Malwarebytes' Anti-Malware\mbam.exe
C:\Program Files (x86)\Malwarebytes' Anti-Malware\mbamgui.exe
C:\Program Files (x86)\Malwarebytes' Anti-Malware\mbamservice.exe
C:\Program Files (x86)\Malwarebytes' Anti-Malware\mbam.dll
C:\Program Files (x86)\Malwarebytes' Anti-Malware\mbamext.dll
C:\ProgramData\Malwarebytes\Malwarebytes' Anti-Malware\rules.ref
C:\Windows\System32\drivers\mbam.sys
C:\Windows\SysWoW64\drivers\mbamswissarmy.sys
C:\Program Files (x86)\Malwarebytes' Anti-Malware\*
C:\ProgramData\Malwarebytes\*
Click on OK
Close Avast!
------------------------------------------------------------------------
Add Avast to the MBAM Ignore List (MBAM version 1.50 or higher)
------------------------------------------------------------------------
Opem MBAM, click on "Ignore List", click "Add"
Browse for this folder:
C:\Program Files\Alwil SoftwareClick "OK", click "Exit".
-
<snip>
I used to advocate pausing the avast resident scanner when running third party scans to avoid this duplication of scan, increased use of resources, extending the overall scan duration and the possibly conflict between the two scanners.
I can 100% confirm your statement that Avast is scanning everything while MBAM scans. Is this double scanning specific to Avast or would any AV-software do that? Does this behavior have any negative effects on my system? I saw that there is a high CPU usage of both mbam.exe and avastsvc.exe with this double scanning, but it fluctuated and was ok in the end. Scan time of MBAM did not increase significantly.
To sum up: do I have to/should I deactive Avast or certain components while scanning with MBAM? (Didnt have to do this with other AV-software before)
Thanks to all!
Generally this double scanning will happen with any good resident AV as that is essentially its job, to scan files before they are opened, etc.
You don't have to disable anything, you just need to know the overheads and the potential for conflict and decide based on your own system if you need to stop the file system shield whilst doing another security scan.
-
Two things, Avast! absolutely does scan at the same time Malwarebytes does and doesn't seem to slow anything down at all. I consider this to be desirable.
Secondly, even the maker of MBAM says that a quick scan is all you should ever have to do with that program. They constantly update the program to scan in the locations where malware has been known to insert itself or make changes, it's part of the database. If the malware is not in their database, it won't be detected anyway and a full scan will offer no further benefit than a quick one.
-
To prevent Avast from scanning everything while MBAM scans, you should exclude MBAM in Avast Settings - Exclusions:
How to exclude Malwarebytes' Anti-Malware (MBAM) from Avast! 5.x:
<snip>
Sorry but that won't stop avast from scanning files that MBAM opens to scan, if those files are scanned in place, then depending on the file type avast will scan them (generally those that present an immediate risk, executables and those targeted by malware). By excluding MBAM files only excludes those files from being scanned, it doesn't ignore/exclude the processes/actions, e.g. the files it opens for scanning.
This mask covers all files in the folder so all of the files excluded in the Malwarebytes' Anti-Malware before this are a waste of time anyway.
C:\Program Files\Malwarebytes' Anti-Malware\*
Excluding a complete folder will obviously leave it less secure as nothing in it would be scanned.
I only have the free version and I have nothing for MBAM excluded on my XP or win7 systems.
~~~~
The major area to exclude in MBAM (Pro) for avast isn't actually in the avast folder but in c:\windows\temp\_avast5_ folder as that is where avast unpacks files it is going to scan.
-
MBAM 1.50 dropped the zlib.dll
My list was correct for current versions of MBAM. I got this list from the MBAM forum.
I and many of my customers use the Pro version of MBAM.
I am currently reviewing what David R said, thanks
-
Why would you not just do the 'whole' Malwarebytes 'Program' Folder?
thats what I was told to do....
-
MBAM 1.50 dropped the zlib.dll
My list was correct for current versions of MBAM. I got this list from the MBAM forum.
I and many of my customers use the Pro version of MBAM.
I am currently reviewing what David R said, thanks
Do you have a link for those latest exclusion's on the MBAM forum as i cant find them, i can only find the one's that i have show'n here.
-
@CraigB
http://forums.malwarebytes.org/index.php?showtopic=10138&st=0&p=167851&#entry167851
They do not specifically say for Avast, so refer to AVG.
They tell you to exclude the directories, then they show the list. Note that zlib.dll is no longer used in the current version of MBAM as of 1.50
I have read in their forum that Avast 5 works without these exclusions though. But I use the MBAM pro version and thought it might help performance to add the exclusions anyway. I am open to corrections though.
I already added C:\Windows\Temp\_avast5_ to MBAM ignore list
-
This is the only exclusion i use as well in MBAM C:\Windows\Temp\_avast5, i deleted all the other exclusion's for MBAM in avast several weeks ago as per discussion's with DavidR and have had no problem's or slow down's what so ever.
-
Interesting and thanks folks!
can you list in this section just what is needed to exclude in avast
for Malwarebytes Pro? thank you
-
Interesting and thanks folks!
can you list in this section just what is needed to exclude in avast
for Malwarebytes Pro? thank you
The exclusion's for MBAM in avast are all listed on the previous page but as discussed they are not needed, if you were to include the exclusions you would have to add them to the settings exclusion's as well as the file system shield exclusion's.
-
I do not have any MBAM files in my avast! Exclusions.
They are only needed with avast! AIS for the firewall I believe.
-
I have nothing whatsoever in Avast! exclusions and have no problems.
-
Man I don't know about this whole thing with Malwarebytes.
I have been using it as a secondary Malware program running in batch mode for about as long as I have been using Avast free and now AIS about two years. I don't think that Malwarebytes has found more than one or two bad files over the two years.
I still run it in batch mode because you never know and it is no hassle to run it once a week that way.
However to me at least based upon my experience since running AIS running any Malware program real time is not worth the the drain on resources and potential conflicts for what it gives you.
I do run Windows Defender real time but that is because I consider it part of the Windows 7 Operating System, even though one could argue that it isn't and it has never conflicted with anything and my Windows 7 computers. It comes with Windows 7 and I just set it up when I got the my Windows 7 computers. Since then I have left it alone and actually check once every several months or so to see if it is actually still running because that is the only way I know that it is there and running. While it might create some drain on the computer's processing power I still leave it because again I consider part of the Windows 7 operating system just like I do the Windows Firewall which I have left on.
Since I have been using AIS I have found a couple of questionable programs using batch AV scanners like on-line ESET and Dr. Web that AIS does not classify as infected or questionable and have just deleted them. However Malwarebytes never Identified them as such and they could be false positives.
I think when you running AIS, Windows Defender and Windows Firewall that running Malwarebytes in real-time mode is unnecessary overkill.
Just my not to popular opinion :) :)
-
... I think running Malwarebytes in real-time mode is unnecessary overkill. ...
If you only have Avast! Free, I highly recommend MBAM Pro real time protection. The web site blocking blocks "drive by" exploits on web sites before they get on the computer.
-
If you only have Avast! Free, I highly recommend MBAM Pro real time protection. The web site blocking blocks "drive by" exploits on web sites before they get on the computer.
+1
-
... I think running Malwarebytes in real-time mode is unnecessary overkill. ...
If you only have Avast! Free, I highly recommend MBAM Pro real time protection. The web site blocking blocks "drive by" exploits on web sites before they get on the computer.
It is worth the money getting and installing AIS rather than using some combo. Better to save up the pennies that it cost to get an AIS license and purchase the AIS license. Just my opinion :)
-
***
By now, most of you are actually Off Topic. Read the Original Post again.
This thread is about running 2 scanners at once and not about the 2 scanners detecting each others files. It is about 2 different scans trying to scan the same files accessed by each scanner at the same time.
It has already been stated why it is not a good idea to run 2 scans at the same time in the first 5 or 6 replies.
If you want to discuss excluding each scanner from the other scanner, start your own thread about it and stop hijacking this one.
***
-
Many people say you mustn't install more than 1 antivirus into your PC. That's a lie. You can.
* None of your antivirus can be "jealous". Bit-Defentes, for example, is and uninstalls your Avast if you put it into your PC.
* If you have a couple of Antivirus in your PC, one of them has to be the "boss" the others its "slaves". Only the "boss" can do realtime-scanning, whereas this function cannot be active in the "slaves", which only run, when cliced by you, after scanning of the whole HD by the "boss".
I prefer Avast Free as the "boss", because it is one of the most comfortable free antivirus.
* Malwarebytes Free (not its trial version) fits quite well with Avast Free, because it does not have any realtime-scanning at all (its trial version however has). After "scanning at initiation" with Avast Malwarebytes detects almost all PUPs and PUMs, which are quite hard for Avast.
-
Many people say you mustn't install more than 1 antivirus into your PC. That's a lie. You can.
* None of your antivirus can be "jealous". Bit-Defentes, for example, is and uninstalls your Avast if you put it into your PC.
* If you have a couple of Antivirus in your PC, one of them has to be the "boss" the others its "slaves". Only the "boss" can do realtime-scanning, whereas this function cannot be active in the "slaves", which only run, when cliced by you, after scanning of the whole HD by the "boss".
<snip>
First there is little benefit in breathing life into a topic that is almost three and a half years old as programs will have changed massively in that time.
No lie, your example of one AV uninstalling the previous one, is done for a single purpose, to prevent them from conflicting.
If there was no issue why would you have to take such measures to have one as the boss.
Resident AVs even when you disable the resident cover are still going to have the low level drivers running and it is these which can conflict.
-
ogalofofo you seem to be of the assumption that Malwarebytes is an anti-virus and it's not which is why it can be run alongside anti-viruses :)