I’m using the latest version of AIS, and for some reason the firewall gets turned off automatically after some time… I cant tell exactly when, but this has been happening for the past 5 days… I’m pretty sure that my PC is not infected as I have 3 resident shields running - AIS, MBAM, SAS…
I know 3 might be a bit too much, but wanted to run 3 of them because AIS and MBAM didnt warn me when opening this infected file, it detected it AFTER opening and executing it only… So I decided to add SAS as well… Since the specs on my PC are good it shouldnt make much of a difference in the performance… Also there are no known compatibility issues between these 3 for the moment right ?
But anyway is there a log or something that records firewall activity - like what caused it to turn off, whether it was manually done or not ? the FW activity log doesnt mention anything…
As so far there were no incompatibilities among SAS and MBAM. Last few days I have used both products (paid versions) but leaving one as On-demand. MBAM also track malware before execution too. But with SAS Pro, it processes heavily when definitions get automatically updated at start up and it runs automatic startup test too. As my guess it may interfere with avast. And if you research more you may see that MBAM has more detection rate than SAS.
1st you may try disabling Windows Firewall & SAS automatic protection n see if it works.
I know that MBAM tracks malware before they execute… So does Avast… but thats not the case, they failed to stop it at the execution but removed it AFTERWARDS… Stopping it before it got spread would have saved me the trouble of performing scans and removing them… Which is why I have SAS running real time…
I know that SAS is a bit heavy on the startup so I have disabled it on startup… So I manually run it everytime I login but have real time protection…
You have misunderstood my post… Avast FW and Win FW are said to have no conflicts… Same goes with MBAM + SAS + AIS, there are so many people who use all of these together without any problems… I wanted to know how the Avast FW could have gotten disabled automatically and whether I can track what did it by referring to a log or something…
I have no answer exactly why you should WF turn off. But once I had same problem and another member offered me to turn off WF n try out. As he suggested, it solved.
There are many who use MBAM + SAS + AIS. But most have one On-Demand, either MBAM or SAS.
Yeah I know but as I have said in my first post I dont know when/how it gets turned off… I had it running with windows FW for so many months so I know for a fact that its not the issue… the ONLY difference was I turned on real-time protection of SAS… But then again I have seen users in this forum who run ALL 3 of them REAL TIME… So again I’m not sure why it happens… If only theres a log that gives out the time/reason the FW stopped…
Giving a try wont be worthless but since I dont know exactly when it goes off, it wont help much…
Alright, as if you prefer you may try Firewall Logs under Firewall menu, and make sure to set - Show log for > ‘Activity’ to show activities that has been carried out.
Thanks Mayura for the assisst :), but it doesnt mention anything about being turned off… I mentioned it in the first post. Hope theres another log… MBAM has a log that mentions when the protection is turned off and when it gets back on… I think Avast also has a log like that… :-\
ooo Thanks! There you go! ;D These are the errors(There are more but these are the most recent ones)! Now hope someone with an in-depth knowledge about the Avast FW will tell me what they mean ;D
I’ve checked those minidump files. Crashes of programs can be found as below,
unp33134183.tmp : Crash of AvastUI.exe, AshBase.dll
unp86191549.tmp : Crash of Google Chrome Real Player Plugin
unp251887968.tmp : Crash of afwServ.exe (avast! Firewall) and stop service
As my knowledge it may happen due to new driver or program update like Microsoft Visual C++ Package installed via another software installation or windows update. avast! use Microsoft Visual C++ Package too. So overwritten of files might be the reason of sudden crash. May be it cause due to Bad Sectors too, but I hope you haven’t got any of em.
It took some time to check and analyze:)
If you are still suffering from this error, the recommendation is trying repair or fresh install of avast!
Thanks Mayura for taking your time to help me out. The only new thing I installed was my VGA drivers - I actually reinstalled it had the latest version and I removed it completely and had to reinstall… Other than that I installed the latest version of VirtualBox… Thats pretty much it… Still dont know what caused it :-\ If it happens again will reinstall Avast, but dont know if it will help with this as this started happening a few days ago…
Before you make any drastic changes, I would make one of your resident (either SAS or MBAM) as on-demand. You have 3 resident scanners now, and they are most likely causing a conflict. As a test, turn one of them (SAS or MBAM) to on-demand and see if this fixes your problem.
In addition, did you put your resident software into each other’s software exclusions? If not, please do so to avoid conflicts.
I do not see a reason to uninstall/install until you test out the above first. Report back on your findings. Thank you.
Yes, I have excluded Avast on MBAM, and I forgot about SAS, so just excluded Avast on that as well… Also MBAM is excluded on SAS and vice versa… Didnt exclude anything on Avast yet - but since Avast FW is being disabled, as long as I exclude Avast on both of them it should be fine - theoretically…
If the problem persists, will exclude others on Avast and if its still there will go back to 2 resident scanners… I stated why I added a third in the earlier post, but if they cause conflicts I will disable one of them, most likely SAS… Because AIS and MBAM were running fine for a pretty long time and I think this started hapenning after I added SAS realTime, again the problem is I am not aware of the exact time this happens and therefore I cannot put a pin on whats causing it… Right now I have all 3 running realTime and so far the FW is enabled…
Ok so I didnt have SAS running today but it still got turned off… the FW I mean… I didnt have any “odd” program running… Does anyone know how to check for the cause of this? Is there a way to pin point to the program thats causing this? Any help is highly appreciated…
I had the computer running from 1pm, and now its 5pm when I noticed it wasnt running bu inbetween I kept checking if it was running or not, so it wasnt turned off instantly and I wasnt running any new program between the time it was running and stopped…
I know you mentioned that in the past you tried turning off Windows FW, which you had running with AIS and SAS Pro. Now that you have SAS Pro as on-demand, try turning off Windows FW as well leaving only AIS and MBAM as resident. Reboot.
Have you upgraded to the current version of Avast 6.0.1125 yet? If not, please do so and see if this fixes the problem. Thanks.
Did you check out ‘Application Rules’ for avast! FW service?
There you go! ;D These are the errors(There are more but these are the most recent ones)! Now hope someone with an in-depth knowledge about the Avast FW will tell me what they mean ;D