Automatic Updates Service Maxing out CPU

I have a terminal server running as a VM whose CPU was pegged; using Process
Explorer I was able able to narrow the source of the issue down to the
Automatic Updates service. Once I stopped the service, the CPU returned to
normal. Has anyone seen this recently? I know this was an issue a few years
ago, but everything I've read says that it was fixed back then.

Thanks in advance.

 

Hello Tim,

Which OS version do you use and is it full patched? Does the server has internet
connection, so that it can reach MS update sites?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> I have a terminal server running as a VM whose CPU was pegged; using
> Process Explorer I was able able to narrow the source of the issue
> down to the Automatic Updates service. Once I stopped the service,
> the CPU returned to normal. Has anyone seen this recently? I know
> this was an issue a few years ago, but everything I've read says that
> it was fixed back then.
>
> Thanks in advance.
>

 

On Fri, 22 May 2009 07:26:10 -0700, Tim <Tim@discussions.microsoft.com> wrote:

>I have a terminal server running as a VM whose CPU was pegged; using Process
>Explorer I was able able to narrow the source of the issue down to the
>Automatic Updates service. Once I stopped the service, the CPU returned to
>normal. Has anyone seen this recently? I know this was an issue a few years
>ago, but everything I've read says that it was fixed back then.
>
>Thanks in advance.

It was but there have been a number of similar reports recently and this problem
is under investigation in
Newsgroups: microsoft.public.windows.server.update_services

pop in a lurk a bit, Lawrence Garvin IIRC has referred this to the WSUS dev
team.
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.