@
opus872, here is your own post:
Winver says it's build 6000, which I think is the original Vista, before SP1. Which is odd, since I've been using Windows Update regularly. I just ran Windows Update again, and it's not offering me SP1 or SP2.
It seems I wasn't clear enough, so I'll try to explain myself better this time.
The current valid version of Vista should be at least 6002, which includes SP2. Microsoft doesn't support Vista RTM/SP1 anymore.
I quote your own post here so you can understand my point. Even if you have your system for 3 years, it seems you haven't gone through the "Validation" process (or that you need to do it again, which is indeed plausible).
Only a "Validated" Windows will offer you ALL critical updates, including SP1 and SP2. Moreover, say you make a "Factory Restore" or install Vista anew using your original media, 3 years ago Vista was not SP2 yet. In addition, a new RTM or SP1 installation could offer you several Windows updates (with needed/recommended reboots) before offering SP2.
So, my suggested steps are still relevant.
I can NOT actually know if this is exactly the problem, of course. I only suggested a possible workaround, that MIGHT help, but maybe it doesn't.
A user having this problem doesn't really need to uninstall "all", nor needs to make a Factory Restore nor a Factory Repair. The suggestion would be to:
_ temporarily uninstall Avast (under Windows Safe mode);
_ reboot to normal mode;
_ in case Windows doesn't allow to do anything else but to "Validate", just follow the instructions to Validate it, and then reboot;
_ apply Windows update and reboot, and then repeat this step until there is nothing else to update;
_ reboot (yes, after finally Windows Update offers zero updates available, reboot once more);
_ install Avast again (and reboot accordingly).
This MAY not be your particular case, and you may have "automagically resolved" your problem (as you state in a previous post), but maybe this helps some other user with a similar problem.
I insist that Avast will "pay" for this problem, even in the case Avast is not the main problem (the original MS topic is currently a sticky, so "everyone" is currently reading about this Avast conflict). To be clear, I, in my personal system, have no way to know that Avast is the main problem, or that it isn't, but eitherway Avast should try to find a simple workaround or solution (MS won't do it, and Avast will "pay").
Apparently this is happening with newer installations of Avast 6 and Vista before SP2 - 6002 (or this is a BS campaign; who knows
).
@Avast Team:
A
possible check, during the first step of Avast's Setup, that Avast is being installed in a supported OS edition and/or version and/or build could be "wise". In case the system is "not enough" (in relation to suggested/supported requirements), then Avast Setup could display a "
recommendation" (I would NOT call it a "warning") specifying what "item" is "not enough", with 2 options: "Cancel Avast Installation" or "Continue with Avast Installation Anyway". (To be clear, I would never let Avast Setup to "only Cancel" the installation, but instead always give the user the choice to decide what to do). This is not a "solution", and may "scary" some users too, but at least avoids the "feeling" of "I hate Avast for wasting my time". The best for Avast would be to find what changed between previous and latest versions actually triggers this problem, and then adapt
.
