Thanks for the Ip protection site. I read up on the ip blocking. I understand a bit more now. Yesterday the ip access attempts were happening while I was away from the computer, which is apparently a bad thing. Today they have only occurred while I have benn on the computer. I might close everything down and let it sit idol for a while and see what happens.

Disabled.SecurityCentre was detected by MWB yesterday during its scheduled run late at night. It was cleared. During the day I used Firefox only.

As an experiment I ran MWB's quick scan late in the day and found Disabled,SecurityCentre again. I cleared it, rebooted and the ran the full scan. Found nothing! I did nothing more, turned off all programs and went to bed last night.

What is your home page? Please note the address, and I can do an analysis.

Disabled.SecurityCenter is not an actual threat. It is just a change by malware, when it affects your system. The effects this has on your system are slim to nȯne.

Symantec Endpoint Protection, which I am guessing you still have active, correct? This is what is causing the entries in the Registry to change back.

My script above was a total fix for the Security Center in Windows XP. Since the result is the same, it means that Security software, like Symantec, will disable Security Center. It does this because it has its own security center, so using Windows Security Center would be pointless. Malwarebytes' Anti-Malware continually detects it, but can be ignored. Go ahead and add that detection to your ignore list in MBAM, and you should not get prompted about it.