Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.windows-xp    |    One of my personal favourites!    |    146,966 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 145,793 of 146,966    |
|    Tim Meddick to Pfsszxt@aol.com    |
|    Re: svchost.exe hog --???    |
|    02 Oct 11 00:26:00    |
      XPost: alt.windows-xp       From: timmeddick@o2.co.uk              You don't say how much RAM your system has installed... I mention this       because it has been documented that there is a known issue with Windows XP       systems running "Window's Automatic Updates" with 512MB of RAM.              The process (in the Window's Task Manager under the "Processes" tab) is       named WUAUCLT.EXE but initializes the SVCHOST.EXE process in order to       access the internet. It shares it's massive requirement of RAM between       these two processes for a period of anywhere between 5 and 30 minutes while       it searches for any new system updates on the internet. After this time,       this particular instance of "svchost.exe" terminates and is no-longer a       resource "hog".              It may be the case that your issue has nothing at all to do with "Window's       Automatic Updates", however, even if you have a good deal more than the       512MB of RAM that this issue is associated with, there's no harm in       disabling WAU for a time to see if the "hogging" stops...              You can do this by disabling WAU in the "Window's Updates" control panel       and, as an extra precaution, also disable the "Automatic Updates"       (wuauserv) service in "Local Services" (type "services.msc" into the "Run"       box on the Start Menu)...              ==              Cheers, Tim Meddick, Peckham, London. :-)                                    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca