avast chould be conflicting with another programme on your pc when it starts up u chould go back to the old version until the problem is solved or try reinstalling avast
Can you please right click on the avast icon in the system tray and take a look at “about avast” and validate the specific version of avast it shows you have installed.
The pop-up you are seeing was, as far as I know, only present in beta builds of avast and should be suppressed in the current production release.
A couple of days ago I updated a WinXP SP2 system (with avast 4.8.1195 installed) to SP3 without any pop-ups at all and I have seen none at all since I installed 4.8.1195.
A few minutes ago I updated a WinXP SP3 system to avast 4.8.1195 and no pop-ups are appearing on it.
If you are on 4.8.1195 then the pop-up details are logged in a file called selfdef.log in \Program Files\Alwil Software\Avast4\DATA\log. The log item should tell you the process name that provoked the denial.
There is always the potential that this is working differently in other Windows versions. I am on the US English version of WinXP.
Later thought: it may be relevant so could you also include the current VPS version you are at as well.
I uninstalled this version again about 5 minutes ago, booted into safe mode, used the uninstall tool
Which worked fine, rebooted, reinstalled Avast, and the same message appeared again
In selfdef.log it says the same as what it says in the previous pic, I posted.
And:
Write access to registry key \REGISTRY\MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICES\avast! Web Scanner\Enum\ denied. [C:\WINDOWS\system32\services.exe]
Thats what it says to all of the entries that were denied access
I am also using the English version of XP (with SP3).
The other forum I’m in some people didnt see this message about access denied. At the mo, only 2 of us have seen this error
And they’ve also installed SP3 (altho one installed SP3 AFTER this update).
My SP3 was slipstreamed with the XP CD, so was installed BEFORE I installed the latest version of Avast.
I got these messages while I ran an Ad-Aware Full Scan.
I simply ignored them since it is fine with me if avast! protects it’s own registry entries against access from other programs; and I had started the Ad-Aware scan manually.
I’m convinced that there must be some unresolved permission issues with the current build.
While I have not updated the machine I installed Avast on to SP3, I have what also seems to me to be permission issues. I wonder if the rootkit or self defense feature isn’t causing this, and I’d sure wish that the technicians at Avast would take these issues seriously. I would think it unlikely that other users who have no such problems will be able to solve issues that might be registry related.
These messages do not reflect any permissions problem. They simply represent cases where the avast self protection module has denied write access to avast’s registry entries.
Since the messages caused confusion (the user can do nothing about them) the decision was made for the production release (1195) to suppress the pop-up of the messages (even though they are still logged). It appears that the mechanism used to suppress the pop-ups is not effective for some users and I assume that the avast team will be looking at the issue.
not for me, after updating to XP pro SP3 with avast 4.8.1201, avast still works(manual scan) but there is a red circle at the bottom the notification area(no real time protection). Reinstalling avast doesn’t help.
Well we are on version 4.8.1290 so I would suggest a clean reinstall (see below) of the latest version. So it really is best to have the latest version of avast as there is little value in trying to fault find with an out of date version.
Have (or did) you another AV installed in this system, if so what was it and how did you get rid of it ?