manual update problem when set to auto update

[Snagglegrain]

Okay, I'm patiently waiting for this one computer to auto update to 100406-2.
My other pc installed it about half an hour ago.
Keeping my fingers crossed.

Edit: Aha!  I didn't have long to wait.  Virus database has updated.   

[bong2x]

ok make sure that you have the same as the picture. and and refresh your net connection

edit: sometimes mine i set it in 360min but its originally 60 its fit in my dial-up somtimes. best fit is 240

and better also to auto detect

[DavidR]

The minimum setting is 120 minutes for the update check, anything lower is ignored I believe.

[bong2x]

ah ok, thanks DavidR

[YoKenny]

@ Snagglegrain

Go to PROFILE then Modify Profile then update your Signature: with information like my signature as this helps the helpers offer pertinent advice.

DavidR an avast! Überevangelist has his system's information in his signature. 

[Snagglegrain]

I'm glad too that it all appears to be working fine, though personally I would have let the auto update do the download for further confirmation that the primary update method works.

Auto update appears to be working fine once again.  This v5.0.462 sure is a nice improvement over v4.8. 

[Snagglegrain]

This issue continues to visit me.  Today on my other computer 100409-0 is the last update, even though 100409-1 has been out for many hours.  An attempt to manually update does not result in a message saying "Already up top date", but instead shows the amount of time taken, like 27s, without any of the other usual details like Server or Downloaded files, etc.

I suppose I shall try a repair, as DavidR has previously suggested.  But I wonder how common this update hiccup condition is with v5.0.462? 

[Asyn]

You might want to try the pre-release version 5.0.492...
http://forum.avast.com/index.php?topic=58183.0
asyn

[Snagglegrain]

A reboot triggered an auto update to 100409-1, which doesn't fix my little problem of manual updating not working when an update is available.

@ asyn... thanks for the suggestion.  Have you read on a changelog that 5.0.492 deals with this issue?

[Asyn]

@ asyn... thanks for the suggestion.  Have you read on a changelog that 5.0.492 deals with this issue?

It's 5.0.499 now, just received the update...
And no, haven't read about it, am not sure, if it's a real problem after all, as the update servers need some time till the receive the update for distribution, so maybe it's just about a little patience...
asyn

[Snagglegrain]

It's 5.0.499 now, just received the update...
And no, haven't read about it, am not sure, if it's a real problem after all, as the update servers need some time till the receive the update for distribution, so maybe it's just about a little patience...
asyn

Think about it.  Two computers on a home LAN.  Both running avast 5.0.462.  But with pretty much the same software and hardware, sharing an internet connection.  One computer auto updates to 100409-1, and many hours later, the other has not.  Based on my experiences the other day, one did not update until the next day, i.e. it missed the second update of the day.  Today it only updated because of a reboot.

Yes, patience is a virtue, but I'm not seeing it as a solution to this failure to update condition. 

[Asyn]

Yes, patience is a virtue, but I'm not seeing it as a solution to this failure to update condition.  

I see... Well it could be related to your shared connection on a home network, but let's talk again after you updated to 5.0.499, maybe it helps solving your problem and you won't have to wait any longer...
asyn

[Snagglegrain]

Updated to v5.0.507 and the issue is not resolved.

Even though avast! updates with each new date, it will not manually update after that when a new definition version is available during the day.

As of right now, current version is 100415-1.
That version has already automatically installed on one of my computers,
but the other one still has 100415-0.
When I attempt to manually update, all I get is:
"Already up to date (current version 100415-0)".

I have tried a repair, and rebooted, to no avail.  Sometimes the reboot triggers a new update, but not this time.

What's left?  Uninstall and reinstall, I suppose.

(This issue did not exist when I first updated from v4.8 to one of the earlier v5.0 builds.)

WinXP, SP3

[Asyn]

As avast has many update servers, it will take some time till all can offer the new updates.
So eg., your first machine connects to server xx1 and the second to xx45, it can happen that one gets updated and the other doesn't.
So no repair, reinstall, reboot will help, only waiting will help...
asyn
 

[Snagglegrain]

I think you're wrong.

What you're overlooking is that while that computer isn't able to manually update for many, many hours in a row (like 18 hours yesterday), it also isn't auto updating, which avast! is configured to do.

So, one computer auto updates and manually updates just fine, and the other won't auto update or manually update all day long when a new update is available.

Exceptions are, as noted, sometimes a reboot will trigger the update, and a new day always triggers an update.

This is not a server problem, and telling me that "only waiting will help" contributes nothing.