See recent posts in this possibly-related thread:
http://groups.google.com/group/micro...2272d743e5ee35
Or see
http://blogs.technet.com/sbs/archive...e-the-cpu.aspx
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Client - since 2002


Nick Cozby wrote:
> I have 4 identical servers that are all exhibiting the same issue. We
> have
> hundreds of other clients and servers that are not experiencing this issue
> and pull updates just fine from the same WSUS server.
>
> All 4 servers are Windows 2003 x64 SP2. All 4 had been working just fine
> getting updates for over 6 months. All 4 began exhibiting this issue at
> the
> same time last week. No known changes to any of the systems.
>
> On each server, the "Automatic Update" service runs to pull updates from
> our
> WSUS server. The server then becomes sluggish (100% cpu utilization from
> svchost.exe) and remains so until the Automatic Updates service is
> stopped.
> Process Explorer view of the offending svchost.exe process shows that it
> is
> the Windows Update that is consuming the CPU. I let it run like this over
> the weekend, and it remained at 100% cpu utilization for 4 days without
> installing a single update. Below is the resuling text in the
> WindowsUpdate.log. I had to manually kill the Automatic Update service
> this
> morning to stop the 100% utilization.
>
> 2009-04-23 16:06:35:736 808 dc8 PT +++++++++++ PT: Synchronizing server
> updates +++++++++++
> 2009-04-23 16:06:35:736 808 dc8 PT + ServiceId =
> {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
> http://RAD-VMSRVSUS1/ClientWebService/client.asmx
> 2009-04-23 16:06:49:173 808 dc8 PT +++++++++++ PT: Synchronizing extended
> update info +++++++++++
> 2009-04-23 16:06:49:173 808 dc8 PT + ServiceId =
> {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
> http://RAD-VMSRVSUS1/ClientWebService/client.asmx
> 2009-04-23 16:12:08:595 1872 7a0 COMAPI -------------
> 2009-04-23 16:12:08:595 1872 7a0 COMAPI -- START -- COMAPI: Search
> [ClientId = Exchange12]
> 2009-04-23 16:12:08:595 1872 7a0 COMAPI ---------
> 2009-04-23 16:12:08:595 1872 7a0 COMAPI <<-- SUBMITTED -- COMAPI: Search
> [ClientId = Exchange12]
> 2009-04-24 05:00:10:001 808 e48 AU Forced install timer expired for
> scheduled install
> 2009-04-24 05:00:10:001 808 e48 AU UpdateDownloadProperties: 0 download(s)
> are still in progress.
> 2009-04-24 05:00:10:017 808 e48 AU Setting AU scheduled install time to
> 2009-04-25 10:00:00
> 2009-04-25 05:00:10:017 808 e48 AU Forced install timer expired for
> scheduled install
> 2009-04-25 05:00:10:017 808 e48 AU UpdateDownloadProperties: 0 download(s)
> are still in progress.
> 2009-04-25 05:00:10:017 808 e48 AU Setting AU scheduled install time to
> 2009-04-26 10:00:00
> 2009-04-26 05:00:10:033 808 e48 AU Forced install timer expired for
> scheduled install
> 2009-04-26 05:00:10:033 808 e48 AU UpdateDownloadProperties: 0 download(s)
> are still in progress.
> 2009-04-26 05:00:10:033 808 e48 AU Setting AU scheduled install time to
> 2009-04-27 10:00:00
> 2009-04-27 00:50:11:001 808 e48 AU ########### AU: Uninitializing
> Automatic Updates ###########
> 2009-04-27 00:50:11:001 808 dc8 Agent * WARNING: Failed to filter search
> results, error = 0x8024000B
> 2009-04-27 00:50:11:064 808 dc8 Agent *********
> 2009-04-27 00:50:11:064 808 dc8 Agent ** END ** Agent: Finding updates
> [CallerId = AutomaticUpdates]
> 2009-04-27 00:50:11:064 808 dc8 Agent *************
> 2009-04-27 00:50:11:079 808 e48 Agent Sending shutdown notification to
> client 2009-04-27 00:50:11:079 1872 56c COMAPI WARNING: Received service
> shutdown/self-update notification.