Sorry. My stupidity…
Anyway, there is always the possibility of being using a second computer ;D
Tech,
your point about WinSock may be valid, but I note that the log posted by attfuzz suggests that a valid servers.def file was on the machine with 34 servers in it (which is the count in my file too).
Note that the log also reported a failure to try to re-download the servers.def file as well. It seems this user cannot connect to download19.avast.com - which I can connect to without problems.
As you will see from my posts in this thread and others I have had these (and more) problems myself. This has solved the problems for me on both my laptop and my desktop computers:
Download and run the Alwil uninstaller to uninstall Avast. (Better than the Control Panel one).
Reboot into SAFE MODE.
Reinstall Avast and then reboot normally.
This has solved my problems OK - inluding the error “Not enough user rights to continue.” A few folks on here have insisted that I did not install originally with Admin rights - even though I am positive that I did - and that is why I got the user rights error. Anyway, I don’t know what caused the problems but what I did above certainly solved them for me.
Well, the post was from the PC that is having the update problems. It’s running Windows XP x64, 3200 AMD, 2G RAM, X700 ATI, and using the on-board audio and Gigabit NIC. Internet and everything else is working fine, including online gaming. That was just a small portion of the setup log file. I can post a larger one if that is alright. When going through the update process through the system tray icon on both the defs and the program, neither one work, get some type of timeout error or something. I guess if all else fails, I’ll try Jim’s solution with the uninstall and then install in Safe Mode. But I thought in an earlier post, that that was just a temporary fix.
In fact, seems that we have an auto-update problem…
http://forum.avast.com/index.php?topic=17578.0
Other users are experiencing the same.
It’s working perfectly on both my machines since my reinstalls as above. Several days now on the laptop and since yesterday on the desktop. Updates at least a couple of times each day.
JimTheMuso had different problem with user rights - ProcessGuard was blocking access to registry that avast needs to access for program update. So in this case, starting in safemode helps.
Unfortunately we cannot reproduce problem with error with code 0xC0000005, so there’s no solution yet. You can try to download full setup from our website and use it to update, or contact me by email.
Yes, true but I was also getting the update problem with error
0xC0000005. The reinstall in safe mode fixed this problem on both machines also. I understand the problems may have been separate ones (although I still feel they were connected) but it still fixed both problems on both machines.
I tried Jim’s solution with the uninstall and then reinstalled Avast in Safe Mode. It did the auto update after the initial install and I was also able to manually update it through the system tray icon. So, as of now, all seems to be working. I’ll check the auto thing tomorrow and report back.
I also encountered this error with Avast 4.6.731 not being able to update properly. Auto-update and Icon Tray update both end up displaying a message on a red background saying something to this effect: “An error has occured while updating.”
When I try a manual update by downloading the VPS from avast.com, it crashes and shows what everyone else has reported.
On the other hand, if I uninstall the program, reboot, then install avast AND update without first rebooting, then I can install the VPS manually. Unfortunately, even after I manually updated, once I reboot and try updating using the Icon Tray, the same problem persists… Perhaps this might help the debugging team? Something is happening between installation and reboot which shouldn’t be happening.
Matrix_Peter, will this help?
http://forum.avast.com/index.php?topic=17433.0
http://forum.avast.com/index.php?topic=17379.0
Oh, sorry, I didn’t specify what crashed. I meant the VPS updater, and not Avast! itself.
The VPS I downloaded was the one from here:
http://www.avast.com/eng/update_avast_4_vps.html (Date: 24.11.2005, version: 0547-4)
Either way, I managed to update Avast! for now. I’ll just have to wait until the next VPS to come out in order to see if the same bug/crash will appear.
If it helps, here’s an attached picture with the error that the auto-updater produce (The zonealarm window shows that I did allow outbound connections by Avast! Updater).
I followed Jim’s instructions ‘minus’ the installation in the safe mode. Guess what! the auto-update doesnt’ work. :-\
I guess there’s something wrong with the program itself when you have to install it in the safe mode for it to work!!
I observed one thing though… After installation (in the 6 day evaluation mode) the program updates itself perfectly, but after you add the regstration key it goes all kaput.
I went back to my old avast (.691). too many restarts! >:(
internetstatic
Have you tried re setting all your permissions in your firewall?
Zone alarm is a pain when it or something else updates because it doesnt always remember settings . can i suggest you try that next time you do update the program if in fact you are using ZA.
just remove the program permissions from the program page indicated above then update and grant them again.
good luck 
Cloussau,
I do not want to fault you but there is, it seems to me, some logic lacking in your suggestion.
When these users installed the new release of avast, they, as I did, had to update the program permissions for all the changed avast components in ZoneAlarm. Frankly , I am beginning to think this old story blaming things on forgotten permissions in ZoneAlarm is an urban myth. It is not something I have ever seen in my use of that product.
Anyway, if it is ZoneAlarm at fault, why on earth does not ZoneAlarm cause exactly the same problem when they reinstall 691, as many have done and find the avast update problem has disappeared.
I have yet to see one report in this forum of someone experiencing this problem, who then chose to revert to using 691 and then continued to experience any difficulty.
I hope that the avast team is working more closely with someone experiencing this error than we are seeing reported here.
I am sure that most of the user base have updated without problems, but there certainly seem to be quite a few users reporting the same issue in several threads who must be feeling rather frustrated.
Perhaps the avast team can provide a status update on their current take on this problem.
I have one probleme…
I install v.4.6.731 e i inside the key
But i dont cant update the vps
I have the error:
In red box: "An error has ocurred while attempting to update!
If i update offline (file of site), i have the error: “Can`t install vps update. Please, report following errorcodes:
Ver:4.6.731
SI: 0x000000005
ST: 0xC00000005
LE: 0x000000000.”
What i do to this update work???
I have Xp sp2
firewall sp2 “open port” avast…
Further to the above - I don’t have Zone Alarm. I just use the XP firewall - and ProcessGuard was disabled during all these problems. This is a good product and the guys who develop it do a good job but sometimes they are like politicians - deny everything and keep wriggling until caught.
ProcessGuard acts at very low level in the file system. Even disable, a lot of troubles you’ll see with antivirus, firewall, partition operations, etc.
Which product? avast or ProcessGuard?
Kiyh33, did you try to update at a non-administrator account?
Did you use the Trial version before the Home?
Will this procedure help?
http://forum.avast.com/index.php?topic=17433.0
http://forum.avast.com/index.php?topic=17379.0