Security center says Avast is out of date

[Splinter hell]

Today  when I logged onto my computer I got an alert from security center saying avast is out of date.So I immediately updated avast and it reported it is up-to-date and the vps file is 080117-0.

But even though Avast is up-to-date I still get the alert from security center saying Avast is out of date.So after 15-20 min.Windows defender suddenly appeared in the icon area, saying its out of date.So I immediately updated its definitions.Even though I updated the definitions, windows defender still says its out of date.

Any way to resolve this problem.

[Maxx_original]

do you use Vista as your OS?

[rassel]

Hey try this step.( Uninstall avast,restart,reinstall avast,restart) and remember you should download the latest avast program from the avast website. After you reinstall avast, it "might" says avast out of date and you should wait until there is a blue icon pops up(if there is no blue icon pops up, im sry i cant help you).  if im wrong ask for help from the pro

[oldman]

Check the system time/date. Right click on the clock, make sure everthing is correct.

[Maxx_original]

wait with any reinstall... it's better to tell us more first..

[Splinter hell]

My system specs:
*Xp pro sp2
*P4 2.66 ghz
*760 mb ram

Security software:
*Comodo firewall pro
*Avast home
*Windows defender
*PCtools Threatfi

[Lisandro]

Here you can find more info:
http://forum.avast.com/index.php?topic=23457.msg193534#msg193534
http://windowsxp.mvps.org/repairwmi.htm

If you are running Windows XP, Service Pack 2 you can use a single command to detect and repair a corrupted WMI Repository. To do so, type the following from the command prompt (note that the parameter UpgradeRepository is case-sensitive and must be typed exactly as shown):
rundll32 wbemupgd, UpgradeRepository

After running UpgradeRepository you can verify the results by looking ay the Setup log. If inconsistencies are detected and if the operating system was able to rebuild the Repository you should see information in WMI Setup log (%windir%\System32\Wbem\Logs\Setup.log)