locked
Live OneCare Update has taken over our workgroup and slowed us to a halt RRS feed

  • Question

  • We have 6 Dell Dimensions running XP Pro on a network, as well as 4 Dimensions on a network at another location 65 miles away. We have installed Live OneCare on all of them. Last week, all of the PCs updated and we have been sunk since then. All PCs slowed to a crawl, and Task Manager showed 100% CPU usage 24x7! I had to disable OneCare on most of them to allow the people to work on them. All 10 PCs showed up in the OneCare Circle (even though it says up to 3 PCs to a circle) and all the PCs and printers were showing up, Our router showed the PCs at our other location as part of our workgroup ( we don't have a domain, just 2 workgroups ). I removed the faraway PCs from the circle, and now they are not running any antivirus or firewall. If I re-install LOC on any PC, the One Care Circle begins joining them together, even if they are designated HUBs or not designated as HUBs. The process MsMpEng.exe shows 55,000+ K usage in task manager on each PC that is running LOC. Doing scans and backups takes 24 to 36 hrs per PC if all are running LOC. It appears that the OneCare Circle feature is taxing our resources badly, and the new LOC virus or spyware scan is running constantly, gobbling up what resources weren't being scarfed up by the the networking feature. How can we set each PC to run independently of the others?

    Tuesday, January 15, 2008 8:15 PM

Answers

  • See if this thread helps - http://forums.microsoft.com/WindowsOneCare/ShowPost.aspx?PostID=2008959&SiteID=2

     

    That thread addresses the CPU usage by winss.exe. MSMPENG at 55,000 is a little high, but that might be due to the fact that winss is thrashing. Normal msmpeng usage is between 25 and 60K, depending on what it is doing when you look at it.

     

    The problem is not the Circle feature, so hopefully the above thread is the solution

     

    I would see if you can get one machine locally working and then go on to the others and finally reinstall the remote machines.

     

    If that thread does not 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.

    -steve
    Tuesday, January 15, 2008 9:55 PM
    Moderator

All replies

  • See if this thread helps - http://forums.microsoft.com/WindowsOneCare/ShowPost.aspx?PostID=2008959&SiteID=2

     

    That thread addresses the CPU usage by winss.exe. MSMPENG at 55,000 is a little high, but that might be due to the fact that winss is thrashing. Normal msmpeng usage is between 25 and 60K, depending on what it is doing when you look at it.

     

    The problem is not the Circle feature, so hopefully the above thread is the solution

     

    I would see if you can get one machine locally working and then go on to the others and finally reinstall the remote machines.

     

    If that thread does not 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.

    -steve
    Tuesday, January 15, 2008 9:55 PM
    Moderator
  •  

    I heard of someone fixing this WINSS/Services.exe 99% CPU issue by starting the Network Location Awareness service.

     

    I also heard that sometimes the PNRP (Peer Network Resolution Protocol) can sometimes cause this error when it's started and installed.  Try disabling this service to see if that helps.

     

    hope this helps!

     

     

    Tuesday, January 15, 2008 10:13 PM