Windows Update CPU Utilization

Our product continues to fail because it is starved for resources since the
svchost.dll is consuming 99% of the CPU for at least 7 minutes. There are
many users that know of this problem and indicate that Microsoft also knows.
Are they going to fix this or do we just disable the Updates?

I worked with a Microsoft agent for 3 hours a couple weeks ago and they tried
a couple Beta fixes. Very minimal results.

I have pushed out to my computers on network a job to stop the service when
they log in ( Placed In Registry Run) net stop wuauserv . I then pushed
out a Scheduled task to start service during the night and then stop the
service before many people arrive to work. These tasks must be run using the
NT Authority\system account.

Also make sure you have set the time to install critical updates when nobody
is using computer.
It does mean people have to log out at end of day and keep computer running
and not shut down. I usually ask them to reboot every few days to keep
computers running smootly.

Appears to have solved our issues until Microsoft provides a proper fix.
Note: Does not work if computers are used 24 hours per day. Also if someone
goes out to windows update it starts the service again.

--
GT


"Rainee" wrote:

> Our product continues to fail because it is starved for resources since the
> svchost.dll is consuming 99% of the CPU for at least 7 minutes. There are
> many users that know of this problem and indicate that Microsoft also knows.
> Are they going to fix this or do we just disable the Updates?