I see your posts concerning the different problems due to the upload of viral basis , i confirm this problem i tested 4.6 731 and i go back 691 and i’ve the information ( a popup red) that explains ’ problem to upload.’
27/11/2005 10:53:23 FB 3548 Function setifaceUpdatePackages() has failed. Return code is 0xC0000005, dwRes is C0000005.
27/11/2005 14:53:52 SYSTEM 1344 Function setifaceUpdatePackages() has failed. Return code is 0xC0000005, dwRes is C0000005.
27/11/2005 14:53:53 SYSTEM 1344 An error has occured while attempting to update. Please check the logs.
27/11/2005 15:39:39 FB 1864 Function setifaceUpdatePackages() has failed. Return code is 0xC0000005, dwRes is C0000005.
27/11/2005 15:39:46 FB 1864 Function setifaceUpdatePackages() has failed. Return code is 0xC0000005, dwRes is C0000005.
27/11/2005 15:40:08 FB 1864 Function setifaceUpdatePackages() has failed. Return code is 0xC0000005, dwRes is C0000005.
27/11/2005 15:40:10 FB 1864 Function setifaceUpdatePackages() has failed. Return code is 0xC0000005, dwRes is C0000005.
That’s samething which others persons
I’ve tested with 4 versions pro and home and i found the same problem , i’am sure that’s a server problem chez Alwill , i don’t changed my firewall and windows XP don’t refuses to open the connexion for it.
Which firewall are you using?
If it’s a third party, each avast installation will change the programs that access the Internet and each time you should allow (or change) them into the firewall settings.
Just for the record, I am having the exact same problem with the exact same log code:
11/27/2005 6:06:08 PM SYSTEM 652 Function setifaceUpdatePackages() has failed. Return code is 0xC0000005, dwRes is C0000005.
11/27/2005 6:06:10 PM SYSTEM 652 Function setifaceUpdatePackages() has failed. Return code is 0xC0000005, dwRes is C0000005.
11/27/2005 6:06:10 PM SYSTEM 652 An error has occured while attempting to update. Please check the logs.
This error occurs several times throughout the day as Avast attempts to update. Each time, I get the little red pop-up in the corner indicating there has been a problem updating. This only started occurring when I updated to 731. In an attempt to solve the problem, I’ve tried uninstalling and reinstalling (with necessary reboots), and that has been unsuccessful.
I have no third party firewall other than my router, and I have Windows Firewall off. I have no changed the configuation of any of the firewalls, and Avast has always worked in the past. I’m pretty sure the problem lies with the server or the updated version.
At this point, I’m just going to turn off automatic updates until the problem is resolved.
There is a large thread on on this issue which is affecting a fair amount of users but not all. There you can see what is being done to try and resolve this issue and hopefully that will be where a solution is found will no doubt be published.
http://forum.avast.com/index.php?topic=17501.0
It is not until the latter pages of the thread that some are involved in testing to help with a solution, but it is likely to give you a good idea of what is going on.
Can you do manual updates, some have not been able to do either?
I don’t have a firewall installed only Windows Xp Pro with its firewall , but when a program tries to open a port or open my internet connection, i receive an information to allows or not this procedure.
Moreover , i used the version 691 when i pass to 731 the problem appears with a red popup and next i tried to go back at version :
4.6. 691 Home / Pro ------------> error
4.6. 731 Home/ Pro-------------> error too
Due to, the fact that i not have changed the configuration of the firewall this problem cannot be in my configuration.
Perhaps this last version installs a file or modifies a register key that generates this problem when you reinstall old versions.
The only possibilte that not all persons a touched by this problem is their Windows are not Windows XP pro with SP2 , the SP2 was not installed by all customers of avast in everyone version.
I hope, you can released a patch to resolve this problem or another procedure.
Hi and welcome Fred77,
If as you say you get an alert for every attempt that a program makes for internet access which you have the option to deny. Can you tell us which program that is that controls this behaviour?
XP’s firewall doesn’t provide full outbound protection, so you would be advised to seek a solution that does. Perhaps the program that is poping-up the messages whatever that is?
Something other than XP’s firewall is acting in a way that a firewall could by checking new program attempts to connect, what is that?
So are you saying that you had/have the same problem as you indicate above? If so then the update to 731 hasn’t brought this on as has been the case for many others. What is needed to be done is identify the problem that existed in 691 and if we can eliminate that perhaps that would also be the case in 731?
You don’t have to change firewall settings, if a program update occurs then it has changed and would usually challenged by a firewall (not XP) or some form of program behavior inspection.
If you check my signature you will see I’m running XP Pro SP2 fully updated and no problems.
Alwil are you can be assured trying to resolve this issue as they have always done in the past. However, as I mentioned above, if this problem existed in 691 then a patch for 731 may not resolve that problem.
Have you read my post earlier today in another thread:
"
Hi all!
I have been using Avast for several years and never had a problem.
But in the beginning of November Avast let me down. I was not able to update vps neither automatically nor manually as many in this thread have already stated.
The difference is that I at that time was on version 4.5.xxx.!
I noted somewhere in the fora that a poster mentioned his last successful vps-update dates and they were exactly the same as mine.
I know it is a radical suggestion, but perhaps something has gone wrong with the updates-files. By coincidence this occured at the same time as the new release.
Well, for me it looked as if I could not get in touch with any of the thirty+ servers, but I was able to ping them.
Anyway I was not able to update manually or automatically, but downloading the whole set of defs from Avast site did the update. I thought everything was ok, but was still not cabable of normal vps updating.
I ended up uninstalling and installing 4.6.731 and since then everything is fine.
"
This should indicate that this is not a 731 problem(only).
Not sure who this is addressed to, but it is always better to contain the information in the same thread as you have
Those who help here are reading many threads in the course of the day, even if they could remember reading your earlier post. There is no way they could hope to remember the content.
Since this problem only started being noticed in a big way was when people updated to 731, I would suggest that it is entirely related to the 731 update. Yes there are likely to be other reasons why someone can’t update and that could show in any version. When we see this kind of activity related to being unable to update they can’t all be having firewall problems with blocking. Then we have to look at other things and coming so close on the heals of a program update, that has to be considered a contributary factor.
The thread you posted in firstly was the right one as that is the one with most information on this issue. For some uninstalling and reinstalling hasn’t rectified the problem. There are also many others who it isn’t effecting at all, so it isn’t easy to pin down.
In Norway we say something like this in English: " If you are not finding what you are looking for, you are looking the wrong way".
I discovered this issue 11 of November but when I ghosted my PC back to 30 of october the error was there too without me noticing it. If I had updated to 731 11 of November I would have blamed falsefully the update for the error.
Anyway, good luck with investigation and good night.(if in Europe )
)