Well, I don’t know, so please EXPLAIN, why I should repair Avast when it’s working well for me.
Perhaps I didn’t make my post clear enough. Perhaps these pictures will explain what I’m puzzled by.
Let me know if need any more information. Also, exactly what it is that I’m to repair, based on what you can now see in the screenies. EDIT: the last shot I just got as definitions were coming in so this completes my entire picture.
OK I am with you now, you still have V7 yet the update does not show V8 as it should
The update should be for v8.0.1483 there may well be a glitch in the update server
Oh yes, every major version deserves a clean installation, I often do the safe mode cleanup as well.
Whether I’ll go to v8 is still debatable in my brain
I was getting those updates also and I noticed last week that the update sounds had quit but the definitions did update. I have done a clean install of version 8 and all is well. This was on several installs XP, Vista and Windows 7 all work fine.
Joe
JoeS, thanks, but I’m still waiting for an official blessing of what it is we’re to do. A hit-or-miss installation scares me as it does many participants of this forum. Today’s situation continues this very sad, and unexpected from a great outfit like Avast, version confusion saga:
I think we may safely assume that Avast employees are aware of this anomoly in the internal UI program updater by now after all the posts about it! Why there is still no official word from Avast on what is causing it and/or any possible problems that could/might occur from using the programs internal updater in the UI or clicking on the blue update notifier pop up, (which also shows the erroneous non existant 7.0.1483 version), is anyones guess.
Updating by this normal method is what most average users would use ‘out there’ surely and therefore it should be dependable and deliver what it says it will with no unpleasant suprises. Is that too much to ask?.
