Dammit, I had my attention divided, and my full response, although quoting your post in this thread, ended up being posted as a new thread through the magic of a glitched submission, inadvertently, here:
https://forum.avast.com/index.php?topic=106630.msg848173#msg848173So I had to give it a fitting title and all, and let it stand.
Well, I made some general points in it, so hopefully it stands on its own legs (but maybe I should edit it and transfer the part that's my reply to you, and this particular update issue and version numbers discussion, back here, into this post, for what it's worth.
Right, then, here it is, the relevant bit:
@iroc9555: nah, not an isolated issue, you're not alone -- same thing happened here (and others).
I didn't mean the "I can't update Avast!" deal. I know it is a problem Avast! is working on. I meant if you, or any one, had already 121003-2 and Avast! by itself downloaded the whole VPS, and now is saying it is not updated. You need to repaired Avast! to go back to 121003-1 that it is the correct VPS. There are members who still have VPS 121003-2 shown as correct and without problems.
I realised that, Iroc. The answer is still yes, though. To be honest, once I saw there was a problem (and suspecting the latest virus definition package to be at fault), I immediately began to go through the whole song and dance, all the usual procedures, step by step, and separately (instead of wisely and patiently waiting 24 hours or so, as much wiser and level-headed
Bioruffo had suggested).
By that, I mean manual online update, followed by full distributable download offline update, followed by repair, followed by normal uninstall and reinstall, followed by another uninstall
and full removal via the Avast removal tool and another reinstall, then the same procedure in safe mode, etc.
In the course of all that, I did encountere the problem you referred to, thrice, and using one or more of those procedures, so have others, here and elsewhere (not members of this forum -- till now, neither was I -- and not likely to post, themselves).
So I had 121003-2, and 121003-1 -- right now, I'm back to 121003-1 (still listed as latest as of few minutes ago, last I tested again the update), and staying there, obviously, till the new package, glitch-free hopefully, is ready.
In any case, like I said before, it's not the glitch and possibly bad VPS that rankles with me, but that there was no official word, and still isn't, last I checked.
