Excuse me if this is in the wrong place or already been asked. I have been using Avast4 Home for a number of years and am extremely happy with it.
However since the upgrade to 4.8 I have been getting a pop-up which is asking for permissions to be changed or granted. Could some one please explain this to me and how can it be fixed.
Oh and it seems that if I click NO then all animations from any web page stops working, whilst clicking yes only allows some pages to work but not others.
and alanrf…have check the thread you suggested. Is this a new problem between Avast & ZA, as I have had both for approx 5 years now without any form of dispute betwwen them…that is until the most recent updates of Avast.
The avast team report that the problem you are encountering has been fixed in the new program update of avast. That update is now undergoing beta testing and you can read about that beta testing in the sticky post at the top of the forum.
If this problem is causing you difficulty you can:
Join the beta program and install the new release - bearing in mind that it is still in beta testing (I am using the new release and it has corrected a number of other issues and I cannot find any problems with it).
-or-
You can temporarily disable the avast self-defense module by avast Program Settings > Troubleshooting and checking the “Disable avast! self-defense module” box. That will stop the error message you are seeing.
This will not affect the antivirus functions of avast. The self-defense is a new function in avast 4.8 and with it off you will be really in the same circumstance as you were before with 4.7.
If you do disable the self-defense please remember to go back and turn it on again when you receive the next program update from avast.
That thread also mentions the disabling of the second AV, a point which seems to have been missed. Your image clearly shows that the culprit accessing the avast4.ini file is the ZA anti-virus module.
My main concern isn’t that this may or may not be a problem which has been fixed by the latest release which I think is an aside to the real issue, having two resident AVs installed on your system.
So you effectively have two resident anti-virus scanners on your system and this isn’t recommended and this is even if there weren’t any problems with the avast self-defence module. Uninstall/disable the ZA anti-virus module would resolve the problem and you could have the self-defence enabled and protecting avast now.
I deliberately did not go down this path. While I agree with you about the general undesirability of running two anti-virus products on the same system we know that some users do and without apparent conflict. (Were this a known conflict situation I would have gone down that path).
the user reports that the this was the case in avast 4.7 and had been for some time
the problem with the avast4.ini file pop-up introduced with avast 4.8
the developers have agreed that this “overkill” and have modified it in the new beta release 1178
when this user installs the new release it will be possible to continue with the same software configuration without the avast popup.
the problem here is clearly avast 4.8.1169 and not the user’s configuration.
Alanrf, I will disagree in this point. Nowadays is difficult to even think in a second antivirus running side-by-side with avast. Maybe BitDefender will be the only one without side-effects.
I don’t think ZA antivirus, sooner or later, won’t have problems with any other antivirus present.
I won’t recommend that anyone use a second resident AV as whilst it may have been working without problem for some time, when they do clash it can be more serious with systems locked on boot probably the most serious and we do see then in the forums, too frequently.
This avast4.ini modification issue which isn’t a clash between the two AVs but the draconian self-defence. But I feel it advisable to point out that two resident AVs isn’t advisable.
I even think it’s a bad feature or it’s not correctly working.
It will have issues and they’re being addressed. The self-defense module is welcome and should be there. It’s not funny has anything disabling and destroying avast…
I think it is a good and necessary feature, but the design and balance has to be right. I think it may be working correctly based on what they wanted it to do (stop anything having an impact on avast files, etc.), but we aren’t privy to that, so that is speculation on my part.
I think the issues are being addressed, it is just a shame that none of those beta testing this experienced any of these self-defence issues and they could have been addressed sooner.
The forums have had many, many topics on beagle infections killing avast!
Well… beta is only released at forums… there aren’t many users testing it. A lot of forum users just avoid using (testing) the beta… So, how many are really testing it? 50 guys?
I have made entirely clear that I wholeheartedly agree with both of you on the issue of two anti-viruses.
I pointed the original poster to a thread where David clearly recommended avoiding two antivirus products running concurrently. However, the poster also made entirely clear that ZA and avast has coexisted without issues on the system in question.
The irrefutable fact is that the user’s system was disturbed not by that but by the installation of avast 4.8. The next release will remove the disturbance to the user’s environment. I merely suggest it is not our place, especially with this issue, to demand the user change a problem free environment to compensate for the present over zealous actions of 4.8.1169.
I never meant to start an argument over this problem…however I have always believed that any user should be able to run 2 or more similar programs simultaneously without conflict. As a low end user I could only imagine how hard this makes writing and preparing programs, but for me where 1 AV has missed something the other usually picks it up and I have found both Avast & ZoneAlarms to be sufficient for the job at hand.
The fact that the Avast officialdom has recognized the problems and are endeavouring to repair this issue in the forthcoming release is a great thing as I am certain I am not the only person to be running both programs together.
As a matter of fact, we have decided to change the way avast INI modification consent dialog will be shown (from the next program update on).
Right now, any process (EXCEPT for those explicitly listed in the virus database) that tries to open the INI file for write access will trigger the consent dialog.
Now, from the next update on, we will only show the consent dialog if the request is EITHER coming from Notepad, OR if the process explicitly whitelisted by the user. The rationale behind this is that most people (probably) use Notepad to edit the file anyway, and those who don’t can tweak the settings a bit and configure avast to enable their favorite text editor to save the file.
This change should resolve practically all compatibility issues we’re now seeing (with regard to this feature).