Constant Updates

jvidal · 2014-04-12T18:09:19.000Z

Well, I tried the repair and windows started telling me to look online for an AV product and to enable windows defender. I rebooted, even though the installer didn’t prompt me to. After the reboot, windows was quiet, but the instup.exe process never showed up in task manager. So, i tried to update avast and i got the same result. No need to update, it’s up to date (140409-3 is NOT up to date). Also avast tells me that everything is ok, although my defs are 3 days old…
On my destop PC, avast won’t update either, it says that 140411-1 is up to date, which isn’t.

DavidR · 2014-04-12T18:30:42.000Z

It it an out of sync condition, it isn’t that your defs are three days old, just the fact that the UI display isn’t correct as I mentioned; out of sync being what is displayed differing from what is installed. You could also check/confirm the defs sub folder - C:\Program Files\AVAST Software\Avast\defs- that should show sub-folders for the virus definitions (same numbering style for the folder name/defs version).

If you don’t see later defs sub-folders (see attached image), you could try downloading the full virus definitions database as mentioned by essexboy in Reply #3 above.

jvidal · 2014-04-12T19:03:11.000Z

downloading and installing the offline updater doesn’t fix anything, avast still won’t update automatically…you only get the latest update, but the problem persists.
looking in the def folders, this is what i see
14040903
14040903_stream
and a bunch of stream updates upto
14041201_stream

DavidR · 2014-04-12T19:25:58.000Z

Something that just came to mind, do you have avast set on silent/gaming mode ?
If so that can stop the virus definitions update.

Well you are getting the streaming updates, which is good (not totally out of date), are you getting any errors displayed when avast does its virus definitions auto update ?

If not, it could be time to try a clean reinstall on one of the problem systems and see if that resolves it.

Download the latest version of avast, 9.0.2016 (see below for download locations) and save it to your HDD, somewhere you can find it again (if you didn’t save your last download). Use that when you reinstall.
Download the avast! Uninstall Utility, avastclear.exe http://files.avast.com/iavs9x/avastclear.exe and save it to your HDD.
1. Now uninstall avast! - using add remove programs, if you can’t do that (as appears to be the case) start from the next step, reboot.- 2. run the avast! Uninstall Utility, it will request it be run from safe mode (and will handle the boot into safe mode), once complete reboot into normal mode.- 3. install the latest version, reboot.
  Note: save the copy of avastclear.exe so it can be reused as some users are reporting that after running it, it is self-deleting.

Download locations - You can download the full 9.0.2016 installer and it will allow you to update.
Free AV: - http://files.avast.com/iavs9x/avast_free_antivirus_setup.exe
Pro AV: - http://files.avast.com/iavs9x/avast_pro_antivirus_setup.exe
AIS: - http://files.avast.com/iavs9x/avast_internet_security_setup.exe
Premier: - http://files.avast.com/iavs9x/avast_premier_antivirus_setup.exe

jvidal · 2014-04-12T21:04:52.000Z

No, it’s not silent. I just turned on another PC, that I had just assembled yesterday and again, avast updated to same version it has installed.

I thank you for your suggestions, but it seems you’re not getting the picture. Now I have THREE pcs experiencing the exact same issue. One is a freshly built PC, OS just installed, Avast just installed, makes no sense to do a clean install, don’t you think? It is EXACTLY what has been done, I have just installed it on a newly installed OS.

Just give up an assume it’s a server issue that needs fixing ASAP.

jvidal · 2014-04-12T21:17:30.000Z

And again, now my main PC “updated” to v 140411-1, which is the same I have installed. Pop-up and everything…

jvidal · 2014-04-12T22:05:49.000Z

Ok, I think I know what’s going on. I fired up a VM I have, running xp x64 + Avast 8. Avast updated normally to v 140212. Then I installed avast 9 over avast 8 and rebooted. After rebooting, avast updated to v 140409-3 instead of today’s update.
So, it seems that for some reason, avast won’t update to anything newer than 140409-3, that’s why it doesn’t update if you have a newer version (installed via the offline updater, for example).
Of course, trying to update gives the same result: It’s already up to date (which it isn’t!)
THIS IS DEFINITELY an issue with the v9 update servers.

midnight · 2014-04-12T23:13:55.000Z

My last popup shows current version 140412-1. I’m using Avast 2016.

jvidal · 2014-04-12T23:31:49.000Z

doesn’t update after 140409-3 for me…

system · 2014-04-12T23:37:55.000Z

jvidal post:7:

There’s something else wrong. I’m seeing the same behavior on my laptop. avast is updated to 140409-3, if I click update, it tells me that it’s up to date.
No way i have the exact same problem on two diff. computers, its’s obviously an external issue, servers or something.

system · 2014-04-13T04:37:40.000Z

same problem, it is not my pc, the server is

http://i.imgur.com/pt5Itgm.png

midnight · 2014-04-13T11:44:09.000Z

My last update. If it’s a server problem I wonder why it hasn’t been fixed?

jvidal · 2014-04-13T14:07:59.000Z

Poblem persists, tried to update and avast says that v140409-03 is up to date.
PLEASE SOMEONE FIX THIS!!!

system · 2014-04-14T04:38:37.000Z

I just want to know if an error notification or actually still using update 5 days ago

skinnypops · 2014-04-14T11:35:32.000Z

i’m seeing current update 140414-0. southeast US

jvidal · 2014-04-14T14:28:02.000Z

Problem seems to be fixed today, finally!!!
I opened my laptop and it updated to v 140414-0…I have yet to check my other PCs

thx!!!

jvidal · 2014-04-14T14:34:03.000Z

My main PC seems to be ok too.

jvidal · 2014-04-14T17:17:03.000Z

Tested my VM and the other PC i had, all updated OK.
So it’s seems the problem is solved.

jvidal · 2014-04-24T01:35:32.000Z

Crap!!!
The problem is back!!!
PLEASE, devs, FIX IT!!!

thx!

jvidal · 2014-04-24T14:38:43.000Z

Problem is still there.

Announcements