XPost: alt.windows-xp
On Sun, 2 Oct 2011 00:26:00 +0100, "Tim Meddick"
wrote:
>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. :-)
>
>
THANK YOU!!! I think you've nailed it!
Frequently when this action is going on, update.exe
is also running.
>
>
> wrote in message
>news:hiu687p14gjlvpl1tgu99aq8ng1lpjd2t9@4ax.com...
>>
>>
>> Just did a system restore and reboot. Can hardly use anything ----
>> svchost.exe has been running for 10 minutes using 60K RAM
>> and 99% od CPU.
>> What is all this ????
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
