none
SVCHOST uses high CPU because of Windows Update process during Automatic Detection Frequency when even there is no update to be installed on Windows XP SP2 X64.

    Pregunta

  • Dears Hi,

    I've attached the WinodwsUpdate.log

    SVCHOST uses high CPU because of Windows Update process during Automatic Detection Frequency when even there is no update to be installed on Windows XP SP2 X64.

    Would you please kindly help because the business is being affected. 

    2013-04-17 11:12:21:815 736 a14 AU AU received policy change subscription event
    2013-04-17 11:18:28:613 736 a14 AU #############
    2013-04-17 11:18:28:613 736 a14 AU ## START ##  AU: Search for updates
    2013-04-17 11:18:28:613 736 a14 AU #########
    2013-04-17 11:18:28:613 736 a14 AU <<## SUBMITTED ## AU: Search for updates [CallId = {D148F347-A3BD-4C44-955D-48527AB9EC70}]
    2013-04-17 11:18:28:613 736 770 Agent *************
    2013-04-17 11:18:28:613 736 770 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2013-04-17 11:18:28:613 736 770 Agent *********
    2013-04-17 11:18:28:613 736 770 Agent  * Online = Yes; Ignore download priority = No
    2013-04-17 11:18:28:613 736 770 Agent  * Criteria = "IsHidden=0 and IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and IsAssigned=1 or IsHidden=0 and IsInstalled=1 and DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and IsAssigned=1 and RebootRequired=1"
    2013-04-17 11:18:28:613 736 770 Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2013-04-17 11:18:28:613 736 770 Agent  * Search Scope = {Machine}
    2013-04-17 11:18:29:300 736 770 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2013-04-17 11:18:29:300 736 770 Misc Microsoft signed: Yes
    2013-04-17 11:18:29:300 736 770 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
    2013-04-17 11:18:29:316 736 770 Misc Microsoft signed: Yes
    2013-04-17 11:18:29:316 736 770 Setup ***********  Setup: Checking whether self-update is required  ***********
    2013-04-17 11:18:29:316 736 770 Setup  * Inf file: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
    2013-04-17 11:18:29:316 736 770 Setup Update NOT required for C:\WINDOWS\system32\cdm.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-04-17 11:18:29:316 736 770 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-04-17 11:18:29:316 736 770 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-04-17 11:18:29:316 736 770 Setup Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-04-17 11:18:29:316 736 770 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-04-17 11:18:29:316 736 770 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-04-17 11:18:29:316 736 770 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-04-17 11:18:29:316 736 770 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-04-17 11:18:29:316 736 770 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-04-17 11:18:29:316 736 770 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-04-17 11:18:29:316 736 770 Setup FATAL: Update required for C:\WINDOWS\system32\wups.dll: target version = 7.1.6001.65, required version = 7.4.7600.226
    2013-04-17 11:18:29:316 736 770 Setup FATAL: Update required for C:\WINDOWS\system32\wups2.dll: target version = 7.1.6001.65, required version = 7.4.7600.226
    2013-04-17 11:18:29:316 736 770 Setup Update NOT required for C:\WINDOWS\system32\wuweb.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-04-17 11:18:29:316 736 770 Setup Update NOT required for C:\WINDOWS\SysWow64\wuweb.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-04-17 11:18:29:316 736 770 Setup Update NOT required for C:\WINDOWS\SysWow64\wuapi.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-04-17 11:18:29:316 736 770 Setup Update NOT required for C:\WINDOWS\SysWOW64\wuapi.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-04-17 11:18:29:316 736 770 Setup FATAL: Update required for C:\WINDOWS\SysWow64\wups.dll: target version = 7.1.6001.65, required version = 7.4.7600.226
    2013-04-17 11:18:29:316 736 770 Setup FATAL: Update required for C:\WINDOWS\SysWow64\wups2.dll: target version = 7.1.6001.65, required version = 7.4.7600.226
    2013-04-17 11:18:29:316 736 770 Setup Update NOT required for C:\WINDOWS\SysWow64\wuaueng.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-04-17 11:18:29:316 736 770 Setup Update NOT required for C:\WINDOWS\SysWOW64\wuaueng.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-04-17 11:18:29:316 736 770 Setup Update NOT required for C:\WINDOWS\SysWow64\wuaucpl.cpl: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-04-17 11:18:29:316 736 770 Setup Update NOT required for C:\WINDOWS\SysWOW64\wuaucpl.cpl.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-04-17 11:18:29:316 736 770 Setup  * IsUpdateRequired = Yes
    2013-04-17 11:18:29:316 736 770 Setup *************
    2013-04-17 11:18:29:316 736 770 Setup ** START **  Setup: Downloading client CABs
    2013-04-17 11:18:29:316 736 770 Setup *********
    2013-04-17 11:18:29:316 736 770 Setup  * Main CAB URL: http://drwb003/selfupdate/WSUS3/x64/Other
    2013-04-17 11:18:29:316 736 770 Setup  * MUI CAB URL: http://drwb003/selfupdate/WSUS3/x64/Other
    2013-04-17 11:18:29:316 736 770 Setup  * Wow64 CAB URL: http://drwb003/selfupdate/WSUS3/x86/Other
    2013-04-17 11:18:29:316 736 770 Setup  * Download directory: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default
    2013-04-17 11:18:29:316 736 770 Setup  * WOW64 download directory: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wow64
    2013-04-17 11:18:29:331 736 770 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wups.cab:
    2013-04-17 11:18:29:331 736 770 Misc Microsoft signed: Yes
    2013-04-17 11:18:29:347 736 770 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wups2.cab:
    2013-04-17 11:18:29:347 736 770 Misc Microsoft signed: Yes
    2013-04-17 11:18:29:363 736 770 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wow64\wups.cab:
    2013-04-17 11:18:29:363 736 770 Misc Microsoft signed: Yes
    2013-04-17 11:18:29:378 736 770 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wow64\wups2.cab:
    2013-04-17 11:18:29:378 736 770 Misc Microsoft signed: Yes
    2013-04-17 11:18:29:378 736 770 Setup *********
    2013-04-17 11:18:29:378 736 770 Setup **  END  **  Setup: Downloading client CABs
    2013-04-17 11:18:29:378 736 770 Setup *************
    2013-04-17 11:18:29:378 736 770 Agent  * WARNING: Skipping scan, self-update check returned 0x8024001B
    2013-04-17 11:18:29:378 736 a14 AU ###########  AU: Uninitializing Automatic Updates  ###########
    2013-04-17 11:18:29:394 736 a14 Setup *************
    2013-04-17 11:18:29:394 736 a14 Setup ** START **  Setup: Installing client binaries
    2013-04-17 11:18:29:394 736 a14 Setup *********
    2013-04-17 11:18:29:394 736 a14 Setup  * Download directory: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default
    2013-04-17 11:18:29:394 736 a14 Setup  * Stop and start service: No
    2013-04-17 11:18:29:394 736 a14 Setup Starting file operations for section wups
    2013-04-17 11:18:29:409 736 770 Agent  * WARNING: Exit code = 0x8024001B
    2013-04-17 11:18:29:409 736 770 Agent *********
    2013-04-17 11:18:29:409 736 770 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2013-04-17 11:18:29:409 736 770 Agent *************

    jueves, 18 de abril de 2013 15:57

Respuestas

  • SVCHOST uses high CPU because of Windows Update process during Automatic Detection Frequency when even there is no update to be installed on Windows XP SP2 X64.

    When was Service Pack 2 for Windows XP x64 installed?

    What was recently done to this system that instigated this behavior?

    There are numerous, known (and LEGACY) causes for high CPU utilization in SVCHOST.EXE due to the Windows Update Agent, but we've not seen them for a very, very long time, so getting some context and perspective on this particular scenario will be critically important to providing any useful response.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    martes, 23 de abril de 2013 23:09
    Moderador

Todas las respuestas

  • Continue of the logs:

    2013-04-17 11:18:29:409 736 770 Agent WARNING: WU client failed Searching for update with error 0x8024001b
    2013-04-17 11:18:29:800 736 a14 Setup Successfully copied source file C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wups.dll to C:\WINDOWS\system32\wups.dll.wusetup.42026203.new
    2013-04-17 11:18:29:800 736 a14 Setup File operations for section wups completed successfully
    2013-04-17 11:18:29:800 736 a14 Setup Starting file operations for section wups2
    2013-04-17 11:18:29:816 736 a14 Setup Successfully copied source file C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wups2.dll to C:\WINDOWS\system32\wups2.dll.wusetup.42026218.new
    2013-04-17 11:18:29:831 736 a14 Setup File operations for section wups2 completed successfully
    2013-04-17 11:18:29:831 736 a14 Setup Starting file operations for section wow64_wups
    2013-04-17 11:18:29:847 736 a14 Setup Successfully copied source file C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\Wow64\wups.dll to C:\WINDOWS\SysWow64\wups.dll.wusetup.42026250.new
    2013-04-17 11:18:29:847 736 a14 Setup File operations for section wow64_wups completed successfully
    2013-04-17 11:18:29:863 736 a14 Setup Starting file operations for section wow64_wups2
    2013-04-17 11:18:29:878 736 a14 Setup Successfully copied source file C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\Wow64\wups2.dll to C:\WINDOWS\SysWow64\wups2.dll.wusetup.42026281.new
    2013-04-17 11:18:29:878 736 a14 Setup File operations for section wow64_wups2 completed successfully
    2013-04-17 11:18:29:878 736 a14 Setup Starting registry operations for section wups
    2013-04-17 11:18:29:894 736 a14 Setup Completed registration operations for section wups: status 0
    2013-04-17 11:18:29:894 736 a14 Setup Starting registry operations for section wups2
    2013-04-17 11:18:29:894 736 a14 Setup Completed registration operations for section wups2: status 0
    2013-04-17 11:18:29:894 736 a14 Setup Starting registry operations for section wow64_wups
    2013-04-17 11:18:29:894 736 a14 Setup Completed registration operations for section wow64_wups: status 0
    2013-04-17 11:18:29:894 736 a14 Setup Starting registry operations for section wow64_wups2
    2013-04-17 11:18:29:894 736 a14 Setup Completed registration operations for section wow64_wups2: status 0
    2013-04-17 11:18:29:894 736 a14 Setup Processing registry operations completed. Deleting backup files.
    2013-04-17 11:18:29:909 736 a14 Setup *********
    2013-04-17 11:18:29:909 736 a14 Setup **  END  **  Setup: Installing client binaries
    2013-04-17 11:18:29:909 736 a14 Setup *************
    2013-04-17 11:18:29:909 736 a14 Report REPORT EVENT: {41820B84-6C23-4DB8-BDEB-CB634087AC4C} 2013-04-17 11:18:29:378+0430 1 162 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 0 0 SelfUpdate Success Content Download Download succeeded.
    2013-04-17 11:18:29:909 736 a14 Report REPORT EVENT: {2E32420C-D207-493D-874B-1222A59EB0A3} 2013-04-17 11:18:29:909+0430 1 201 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 0 0 SelfUpdate Success Content Install Installation pending.
    2013-04-17 11:18:30:066 736 a14 PT WARNING: Cached cookie has expired or new PID is available
    2013-04-17 11:18:30:066 736 a14 PT Initializing simple targeting cookie, clientId = fa4d3885-67ee-49b3-95ff-c315aa54ce3d, target group = , DNS name = r-7.rbt.local
    2013-04-17 11:18:30:066 736 a14 PT  Server URL = http://drwb003/SimpleAuthWebService/SimpleAuth.asmx
    2013-04-17 11:18:30:097 736 a14 PT WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2013-04-17 11:18:30:097 736 a14 PT WARNING: SOAP Fault: 0x00012c
    2013-04-17 11:18:30:097 736 a14 PT WARNING:     faultstring:Fault occurred
    2013-04-17 11:18:30:097 736 a14 PT WARNING:     ErrorCode:ServerChanged(4)
    2013-04-17 11:18:30:097 736 a14 PT WARNING:     Message:Server rolled back since last call to GetCookie
    2013-04-17 11:18:30:097 736 a14 PT WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
    2013-04-17 11:18:30:097 736 a14 PT WARNING:     ID:661ad35c-6ac0-4c05-b7c4-0ce8fd904599
    2013-04-17 11:18:30:097 736 a14 PT WARNING: PTError: 0x80244015
    2013-04-17 11:18:30:097 736 a14 PT WARNING: GetCookie_WithRecovery failed : 0x80244015
    2013-04-17 11:18:30:097 736 a14 PT WARNING: RefreshCookie failed: 0x80244015
    2013-04-17 11:18:30:097 736 a14 PT WARNING: RefreshPTState failed: 0x80244015
    2013-04-17 11:18:30:316 736 a14 PT WARNING: Cached cookie has expired or new PID is available
    2013-04-17 11:18:30:316 736 a14 PT Initializing simple targeting cookie, clientId = fa4d3885-67ee-49b3-95ff-c315aa54ce3d, target group = , DNS name = r-7.rbt.local
    2013-04-17 11:18:30:316 736 a14 PT  Server URL = http://drwb003/SimpleAuthWebService/SimpleAuth.asmx
    2013-04-17 11:18:33:597 736 a14 Report Uploading 2 events using cached cookie, reporting URL = http://drwb003/ReportingWebService/ReportingWebService.asmx
    2013-04-17 11:18:33:613 736 a14 Report Reporter successfully uploaded 2 events.
    2013-04-17 11:18:33:847 736 a14 Service *********
    2013-04-17 11:18:33:847 736 a14 Service **  END  **  Service: Service exit [Exit code = 0x240002]
    2013-04-17 11:18:33:847 736 a14 Service *************
    2013-04-17 11:18:33:847 736 a14 Misc ===========  Logging initialized (build: 7.4.7600.226, tz: +0430)  ===========
    2013-04-17 11:18:33:847 736 a14 Misc  = Process: C:\WINDOWS\System32\svchost.exe
    2013-04-17 11:18:33:847 736 a14 Misc  = Module: C:\WINDOWS\system32\wuaueng.dll
    2013-04-17 11:18:33:847 736 a14 Service *************
    2013-04-17 11:18:33:847 736 a14 Service ** START **  Service: Service startup
    2013-04-17 11:18:33:847 736 a14 Service *********
    2013-04-17 11:18:33:878 736 a14 Misc Registering binary: C:\WINDOWS\system32\regsvr32.exe  /s "C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wups.dll\7.4.7600.226\wups.dll"
    2013-04-17 11:18:34:113 736 a14 Misc Registering binary: C:\WINDOWS\system32\regsvr32.exe  /s "C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wups2.dll\7.4.7600.226\wups2.dll"
    2013-04-17 11:18:34:316 736 a14 Misc Registering binary: C:\WINDOWS\SysWOW64\regsvr32.exe  /s "C:\WINDOWS\SysWOW64\SoftwareDistribution\Setup\ServiceStartup\wups.dll\7.4.7600.226\wups.dll"
    2013-04-17 11:18:34:503 736 a14 Misc Registering binary: C:\WINDOWS\SysWOW64\regsvr32.exe  /s "C:\WINDOWS\SysWOW64\SoftwareDistribution\Setup\ServiceStartup\wups2.dll\7.4.7600.226\wups2.dll"
    2013-04-17 11:18:34:691 736 a14 Agent  * WU client version 7.4.7600.226
    2013-04-17 11:18:34:691 736 a14 Agent  * Base directory: C:\WINDOWS\SoftwareDistribution
    2013-04-17 11:18:34:691 736 a14 Agent  * Access type: No proxy
    2013-04-17 11:18:34:691 736 a14 Agent  * Network state: Connected
    2013-04-17 11:18:34:925 736 a14 Agent Created new random SusClientId 526a17cb-a059-4cd4-b467-2b1aeac75157. Old Id: none.
    2013-04-17 11:18:34:925 736 a14 Report ***********  Report: Initializing static reporting data  ***********
    2013-04-17 11:18:34:925 736 a14 Report  * OS Version = 5.2.3790.2.0.65792
    2013-04-17 11:18:34:957 736 a14 Report  * Computer Brand = VMware, Inc.
    2013-04-17 11:18:34:957 736 a14 Report  * Computer Model = VMware Virtual Platform
    2013-04-17 11:18:34:957 736 a14 Report  * Bios Revision = 6.00
    2013-04-17 11:18:34:957 736 a14 Report  * Bios Name = Default System BIOS
    2013-04-17 11:18:34:957 736 a14 Report  * Bios Release Date = 2012-06-22T00:00:00
    2013-04-17 11:18:34:957 736 a14 Report  * Locale ID = 1065
    2013-04-17 11:18:34:972 736 a14 Service  * Service restarted after self update
    2013-04-17 11:18:39:957 736 468 Report REPORT EVENT: {258ACDCD-C81B-4357-9777-449D94CF0AE2} 2013-04-17 11:18:34:910+0430 1 183 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 0 0 SelfUpdate Success Content Install Installation Successful: Windows successfully installed the following update: Automatic Updates
    2013-04-17 11:19:19:912 736 a14 Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2013-04-17 11:19:19:912 736 a14 Agent ***********  Agent: Initializing global settings cache  ***********
    2013-04-17 11:19:19:912 736 a14 Agent  * WSUS server: http://drwb003
    2013-04-17 11:19:19:912 736 a14 Agent  * WSUS status server: http://drwb003
    2013-04-17 11:19:19:912 736 a14 Agent  * Target group: (Unassigned Computers)
    2013-04-17 11:19:19:912 736 a14 Agent  * Windows Update access disabled: No
    2013-04-17 11:19:19:927 736 a14 DnldMgr Download manager restoring 0 downloads
    2013-04-17 11:19:19:927 736 a14 AU ###########  AU: Initializing Automatic Updates  ###########
    2013-04-17 11:19:19:927 736 a14 AU AU setting next detection timeout to 2013-04-17 06:49:19
    2013-04-17 11:19:19:927 736 a14 AU AU setting next sqm report timeout to 2013-04-17 06:49:19
    2013-04-17 11:19:19:927 736 a14 AU AU setting next featured software notification timeout to 2013-04-17 06:49:19
    2013-04-17 11:19:19:927 736 a14 AU AU featured software notification sequence number is 314, Generation Time:2013-04-17 06:49:19
    2013-04-17 11:19:19:927 736 a14 AU  # WSUS server: http://drwb003
    2013-04-17 11:19:19:927 736 a14 AU  # Detection frequency: 2
    2013-04-17 11:19:19:927 736 a14 AU  # Approval type: Scheduled (Policy)
    2013-04-17 11:19:19:927 736 a14 AU  # Scheduled install day/time: Every day at 3:00
    2013-04-17 11:19:19:927 736 a14 AU  # Auto-install minor updates: Yes (Policy)
    2013-04-17 11:19:19:927 736 a14 AU  # Will interact with non-admins (Non-admins are elevated (Policy))
    2013-04-17 11:19:19:927 736 a14 Agent Switching to hardware-verified ClientId.
    2013-04-17 11:19:19:927 736 a14 AU Setting AU scheduled install time to 2013-04-17 22:30:00
    2013-04-17 11:19:19:927 736 a14 AU Initializing featured updates
    2013-04-17 11:19:19:927 736 a14 AU Found 0 cached featured updates
    2013-04-17 11:19:19:927 736 a14 AU AU finished delayed initialization
    2013-04-17 11:19:19:990 736 a14 Agent Created new random SusClientId 11cdc0f4-4737-4765-9d61-e7e52abe7c66. Old Id: 526a17cb-a059-4cd4-b467-2b1aeac75157.
    2013-04-17 11:19:19:990 736 a14 AU #############
    2013-04-17 11:19:19:990 736 a14 AU ## START ##  AU: Search for updates
    2013-04-17 11:19:19:990 736 a14 AU #########
    2013-04-17 11:19:19:990 736 a14 AU <<## SUBMITTED ## AU: Search for updates [CallId = {64A5F618-02FE-444A-9E71-B17D6D94A670}]
    2013-04-17 11:19:20:568 736 468 Agent *************
    2013-04-17 11:19:20:568 736 468 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2013-04-17 11:19:20:568 736 468 Agent *********
    2013-04-17 11:19:20:568 736 468 Agent  * Online = Yes; Ignore download priority = No
    2013-04-17 11:19:20:568 736 468 Agent  * Criteria = "IsHidden=0 and IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and IsAssigned=1 or IsHidden=0 and IsInstalled=1 and DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and IsAssigned=1 and RebootRequired=1"
    2013-04-17 11:19:20:568 736 468 Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2013-04-17 11:19:20:568 736 468 Agent  * Search Scope = {Machine}
    2013-04-17 11:19:20:568 736 468 Setup Agent skipping selfupdate check following a successful selfupdate
    2013-04-17 11:19:22:084 736 468 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2013-04-17 11:19:22:084 736 468 PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://drwb003/ClientWebService/client.asmx
    2013-04-17 11:19:22:146 736 468 EEHndlr WARNING: Failed to populate ServiceStartup entries in Cache: error 0x80070002

    2013-04-17 11:19:24:756 736 468 EEHndlr WARNING: Failed to populate ServiceStartup entries in Cache: error 0x80070002

    2013-04-17 11:19:24:771 736 468 EEHndlr WARNING: Failed to populate ServiceStartup entries in Cache: error 0x80070002

    2013-04-17 11:19:24:787 736 468 EEHndlr WARNING: Failed to populate ServiceStartup entries in Cache: error 0x80070002

    2013-04-17 11:19:58:867 736 468 PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2013-04-17 11:19:58:867 736 468 PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://drwb003/ClientWebService/client.asmx
    2013-04-17 11:20:02:335 736 468 Agent  * Found 0 updates and 69 categories in search; evaluated appl. rules of 1343 out of 2192 deployed entities
    2013-04-17 11:20:02:335 736 468 Agent *********
    2013-04-17 11:20:02:335 736 468 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2013-04-17 11:20:02:335 736 468 Agent *************
    2013-04-17 11:20:02:351 736 11f4 AU >>##  RESUMED  ## AU: Search for updates [CallId = {64A5F618-02FE-444A-9E71-B17D6D94A670}]
    2013-04-17 11:20:02:351 736 11f4 AU  # 0 updates detected
    2013-04-17 11:20:02:351 736 11f4 AU #########
    2013-04-17 11:20:02:351 736 11f4 AU ##  END  ##  AU: Search for updates [CallId = {64A5F618-02FE-444A-9E71-B17D6D94A670}]
    2013-04-17 11:20:02:351 736 11f4 AU #############
    2013-04-17 11:20:02:351 736 11f4 AU Featured notifications is disabled.
    2013-04-17 11:20:02:351 736 11f4 AU AU setting next detection timeout to 2013-04-17 08:27:40
    2013-04-17 11:20:02:351 736 11f4 AU Setting AU scheduled install time to 2013-04-17 22:30:00
    2013-04-17 11:20:07:336 736 468 Report REPORT EVENT: {3ED8174D-BB2F-4D5E-9711-B297EE6ACBC6} 2013-04-17 11:20:02:335+0430 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
    2013-04-17 11:20:07:336 736 468 Report REPORT EVENT: {24AFB46E-6E8A-41AB-9861-BA53915C7EFE} 2013-04-17 11:20:02:335+0430 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
    2013-04-17 11:29:56:362 736 468 Report Uploading 3 events using cached cookie, reporting URL = http://drwb003/ReportingWebService/ReportingWebService.asmx
    2013-04-17 11:29:56:378 736 468 Report Reporter successfully uploaded 3 events.

    jueves, 18 de abril de 2013 16:13
  • SVCHOST uses high CPU because of Windows Update process during Automatic Detection Frequency when even there is no update to be installed on Windows XP SP2 X64.

    When was Service Pack 2 for Windows XP x64 installed?

    What was recently done to this system that instigated this behavior?

    There are numerous, known (and LEGACY) causes for high CPU utilization in SVCHOST.EXE due to the Windows Update Agent, but we've not seen them for a very, very long time, so getting some context and perspective on this particular scenario will be critically important to providing any useful response.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    martes, 23 de abril de 2013 23:09
    Moderador