Saturday, December 08, 2007 3:23 AMModerator
There are many threads in the forums for people encountering serious problems with OneCare not starting after the update to 2.0. The OneCare team is working to identify all of the causes for these problems and hope to have fixes available soon (no, I don't know when).
However, at this time, they have identified the following:
This issue could be caused if one of the following services is disabled or not running. The workaround is to enable these services :
- Terminal services
- Network Location Awareness
- Network Store Interface Service
- Network List Services
Go to Start/Control Panel/Administrative Tools/Services
Look for the above services in the list and change them to Automatic from manual or disabled and then start them if they are not listed as "Started."
Then, open a command prompt -
In XP, Start/All Programs, Accessories, Command Prompt
In Vista, type cmd in the search box at the Start Orb and then right click cmd.exe on the resulting list and select Run as Administator.
Type: Net Start WINSS
and press <enter> to start the OneCare service.
If this fails to resolve the problem, please contact Support:
How to reach support - http://forums.microsoft.com/WindowsOneCare/ShowPost.aspx?PostID=2421771&SiteID=2
If it fails to validate your subscription, select the option that you are using a trial or beta copy and you can proceed to email support without validation once you've signed in.