Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Yellow-Cab-Driver on April 13, 2005, 08:01:21 AM
-
Hello! Avast was a fine programm until yesterday: the automatic update started and after a while it said: (translated by sense from german version) problem occured: the update file was corrupted.
The definition stayed ("about dialogue") "0515-0", but when i start the update manually avast says, it is alreasy "0515-1" and nothing has to be done?! Whats the matter with this. Can anyone help?! Did it update or not?!
(The avast running on my friends PC updated correctly, but had older signature files than 0510-0 before hand). ???
-
Hi, YCD!
Actually, the Avast! Update Version is 0515-1. Tried to run again? Maybe it was only a temporary failed connection with the server for exagerate traffic volume. If your problem persist, post again.
Buona giornata=guten tag ;D
-
Yes, i actually tried to re-run the update manually several times!
Avast always said, everything fine, already up to date with 0515-1 no need to update. But when I let avast show the definition version it says it has 0515-0 in use!!! So what definition are used by my avast?!
-
Strange thing... Your control of installed version is by right-click on the blueball->about Avast?
-
Yes, that's the way i verify the actually installed version!! Strange indeed!
Any suggestions?
-
I've sent a PM to Igor for help you: surely you'll help you in a short time. I'm sorry!
-
Waiting for Igor's reply, I ask:"Have you tried to open the Avast Registry Visualizer? I don't use English or Deutsch version and on my screen I see "Visualizzatore Registro di Avast!". You know how to open it?
-
Well, i am not at my home desktop to check this possibilty. I would try in the evening. What can you do with this visualizer?!
-
Well, i am not at my home desktop to check this possibilty. I would try in the evening. What can you do with this visualizer?!
If you see the same message (underlined in red) your version was installed successfully. But we don't find why you don't visualize the exact number... :-)
-
Yes, great, thanks for your screenshot, the window above i remember, i know, how to open it...i will check it in the evening time...then i should know which version is installed! Meanwhile waiting for Igor's answer!
-
Ok. Sorry for my incomplete helping :-[. In the evening I will try to come on this post because I'm curious to know the end of this little enigma! Good work! :)
-
Well i just checked the entry as suggested. It showed the following:
12.04.2005 19:43:24 SYSTEM 1904 Info from aswChestS: chestStop.
12.04.2005 19:42:22 Alexander 548 Library Setiface.dll was successfully updated.
12.04.2005 17:28:12 Alexander 548 Library Setiface.dll was successfully updated.
12.04.2005 17:27:59 Alexander 548 Library Setiface.dll was successfully updated.
12.04.2005 17:27:08 Alexander 548 Library Setiface.dll was successfully updated.
12.04.2005 17:26:06 SYSTEM 1904 Library Setiface.dll was successfully updated.
12.04.2005 17:26:00 SYSTEM 1904 Library Setiface.dll was successfully updated.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestCloseListLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestNextFileLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestNextFileLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestNextFileLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestNextFileLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestNextFileLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestGetValueLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestNextFileLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestOpenListLoc.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestAddSystemFiles.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestStart TcpIp=0 Lrpc=1.
12.04.2005 17:23:08 SYSTEM 1904 Info from aswChestS: chestInit.
But in the warning section there is the following:
12.04.2005 17:26:19 SYSTEM 1904 Function setifaceUpdateFiles() has failed. Return code is 0x20000011, dwRes is 20000011.
12.04.2005 17:26:19 SYSTEM 1904 An error has occured while attempting to update. Please check the logs.
Any idea?! What went wrong?
WHICH version is installed?! 1505-1 or 1505-0.
I wonder if i am protected anymore. Could the virus-db be corrupted by this problem, destroying protection?! Please help!!!
-
I wonder if i am protected anymore. Could the virus-db be corrupted by this problem, destroying protection?! Please help!!!
Don't worry... If a download fail, the last VPS will be there, working...
Just set the Update (Basic) > Details settings to 'Normal' (not silent) and 'Show update progress'.
If the update works, never mind, you're protected 8)
-
Ok, thats a relieve! :)
But what's wrong with my avast?! I am curious if the update to the next version 1505-2 or up will function...
Since the updates are incremental...could it happen that the information of 1505-1 will be missing because avast does not "notice" the "gap" (because it states using 1505-0 but does not update to 1505-1 because it thinks, its using it already?!)...very confusing... ???
-
But what's wrong with my avast?! I am curious if the update to the next version 1505-2 or up will function...
We're now using 0515-1 VPS version and not 1505-1...
Since the updates are incremental... could it happen that the information of 1505-1 will be missing...
Forget all the problems... Updates are incremental and intelligent.
All avast! will be at the last version. Update routines 'see' what do you have and what you 'should' have and update.
If you 'miss' an update, avast takes it and adds it to your update.
Worderful, transparent, perfect, secure 8)
-
If it really doesn't update, you might want to consider using the vpsupd file from here (http://www.avast.com/eng/update_avast_4_vps.html).
(http://www.avast.com/eng/images/download_img.gif) (http://files.avast.com/iavs4pro/vpsupd.exe)
-
To Technical: What you say seems logical. But my problem is: my avast obviously has no idea, which version of signature it is actually using: it says (about dialogue) it has 0515-0 but does not update to 0515-1 because than it thinks, it has already 0515-1 (says the update prompt!).
So it is hard for me to believe that everything is going well because i cannot verify what is really going on?!....you have an idea?!
-
To Technical: What you say seems logical. But my problem is: my avast obviously has no idea, which version of signature it is actually using: it says (about dialogue) it has 0515-0 but does not update to 0515-1 because than it thinks, it has already 0515-1 (says the update prompt!).
So it is hard for me to believe that everything is going well because i cannot verify what is really going on?!....you have an idea?!
I'll ask for more specific help... I don't know what's happening, why isn't the date saved into the About dialog?
-
Thank you very much..i am very curious for the answer...i would really like to have peace of mind again with using avast, because in total i think it is a great programm i don't want to stop using...
-
Have you tried a repair of avast. Add Remove programs, avast! Anti-Virus, Change/Remove button and scroll down to Repair, click next and follow. You need to be on-line to do this.
If I remember rightly someone experienced this out of synch update info and a repair worked.
Also when you right click avast icon, select Start avast! Anti-virus, what VPS version and date are shown there?
You can also try to update the VPS by clicking VPS version and Date line from here as well.
-
Thanks for your helpful suggestions.
I just went online again and avast updated automatically saying now it has 0515-3 and before had 0515-1 (remember: about dialogue and antivirus-program gui said always 0515-0 being installed and would not update).
Now all components say: 0515-3 installed, so everything fine and repaired "automatically"?! Can I forget the recent problems??? ::)
-
I think so, you can just monitor the situation and see if they come back.