http://groups.google.com/group/micr...ta.general/browse_frm/thread/2a1445852786e5e1
I have seen it's leftovers keep a system from booting at all as well as
corrupting it in ways that prevented one from updating. Same for McAfee.
These are *suites* (as given by the OP) which means their firewall *can* and
*has* in the past stopped people from updating because it would not allow
some update component to do its job. ;-)
If the OP follows the advice given, they will have a better performing
system with less problems and most likely updating from Microsoft's site.
The suites are generally bloated and overkill - even if they have done a
better job and taming the prior resource hungry apps - most users will never
use 1/10th of the features in such a suite and the chances of something
going wrong when it is not understood is pretty high - and the chances of
fixing it when/if it does - pretty low. K.I.S.S. - always good advice.
However - since you have offered some start of advice - what is your
suggestion to the OP on 'looking for the real problem'?
I will quote from my post:
"I can't help the OP on this one, but I think he needn't waste time getting
rid of Norton instead of looking for the real problem."
As you can see, I had already answered your question in my reply.
He has, in my view, not given enough information to suggest a path to a
solution, since I don't, as I already said, consider Norton a sufficient
reason (or even just "a reason") for his problem.
As for your putting bold marks around "suites": please note that I did
mention above that I have (and do now) run Norton Internet Security, which
*is* a suite, AFAICT. I have run it on a few computers (more than I stated
above, actually) without ever having problems with Windows Update.
Of course, I've also run non-Norton AVs and suites without update problems,
including your recommendation of Avira, plus AVG, AntiVir, MSE, and more
than I can currently recall.
NIS 9 & 10 do interfere with System Restore, but there is a setting to fix
that (turn off its self protection before initiating System Restore). I
usually don't remember to do that until after a System Restore has failed
:-(