Author Topic: So the update worked, but now it says my virus definitions are outdated  (Read 2151 times)

0 Members and 1 Guest are viewing this topic.

Pokesaver

  • Guest
even though when I try to update, it says up-to-date.

Any help?

jtl999

  • Guest
Re: So the update worked, but now it says my virus definitions are outdated
« Reply #1 on: October 04, 2012, 05:00:42 AM »
I would just wait until tomorrow. For now it appears to just be an cosmetic bug.

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89053
  • No support PMs thanks
Re: So the update worked, but now it says my virus definitions are outdated
« Reply #2 on: October 04, 2012, 01:53:24 PM »
As I said in another topic about this:
Quote
I think that they have pulled the VPS 121003-2 version so the update check doesn't fail as it did before.


That is why it is showing 121003-1 as the latest update when you try an update check. This gives them time to find the reason for the problem in the bad VPS update without the problem 'for users' spreading as people update. So those who managed to get round the problem of the bad VPS they will still see version 121003-2 as their current version.

So I would expect an update later today version 121004-0 to be released, that should fully resolve the VPS version number mismatch. But having pulled the bad VPS version from the update servers, the system should be working.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.3.6108 (build 24.3.8975.762) UI 1.0.801/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security