Windows XP Security Center can't be started

I asked for help with this last year, I have just ditched Norton and installed AVG Free Edition from Grisoft. So I thought I’d check on the Windows Security Center. I was not surprised to find it "unavailableâ€, so I followed the instructions above to restart it. NO!
I got this message: "Could not start the Security center on Local computer. Error 123: the filename, directory name, or volume label syntax is incorrectâ€. Any thoughts on how to cure this?

 

Try the following solution for XP/SP2 ... (see Download Wscfix.zip)

When you attempt to start the Security Center Service using the Services.msc applet, one the following errors may occur...
Error 1083:
Error 123: (your stated error)
Error 2:
Error 3:

 

Thanks for this suggestion, Dennis,. Have you any experience of this site/program? There are so many out there that I always feel cautious about running them. I know I can set a restore point before I do.

Another point: someone mentioned that Spybot Search and Destroy can interfere with the Security Centre. I do remember seeing it in the list for a scan and I didn't know what to do with it. Could I have caused this by taking the wrong action?

This an entry from Spybot's log:

--- Report generated: 2007-11-07 ---

Microsoft.WindowsSecurityCenter_disabled: Settings (Registry change, fixed)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wscsvc\Start!=W=2

 

Thank you Pete. Agree with BOTH statements. My preferred suggestions come from Windows BBS or MVP member sites ... always good stuff.

Some A/V's will do this. Norton AntiVirus (it's off because it was replaced by functionality in Norton AntiVirus.) has done this in the past. Do not know if it currently does.
Also infections may be involved. You may want to post here ... Removing Spyware & Viruses Windows BBS. Read the guidelines and provide required information.

 

Yes, I may try this alternative Forum

 

Hi TeenieB

Your POST #6 ...

I almost missed your response in post #6. You state you will try the solution provided in post #2 ... Did this fix the problem??

 

Yes, I've just run it and it worked! Let's hope it lasts; I've had it revert to "not available" on next startup in the past. Thanks for all help.

Teenie

 

Glad the fixed worked. Norton can be challenging when users prefer to remove from system.
Thank you for posting back.