Finally "real" answers
. Not because some of the answers are saying things more or less in the same direction I do. That's not my point, at all.
From my point of view, each and every answer in this topic is correct. There is (almost) no contradiction.
The idea of "starting all over from a clean install" is always tempting. It "seems" to resolve the
users' problem. Generally speaking, it does. But in this case in particular, I think it would only
temporarily deal with the
symptom, not the real problem.
Just to make it clear, my particular system would be updated if only I would "accept the temptation" of
manually updating each time.
It seems that I may not have been clear enough in a specific point. I actually
was following the releases closely, just as other users mentioned here in this same topic.
My particular case is not of a user that did NOT know that a program update was available, although I guess it could have been. Those other cases, if they exist, only mean that other users are simply using older versions of Avast, without knowing of the need / suggestion / recommendation / requirement to update the program.
So, the only difference between my case and all the other users posting here is that I have ( had? ) enough patience so to not click in the manual update possibility,
for months.
The only contradiction I have read here, if it could be called as contradiction (but I'm not so sure it can) is that, for the devs to debug this problem, it was suggested (by a user in this same topic) to try manually updating, and only
then, maybe someone can help in the debug process.
If I indeed manually update, as all other users do, we can't actually debug the "update notification" problem.
Since we don't really know what's going on, and the current alternative for me is to "clean and start over", I'll manually update first to the current stable version (as I already mentioned before in one of my previous posts in this same topic I'll do, before trying the clean install option yet once again).
If this is actually a "non-issue", and the current stable version has no problem, then I'll see a notification update in my tray area next time a new stable release is published
.
If, for the next program update (or, say, a couple of weeks later, after the official release), my situation doesn't change, then my HOPE is that several of the users participating here in this topic can refuse the temptation of manually updating, so to actually test the notification function, and really debug it.
In case all other users here will receive the notification in their tray, and I keep "waiting", then I'll understand that the problem is only mine, and I'll do (once again) a clean and complete uninstallation and installation from scratch.
In either case, only
THEN I'll set this topic as "resolved". I just wish/hope that "my" problem will disappear together with the program's notification problem, if there is one.
