Day two with both SiteAdvisor installed and Net Guard enabled, and still no errors.
If anyone wants to experiment, my suggestion is to try this:
I've gone from having the error occur up to 9 or 10 times per day, to having no errors for the past two days.
The sequence that I've listed is the exact sequence that I've followed over the past several days, except that
in my case each "Reboot" was really a "Reboot and wait a day or more".
The only difference between this and my "original" install is that originally McAfee (with Net Guard enabled)
had been installed for months before I ever installed SiteAdvisor, and SiteAdvisor was installed WHILE Net
Guard was enabled.
Well, nevermind about the installation order making any difference. Moments ago I had the error occur again.
Immediately after the error I disabled Net Guard once again. Then I came here to report....
Put this on here since there are too many different topics already. So my Total Protection just updated this morning on April 26 to the following:
Security Center Build 11.0.669
Virus Scan Build 15.0.300
Firewall Build 12.0.351
All builds have the April 26th date.
IS THIS THE FIX????
Good job WS6571, altough the sad end !
By the way, error returned with a McCafee update ? May be only a (dot)dat update.
In my case no errors since SA uninstalled, I'll keep my PC that way.
Last February I posted the following...
I have been experiencing the svchost pop-up for months. I followed quite a few of the suggestions here to fix the problem. Some seemed to work for a week or so but the problem always returned. Three weeks ago I uninstalled McAfee SiteAdvisor. No more pop-ups since.
OS Win XP Professional SP3
McAfee Security Center 11.0
McAfee Virus Scan 15.0
McAfee Personal Firewall 12.0
One solution that seems to work.
It is now April 14, and still no repeat of the error. Also, as reported earlier, I still have NetGuard active.
OK seems SA is the issue for some I have it installed on my XP box and it is not causing issue as far as I see.
They do have a feel for what is causing this issue and need to schedule release of the patch with a scheduled patch download. When this will happens I am not privy to.