Windows updates 100% CPU

I run 40 something servers and i configured windows update to download but not install through GPO.
The problem is that the check seems to occur during working hours whereby on several servers the cpu rockets to 100% and memory goes up as well.
When i stop the service the server returns to almost no cpu usage and when i start it again cpu and memory go through the roof again.
I'm using an internal wsus server.

Is there a way to have the check run only at night?

Do you know another solution to get a grip on this problem.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Amitabh SinghAWS Certified Solution Architect | L3 IT Specialist for CloudCommented:
well i recommend to use schedule task and schedule to run\check WSUS server at night

Create a schedule task to check for update at night and run the script
Download Link

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Amitabh SinghAWS Certified Solution Architect | L3 IT Specialist for CloudCommented:
or you can use schedule task  to execute\Run "wuauclt.exe /detectnow /reportnow" at night
Scheduling the task is a good idea for a number of reasons, but it does not solve the actual problem.

I recommend controlling the processor affinity for this task.  This will limit the task's ability to overload the entire system, providing you have multiple cores and/or processors.

You can read about Processor affinity here:

For example, this will limit "calc.exe" to only core/processor #1:
cmd.exe /c start "Process Monitor" /affinity 1 "%windir%\system32\calc.exe"

Open in new window

GnukkelAuthor Commented:
Thanks Amitabh you put me on the right track. We use Nagios and i forced the check at night.
Paul StageIT DirectorCommented:
I'm having this exact same issue on my 2008 R2 servers. Unfortunately the processor affinity won't work on all of mine, as they only have a single proc. It would be ideal for Microsoft to resolve the Windows Update issue so we can move on to more important things. But right now, this is a thorn in my side. Does anyone else have any resolution on this issue?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.