Virus defintions old

[Dynaheir]

Should I be concerned? It's at windows 7 and package for virus defitions are from today?

Like, I know last package is 201212-0....but then, why the message?

[Asyn]

Repair Avast:
1. Avast GUI -> Settings -> Troubleshooting
2. Click on 'REPAIR APP'.
3. Follow instructions.
4. Reboot.

[Dynaheir]

My thanks to you Asyn, you alwas help me when I ask around ^^

[Asyn]

You're welcome.

[MrToad]

I've tried the repair strategy twice on a win 7 laptop and still can't get the definitions to update. Any further suggestions?

[Asyn]

I've tried the repair strategy twice on a win 7 laptop and still can't get the definitions to update. Any further suggestions?

- Which Avast..? (Free/Premium)
- Which version/build of Avast..?
- OS..? (32/64 Bit..? - which SP/Build..?)
- Other security related software installed..?
- Which AV(s) did you use before Avast..?

[MrToad]

Win 7 home 64bit, Avast free latest version..did program updates that worked..not sure of number..I installed Avira to provide protection while Avast on vacation..haven't used avastclear..some how Avira works. I've had definition update problems on 3 other win 7 Pro PC's but they've resolved..one with the suggested repair strategy..the others with repeated attempts and restarts. Because it cut across multiple PC's..none of which had recent avast issues, I thought it might be a server problem at Avast.
I've used Avast for years...also have super-antispyware and cyberware ransomefree..but I've had these for years and they've always played well with Avast.

[alanb]

I have the same issue on Win7 Pro x64.  Tried several repairs/restarts & cold boots.

I noticed I have old subfolders (defs and streams) in the Defs folder: the oldest from 5th October - the same date in aswdefs.ini.

I wonder if a faulty def update was pushed for Win7 machines...?

[Asyn]

I have the same issue on Win7 Pro x64.  Tried several repairs/restarts & cold boots.
I noticed I have old subfolders (defs and streams) in the Defs folder: the oldest from 5th October - the same date in aswdefs.ini.
I wonder if a faulty def update was pushed for Win7 machines...?

Hi, download an run (as admin): https://install.avcdn.net/vps18/vpsupd.exe

[alanb]

Hi, download an run (as admin): https://install.avcdn.net/vps18/vpsupd.exe

Hi Asyn.  And this does what exactly (it's a leap of faith to run an unknown piece of software  )

I assume "what" it does should be pretty obvious from its name, but the .exe is almost as large as a full offline Avast installer. 

[Asyn]

That's the full VPS database and hopefully will fix your issue. Note, it's signed by Avast.

[alanb]

Yes, after I woke up I checked it out on the interweb.

Sadly no change.  After a restart and two reboots, all the redundant content of the defs folder is still there and so is the notification.

Thanks for trying though.

[Asyn]

- Which Avast..? (Free/Premium)
- Which version/build of Avast..?
- Other security related software installed..?

[alanb]

Hi Asyn.

Avast Premium 20.1.2397 (build 20.1.5069.562)
No other security software

And I am not willing to try the latest beta 

But - playing devil's advocate here - if I were to disable self-protection, delete all defs up to yesterday inclusive and edit aswdefs.ini to reference the first actual def update for today, how safe (or otherwise) would that be?

About Avast is showing the latest installed def as 201014-0, but the "outdated" notification persists.

[Asyn]

Update to the latest version (20.8.2432): https://forum.avast.com/index.php?topic=238421.0