/build/static/layout/Breadcrumb_cap_w.png

wuauclt.exe using 90% of CPU

Hello,

I have a Win XP SP3 VM for testing patches.
I just started a patch run, and the VM rebooted. After reboot it is really sluggish.
In the process list I see wuauclt.exe using 90% of CPU.

So here's my question. I am using Kbox to patch this machine, Windows Update is disabled in a GPO. So - why is it using 90% of CPU? Does Lumension tie into wuauclt.exe?
Can/should I disable the service (the System CPL shows Updates disabled)?

Thoughts?

-Rich

0 Comments   [ + ] Show comments

Answers (4)

Posted by: cblake 14 years ago
Red Belt
1
Are you certain that the GPO is applied to this VM? I'd verify by running GRRESULT from the command line.
KBOX Patching does not use wuauclt to my knowledge. It would probably be a good idea to disable that service if everything else is as is should be. It sounds like an update was in it's queue and it isn't ready to give up on it. Probably .Net framework or a service pack if it's eating 90%.
Posted by: jkatkace 14 years ago
Purple Belt
1
The service does need to remain enabled for the KBOX to do its scan, but you don't need automatic updates set because the KBOX is downloading them. So, keep it enabled, but tell us the details of this patching schedule. Is this after it's in the "completed" state? What's in the schedule (detect/deploy, reboot actions, etc.)? What does the KBOX say was done?
Posted by: MACSnow 14 years ago
Senior Yellow Belt
1
Thanks John,

That was exactly what I wondered about. If wuauclt is being used to scan for patch updates, then that explains why it was active.
I had just kicked off a scan on my test VM. So that makes sense.

Thanks Again,

Rich
Posted by: airwolf 14 years ago
Red Belt
1
I'm glad I ran into this thread... We aren't using the KBOX for patching, as we are still using WSUS - I'm not sure I see the benefit of using the KBOX over WSUS for patching (aside from 3rd party patching - which we use KBOX Deployments for) if it relies on the WUAUSERV service (wuauclt.exe).
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ