Recursos para Profesionales de TI > Página principal de foros > WSUS > update for root certificates [september2009] (kb931125)
Formular una preguntaFormular una pregunta
 

Respondidaupdate for root certificates [september2009] (kb931125)

  • jueves, 22 de octubre de 2009 9:37sstrate Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     

    I m using WSUS for deploying updates, many of windows XP workstations keep asking to reinstall the root certificate kb931125, and the report in WSUS said it's either installed on some PCs or downloaded on the others.
    any idea to solve the problem?

    thank you.

Respuestas

  • viernes, 23 de octubre de 2009 14:41Lawrence GarvinMVP, ModeradorMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     Respondida
    2009-10-23 09:00:10:013 2044 6b4 AU Forced install timer expired for scheduled install
    2009-10-23 09:00:10:013 2044 6b4 AU UpdateDownloadProperties: 0 download(s) are still in progress.
    2009-10-23 09:00:10:013 2044 6b4 AU #############
    2009-10-23 09:00:10:013 2044 6b4 AU ## START ##  AU: Install updates
    2009-10-23 09:00:10:013 2044 6b4 AU #########
    2009-10-23 09:00:10:013 2044 6b4 AU   # Initiating scheduled install
    2009-10-23 09:00:10:013 2044 6b4 AU   # Approved updates = 1
    2009-10-23 09:00:10:013 2044 6b4 AU <<## SUBMITTED ## AU: Install updates / installing updates [CallId = {8B4C90AF-07AE-4E1B-A778-ACB70B3B54DD}]
    2009-10-23 09:00:10:013 2044 994 Agent *************
    2009-10-23 09:00:10:013 2044 994 Agent ** START **  Agent: Installing updates [CallerId = AutomaticUpdates]
    2009-10-23 09:00:10:013 2044 994 Agent *********
    2009-10-23 09:00:10:013 2044 994 Agent   * Updates to install = 1
    2009-10-23 09:00:10:013 5568 1784 CltUI AU client got new directive = 'Shutdown', serviceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, return = 0x00000000
    2009-10-23 09:00:10:013 2044 6b4 AU AU received handle event
    2009-10-23 09:00:10:045 2044 994 Agent   *   Title = Update for Root Certificates
    2009-10-23 09:00:10:045 2044 994 Agent   *   UpdateId = {3B151C1D-1C4E-492E-82A3-4BF70484841F}.100
    2009-10-23 09:00:10:045 2044 994 Agent   *     Bundles 1 updates:
    2009-10-23 09:00:10:045 2044 994 Agent   *       {748226C3-998C-4C25-AD91-E681D9B8D3FB}.100
    2009-10-23 09:00:10:263 2044 994 DnldMgr Preparing update for install, updateId = {748226C3-998C-4C25-AD91-E681D9B8D3FB}.100.
    2009-10-23 09:00:10:279 2792 1304 Misc ===========  Logging initialized (build: 7.2.6001.788, tz: +0200)  ===========
    2009-10-23 09:00:10:279 2792 1304 Misc   = Process: C:\WINDOWS\system32\wuauclt.exe
    2009-10-23 09:00:10:279 2792 1304 Misc   = Module: C:\WINDOWS\system32\wuaueng.dll
    2009-10-23 09:00:10:279 2792 1304 Handler :::::::::::::
    2009-10-23 09:00:10:279 2792 1304 Handler :: START ::  Handler: Command Line Install
    2009-10-23 09:00:10:279 2792 1304 Handler :::::::::
    2009-10-23 09:00:10:279 2792 1304 Handler   : Updates to install = 1
    2009-10-23 09:00:10:857 2792 1304 Handler   : Command line install completed. Return code = 0x00000000, Result = Succeeded, Reboot required = false
    2009-10-23 09:00:10:857 2792 1304 Handler :::::::::
    2009-10-23 09:00:10:857 2792 1304 Handler ::  END  ::  Handler: Command Line Install
    2009-10-23 09:00:10:857 2792 1304 Handler :::::::::::::
    2009-10-23 09:00:10:873 2044 a94 AU >>##  RESUMED  ## AU: Installing update [UpdateId = {3B151C1D-1C4E-492E-82A3-4BF70484841F}, succeeded]
    2009-10-23 09:00:10:967 2044 994 Agent *********
    2009-10-23 09:00:10:967 2044 994 Agent **  END  **  Agent: Installing updates [CallerId = AutomaticUpdates]
    2009-10-23 09:00:10:967 2044 a94 AU Install call completed.
    2009-10-23 09:00:10:967 2044 994 Agent *************
    2009-10-23 09:00:10:967 2044 a94 AU   # WARNING: Install call completed, reboot required = No, error = 0x00000000
    2009-10-23 09:00:10:967 2044 a94 AU #########
    2009-10-23 09:00:10:967 2044 a94 AU ##  END  ##  AU: Installing updates [CallId = {8B4C90AF-07AE-4E1B-A778-ACB70B3B54DD}]
    2009-10-23 09:00:10:967 2044 a94 AU #############
    2009-10-23 09:00:10:982 2044 a94 AU Install complete for all calls, reboot NOT needed


    2009-10-23 09:00:45:811 2044 17e4 Report REPORT EVENT: {52F3000E-E4DF-4D50-AFC1-D52936FC62BA} 2009-10-23 09:00:10:873+0200 1 190 101 {3B151C1D-1C4E-492E-82A3-4BF70484841F} 100 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Update for Root Certificates


    The installation was successful; looks like the metadata may have a defective isInstalled rule and is not properly detecting that the update is already installed.

    A quick fix for this is to create a special group on WSUS just for this update. Approve the update only for that group, and then ADD your XP machines to that group until this update successfully installed. One you know the update has been downloaded/installed successfully then remove the machine from the group.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com

Todas las respuestas

  • jueves, 22 de octubre de 2009 12:10Lawrence GarvinMVP, ModeradorMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    KB931125 is routinely updated, the most recent having been last month. Do you have systems that actually show this update with a failed installation? If not, you should install it.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
  • viernes, 23 de octubre de 2009 12:41sstrate Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     

    thanks Lawrence for your  reply, but the case here is that the same root certificate september2009 is keep giving warning for installation and it's being installed many many times!!
    this is a part of the WindowsUpdate.log

    2009-10-23 00:03:55:147 2044 11c Report Uploading 2 events using cached cookie, reporting URL = http://computerwsus/ReportingWebService/ReportingWebService.asmx
    2009-10-23 00:03:55:147 2044 11c Report Reporter successfully uploaded 2 events.
    2009-10-23 04:45:55:974 2044 6b4 AU #############
    2009-10-23 04:45:55:974 2044 6b4 AU ## START ##  AU: Search for updates
    2009-10-23 04:45:55:974 2044 6b4 AU #########
    2009-10-23 04:45:55:974 2044 6b4 AU <<## SUBMITTED ## AU: Search for updates [CallId = {B3DC9565-3742-4DAE-B83B-5E78C7050A16}]
    2009-10-23 04:45:55:974 2044 e8c Agent *************
    2009-10-23 04:45:55:974 2044 e8c Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2009-10-23 04:45:55:974 2044 e8c Agent *********
    2009-10-23 04:45:55:974 2044 e8c Agent   * Online = Yes; Ignore download priority = No
    2009-10-23 04:45:55:974 2044 e8c 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"
    2009-10-23 04:45:55:974 2044 e8c Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    2009-10-23 04:45:55:974 2044 e8c Agent   * Search Scope = {Machine}
    2009-10-23 04:45:55:974 2044 e8c Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2009-10-23 04:45:55:974 2044 e8c Misc  Microsoft signed: Yes
    2009-10-23 04:45:58:256 2044 e8c Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2009-10-23 04:45:58:256 2044 e8c Misc  Microsoft signed: Yes
    2009-10-23 04:45:58:271 2044 e8c Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
    2009-10-23 04:45:58:287 2044 e8c Misc  Microsoft signed: Yes
    2009-10-23 04:45:58:287 2044 e8c Setup ***********  Setup: Checking whether self-update is required  ***********
    2009-10-23 04:45:58:287 2044 e8c Setup   * Inf file: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
    2009-10-23 04:45:58:287 2044 e8c Setup Update NOT required for C:\WINDOWS\system32\cdm.dll: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 04:45:58:287 2044 e8c Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 04:45:58:287 2044 e8c Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 04:45:58:287 2044 e8c Setup Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 04:45:58:287 2044 e8c Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 04:45:58:287 2044 e8c Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 04:45:58:287 2044 e8c Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 04:45:58:287 2044 e8c Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 04:45:58:287 2044 e8c Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 04:45:58:287 2044 e8c Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 04:45:58:287 2044 e8c Setup Update NOT required for C:\WINDOWS\system32\wups.dll: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 04:45:58:287 2044 e8c Setup Update NOT required for C:\WINDOWS\system32\wups2.dll: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 04:45:58:287 2044 e8c Setup Update NOT required for C:\WINDOWS\system32\wuweb.dll: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 04:45:58:287 2044 e8c Setup   * IsUpdateRequired = No
    2009-10-23 04:46:05:615 2044 e8c PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2009-10-23 04:46:05:615 2044 e8c PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://computerwsus/ClientWebService/client.asmx
    2009-10-23 04:46:05:756 2044 e8c PT WARNING: Cached cookie has expired or new PID is available
    2009-10-23 04:46:05:756 2044 e8c PT Initializing simple targeting cookie, clientId = 84763a01-0e3a-4fe2-9bea-02ec3c607844, target group = , DNS name = wsf7a20.computer.com
    2009-10-23 04:46:05:756 2044 e8c PT   Server URL = http://computerwsus/SimpleAuthWebService/SimpleAuth.asmx
    2009-10-23 04:46:41:288 2044 e8c PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2009-10-23 04:46:41:288 2044 e8c PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://computerwsus/ClientWebService/client.asmx
    2009-10-23 04:46:50:178 2044 e8c Agent   * Added update {3B151C1D-1C4E-492E-82A3-4BF70484841F}.100 to search result
    2009-10-23 04:46:50:178 2044 e8c Agent   * Found 1 updates and 51 categories in search; evaluated appl. rules of 1188 out of 2206 deployed entities
    2009-10-23 04:46:50:210 2044 e8c Agent *********
    2009-10-23 04:46:50:210 2044 e8c Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2009-10-23 04:46:50:210 2044 e8c Agent *************
    2009-10-23 04:46:50:225 2044 41c AU >>##  RESUMED  ## AU: Search for updates [CallId = {B3DC9565-3742-4DAE-B83B-5E78C7050A16}]
    2009-10-23 04:46:50:225 2044 41c AU   # 1 updates detected
    2009-10-23 04:46:50:225 2044 41c AU #########
    2009-10-23 04:46:50:225 2044 41c AU ##  END  ##  AU: Search for updates [CallId = {B3DC9565-3742-4DAE-B83B-5E78C7050A16}]
    2009-10-23 04:46:50:225 2044 41c AU #############
    2009-10-23 04:46:50:225 2044 41c AU AU setting next detection timeout to 2009-10-23 06:56:50
    2009-10-23 04:46:50:225 2044 41c AU Setting AU scheduled install time to 2009-10-23 07:00:00
    2009-10-23 04:46:55:194 2044 e8c Report REPORT EVENT: {1AEA964B-D66D-402C-B65F-7B809888B544} 2009-10-23 04:46:50:194+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 1 updates.
    2009-10-23 04:46:55:194 2044 e8c Report REPORT EVENT: {45AA2982-1A9F-49DE-A50B-787185020E52} 2009-10-23 04:46:50:210+0200 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
    2009-10-23 05:00:44:845 2044 e8c Report Uploading 2 events using cached cookie, reporting URL = http://computerwsus/ReportingWebService/ReportingWebService.asmx
    2009-10-23 05:00:44:861 2044 e8c Report Reporter successfully uploaded 2 events.
    2009-10-23 08:56:50:417 2044 6b4 AU #############
    2009-10-23 08:56:50:417 2044 6b4 AU ## START ##  AU: Search for updates
    2009-10-23 08:56:50:417 2044 6b4 AU #########
    2009-10-23 08:56:50:417 2044 6b4 AU <<## SUBMITTED ## AU: Search for updates [CallId = {7AC4E357-5764-4805-9411-E33F2FE09EE8}]
    2009-10-23 08:56:50:417 2044 17e4 Agent *************
    2009-10-23 08:56:50:417 2044 17e4 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2009-10-23 08:56:50:417 2044 17e4 Agent *********
    2009-10-23 08:56:50:417 2044 17e4 Agent   * Online = Yes; Ignore download priority = No
    2009-10-23 08:56:50:417 2044 17e4 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"
    2009-10-23 08:56:50:417 2044 17e4 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    2009-10-23 08:56:50:417 2044 17e4 Agent   * Search Scope = {Machine}
    2009-10-23 08:56:50:417 2044 17e4 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2009-10-23 08:56:50:417 2044 17e4 Misc  Microsoft signed: Yes
    2009-10-23 08:56:52:698 2044 17e4 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2009-10-23 08:56:52:698 2044 17e4 Misc  Microsoft signed: Yes
    2009-10-23 08:56:52:714 2044 17e4 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
    2009-10-23 08:56:52:714 2044 17e4 Misc  Microsoft signed: Yes
    2009-10-23 08:56:52:714 2044 17e4 Setup ***********  Setup: Checking whether self-update is required  ***********
    2009-10-23 08:56:52:714 2044 17e4 Setup   * Inf file: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
    2009-10-23 08:56:52:714 2044 17e4 Setup Update NOT required for C:\WINDOWS\system32\cdm.dll: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 08:56:52:714 2044 17e4 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 08:56:52:714 2044 17e4 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 08:56:52:714 2044 17e4 Setup Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 08:56:52:714 2044 17e4 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 08:56:52:714 2044 17e4 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 08:56:52:714 2044 17e4 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 08:56:52:714 2044 17e4 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 08:56:52:714 2044 17e4 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 08:56:52:714 2044 17e4 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 08:56:52:714 2044 17e4 Setup Update NOT required for C:\WINDOWS\system32\wups.dll: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 08:56:52:714 2044 17e4 Setup Update NOT required for C:\WINDOWS\system32\wups2.dll: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 08:56:52:730 2044 17e4 Setup Update NOT required for C:\WINDOWS\system32\wuweb.dll: target version = 7.2.6001.788, required version = 7.1.6001.65
    2009-10-23 08:56:52:730 2044 17e4 Setup   * IsUpdateRequired = No
    2009-10-23 08:57:00:058 2044 17e4 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2009-10-23 08:57:00:058 2044 17e4 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://computerwsus/ClientWebService/client.asmx
    2009-10-23 08:57:00:214 2044 17e4 PT WARNING: Cached cookie has expired or new PID is available
    2009-10-23 08:57:00:214 2044 17e4 PT Initializing simple targeting cookie, clientId = 84763a01-0e3a-4fe2-9bea-02ec3c607844, target group = , DNS name = wsf7a20.computer.com
    2009-10-23 08:57:00:214 2044 17e4 PT   Server URL = http://computerwsus/SimpleAuthWebService/SimpleAuth.asmx
    2009-10-23 08:57:36:011 2044 17e4 PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2009-10-23 08:57:36:011 2044 17e4 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://computerwsus/ClientWebService/client.asmx
    2009-10-23 08:57:44:887 2044 17e4 Agent   * Added update {3B151C1D-1C4E-492E-82A3-4BF70484841F}.100 to search result
    2009-10-23 08:57:44:887 2044 17e4 Agent   * Found 1 updates and 51 categories in search; evaluated appl. rules of 1188 out of 2206 deployed entities
    2009-10-23 08:57:44:902 2044 17e4 Agent *********
    2009-10-23 08:57:44:902 2044 17e4 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2009-10-23 08:57:44:902 2044 17e4 Agent *************
    2009-10-23 08:57:44:933 2044 a94 AU >>##  RESUMED  ## AU: Search for updates [CallId = {7AC4E357-5764-4805-9411-E33F2FE09EE8}]
    2009-10-23 08:57:44:933 2044 a94 AU   # 1 updates detected
    2009-10-23 08:57:44:933 2044 a94 AU #########
    2009-10-23 08:57:44:933 2044 a94 AU ##  END  ##  AU: Search for updates [CallId = {7AC4E357-5764-4805-9411-E33F2FE09EE8}]
    2009-10-23 08:57:44:933 2044 a94 AU #############
    2009-10-23 08:57:44:933 2044 a94 AU AU setting next detection timeout to 2009-10-23 11:46:57
    2009-10-23 08:57:44:933 2044 a94 AU Setting AU scheduled install time to 2009-10-23 07:00:00
    2009-10-23 08:57:49:902 2044 17e4 Report REPORT EVENT: {300E2433-57F0-4BB5-9F4E-2DC69CAB2941} 2009-10-23 08:57:44:902+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 1 updates.
    2009-10-23 08:57:49:902 2044 17e4 Report REPORT EVENT: {0AA8A5A2-9AB0-4833-AA50-80D3F1C78275} 2009-10-23 08:57:44:902+0200 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
    2009-10-23 09:00:10:013 2044 6b4 AU Forced install timer expired for scheduled install
    2009-10-23 09:00:10:013 2044 6b4 AU UpdateDownloadProperties: 0 download(s) are still in progress.
    2009-10-23 09:00:10:013 2044 6b4 AU #############
    2009-10-23 09:00:10:013 2044 6b4 AU ## START ##  AU: Install updates
    2009-10-23 09:00:10:013 2044 6b4 AU #########
    2009-10-23 09:00:10:013 2044 6b4 AU   # Initiating scheduled install
    2009-10-23 09:00:10:013 2044 6b4 AU   # Approved updates = 1
    2009-10-23 09:00:10:013 2044 6b4 AU <<## SUBMITTED ## AU: Install updates / installing updates [CallId = {8B4C90AF-07AE-4E1B-A778-ACB70B3B54DD}]
    2009-10-23 09:00:10:013 2044 994 Agent *************
    2009-10-23 09:00:10:013 2044 994 Agent ** START **  Agent: Installing updates [CallerId = AutomaticUpdates]
    2009-10-23 09:00:10:013 2044 994 Agent *********
    2009-10-23 09:00:10:013 2044 994 Agent   * Updates to install = 1
    2009-10-23 09:00:10:013 5568 1784 CltUI AU client got new directive = 'Shutdown', serviceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, return = 0x00000000
    2009-10-23 09:00:10:013 2044 6b4 AU AU received handle event
    2009-10-23 09:00:10:045 2044 994 Agent   *   Title = Update for Root Certificates
    2009-10-23 09:00:10:045 2044 994 Agent   *   UpdateId = {3B151C1D-1C4E-492E-82A3-4BF70484841F}.100
    2009-10-23 09:00:10:045 2044 994 Agent   *     Bundles 1 updates:
    2009-10-23 09:00:10:045 2044 994 Agent   *       {748226C3-998C-4C25-AD91-E681D9B8D3FB}.100
    2009-10-23 09:00:10:263 2044 994 DnldMgr Preparing update for install, updateId = {748226C3-998C-4C25-AD91-E681D9B8D3FB}.100.
    2009-10-23 09:00:10:279 2792 1304 Misc ===========  Logging initialized (build: 7.2.6001.788, tz: +0200)  ===========
    2009-10-23 09:00:10:279 2792 1304 Misc   = Process: C:\WINDOWS\system32\wuauclt.exe
    2009-10-23 09:00:10:279 2792 1304 Misc   = Module: C:\WINDOWS\system32\wuaueng.dll
    2009-10-23 09:00:10:279 2792 1304 Handler :::::::::::::
    2009-10-23 09:00:10:279 2792 1304 Handler :: START ::  Handler: Command Line Install
    2009-10-23 09:00:10:279 2792 1304 Handler :::::::::
    2009-10-23 09:00:10:279 2792 1304 Handler   : Updates to install = 1
    2009-10-23 09:00:10:857 2792 1304 Handler   : Command line install completed. Return code = 0x00000000, Result = Succeeded, Reboot required = false
    2009-10-23 09:00:10:857 2792 1304 Handler :::::::::
    2009-10-23 09:00:10:857 2792 1304 Handler ::  END  ::  Handler: Command Line Install
    2009-10-23 09:00:10:857 2792 1304 Handler :::::::::::::
    2009-10-23 09:00:10:873 2044 a94 AU >>##  RESUMED  ## AU: Installing update [UpdateId = {3B151C1D-1C4E-492E-82A3-4BF70484841F}, succeeded]
    2009-10-23 09:00:10:967 2044 994 Agent *********
    2009-10-23 09:00:10:967 2044 994 Agent **  END  **  Agent: Installing updates [CallerId = AutomaticUpdates]
    2009-10-23 09:00:10:967 2044 a94 AU Install call completed.
    2009-10-23 09:00:10:967 2044 994 Agent *************
    2009-10-23 09:00:10:967 2044 a94 AU   # WARNING: Install call completed, reboot required = No, error = 0x00000000
    2009-10-23 09:00:10:967 2044 a94 AU #########
    2009-10-23 09:00:10:967 2044 a94 AU ##  END  ##  AU: Installing updates [CallId = {8B4C90AF-07AE-4E1B-A778-ACB70B3B54DD}]
    2009-10-23 09:00:10:967 2044 a94 AU #############
    2009-10-23 09:00:10:982 2044 a94 AU Install complete for all calls, reboot NOT needed
    2009-10-23 09:00:10:982 2044 a94 AU Setting AU scheduled install time to 2009-10-24 07:00:00
    2009-10-23 09:00:10:982 2044 a94 AU Triggering Offline detection (non-interactive)
    2009-10-23 09:00:10:982 2044 6b4 AU #############
    2009-10-23 09:00:10:982 2044 6b4 AU ## START ##  AU: Search for updates
    2009-10-23 09:00:10:982 2044 6b4 AU #########
    2009-10-23 09:00:10:982 2044 6b4 AU <<## SUBMITTED ## AU: Search for updates [CallId = {54D794AE-F5F3-4A8D-81BF-CE309D4BF7A2}]
    2009-10-23 09:00:10:982 2044 17e4 Agent *************
    2009-10-23 09:00:10:982 2044 17e4 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2009-10-23 09:00:10:982 2044 17e4 Agent *********
    2009-10-23 09:00:10:982 2044 17e4 Agent   * Online = No; Ignore download priority = No
    2009-10-23 09:00:10:982 2044 17e4 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"
    2009-10-23 09:00:10:982 2044 17e4 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    2009-10-23 09:00:10:982 2044 17e4 Agent   * Search Scope = {Machine}
    2009-10-23 09:00:45:764 2044 17e4 Agent Update {4ED17338-4A74-4F8D-8187-DBFCEF0E8610}.100 is pruned out due to potential supersedence
    2009-10-23 09:00:45:764 2044 17e4 Agent Update {1BAC6A90-E250-4F1E-B254-5D076EFB2966}.100 is pruned out due to potential supersedence
    2009-10-23 09:00:45:764 2044 17e4 Agent   * Added update {20E6483F-EBA9-40D1-89F4-1940F79CBA3B}.101 to search result
    2009-10-23 09:00:45:764 2044 17e4 Agent   * Found 1 updates and 51 categories in search; evaluated appl. rules of 617 out of 2206 deployed entities
    2009-10-23 09:00:45:780 2044 17e4 Agent *********
    2009-10-23 09:00:45:780 2044 17e4 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2009-10-23 09:00:45:780 2044 17e4 Agent *************
    2009-10-23 09:00:45:811 2044 a94 AU >>##  RESUMED  ## AU: Search for updates [CallId = {54D794AE-F5F3-4A8D-81BF-CE309D4BF7A2}]
    2009-10-23 09:00:45:811 2044 a94 AU   # 1 updates detected
    2009-10-23 09:00:45:811 2044 17e4 Report REPORT EVENT: {52F3000E-E4DF-4D50-AFC1-D52936FC62BA} 2009-10-23 09:00:10:873+0200 1 190 101 {3B151C1D-1C4E-492E-82A3-4BF70484841F} 100 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Update for Root Certificates
    2009-10-23 09:00:45:811 2044 a94 AU #########
    2009-10-23 09:00:45:811 2044 a94 AU ##  END  ##  AU: Search for updates [CallId = {54D794AE-F5F3-4A8D-81BF-CE309D4BF7A2}]
    2009-10-23 09:00:45:811 2044 a94 AU #############
    2009-10-23 09:00:45:811 2044 a94 AU Setting AU scheduled install time to 2009-10-24 07:00:00
    2009-10-23 09:00:45:811 2044 a94 AU Auto-approving update for download, updateId = {20E6483F-EBA9-40D1-89F4-1940F79CBA3B}.101, ForUx=0, IsOwnerUx=0, HasDeadline=0, IsMinor=0
    2009-10-23 09:00:45:811 2044 a94 AU Auto-approved 1 update(s) for download (NOT for Ux)
    2009-10-23 09:00:45:811 2044 a94 AU #############
    2009-10-23 09:00:45:811 2044 a94 AU ## START ##  AU: Download updates
    2009-10-23 09:00:45:811 2044 a94 AU #########
    2009-10-23 09:00:45:811 2044 a94 AU   # Approved updates = 1
    2009-10-23 09:00:45:826 2044 a94 AU AU initiated download, updateId = {20E6483F-EBA9-40D1-89F4-1940F79CBA3B}.101, callId = {42A034E5-1019-49D8-9728-C089FDC3BBA1}
    2009-10-23 09:00:45:826 2044 a94 AU Setting AU scheduled install time to 2009-10-24 07:00:00
    2009-10-23 09:00:45:826 2044 a94 AU AU setting pending client directive to 'Download Progress'
    2009-10-23 09:00:45:826 2044 a94 AU   # Pending download calls = 1
    2009-10-23 09:00:45:826 2044 a94 AU <<## SUBMITTED ## AU: Download updates
    2009-10-23 09:00:45:842 2044 17e4 DnldMgr *************
    2009-10-23 09:00:45:842 2044 17e4 DnldMgr ** START **  DnldMgr: Downloading updates [CallerId = AutomaticUpdates]
    2009-10-23 09:00:45:842 2044 17e4 DnldMgr *********
    2009-10-23 09:00:45:842 2044 17e4 DnldMgr   * Call ID = {42A034E5-1019-49D8-9728-C089FDC3BBA1}
    2009-10-23 09:00:45:842 2044 17e4 DnldMgr   * Priority = 2, Interactive = 0, Owner is system = 1, Explicit proxy = 0, Proxy session id = -1, ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    2009-10-23 09:00:45:842 2044 17e4 DnldMgr   * Updates to download = 1
    2009-10-23 09:00:45:842 2044 17e4 Agent   *   Title = Update for Root Certificates [September 2009] (KB931125)
    2009-10-23 09:00:45:842 2044 17e4 Agent   *   UpdateId = {20E6483F-EBA9-40D1-89F4-1940F79CBA3B}.101
    2009-10-23 09:00:45:842 2044 17e4 Agent   *     Bundles 1 updates:
    2009-10-23 09:00:45:842 2044 17e4 Agent   *       {2D5D7333-4C16-40E8-891E-55E46D44E976}.101
    2009-10-23 09:00:45:842 2044 17e4 DnldMgr ***********  DnldMgr: New download job [UpdateId = {2D5D7333-4C16-40E8-891E-55E46D44E976}.101]  ***********
    2009-10-23 09:00:45:842 2044 17e4 DnldMgr   * All files for update were already downloaded and are valid.
    2009-10-23 09:00:45:842 2044 a94 AU >>##  RESUMED  ## AU: Download update [UpdateId = {20E6483F-EBA9-40D1-89F4-1940F79CBA3B}, succeeded]
    2009-10-23 09:00:45:842 2044 a94 AU #########
    2009-10-23 09:00:45:842 2044 a94 AU ##  END  ##  AU: Download updates
    2009-10-23 09:00:45:842 2044 a94 AU #############
    2009-10-23 09:00:45:842 2044 a94 AU Setting AU scheduled install time to 2009-10-24 07:00:00
    2009-10-23 09:00:45:842 2044 17e4 Agent *********
    2009-10-23 09:00:45:842 2044 17e4 Agent **  END  **  Agent: Downloading updates [CallerId = AutomaticUpdates]
    2009-10-23 09:00:45:842 2044 17e4 Agent *************
    2009-10-23 09:00:45:842 2044 a94 AU AU setting pending client directive to 'Install Approval'
    2009-10-23 09:00:50:842 2044 17e4 Report REPORT EVENT: {212BA0BB-64DD-4C84-8188-E034C40AF487} 2009-10-23 09:00:45:842+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on ?24 ?????? ?????, ?2009 at 09:00 ?:  - Update for Root Certificates [September 2009] (KB931125)
    2009-10-23 09:01:00:827 2044 6b4 AU Launched new AU client for directive 'Install Approval', session id = 0x0
    2009-10-23 09:01:00:873 6048 1034 Misc ===========  Logging initialized (build: 7.2.6001.788, tz: +0200)  ===========
    2009-10-23 09:01:00:873 6048 1034 Misc   = Process: C:\WINDOWS\system32\wuauclt.exe
    2009-10-23 09:01:00:873 6048 1034 AUClnt Launched Client UI process
    2009-10-23 09:01:00:905 6048 1034 Misc ===========  Logging initialized (build: 7.2.6001.788, tz: +0200)  ===========
    2009-10-23 09:01:00:905 6048 1034 Misc   = Process: C:\WINDOWS\system32\wuauclt.exe
    2009-10-23 09:01:00:905 6048 1034 Misc   = Module: C:\WINDOWS\system32\wucltui.dll
    2009-10-23 09:01:00:905 6048 1034 CltUI AU client got new directive = 'Install Approval', serviceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, return = 0x00000000
    2009-10-23 09:01:00:905 6048 1034 CltUI AU client creating default WU/WSUS UI plugin
    2009-10-23 09:11:39:538 2044 17e4 Report Uploading 3 events using cached cookie, reporting URL = http://computerwsus/ReportingWebService/ReportingWebService.asmx
    2009-10-23 09:11:39:538 2044 17e4 Report Reporter successfully uploaded 3 events.
    2009-10-23 09:27:06:206 2044 364 AU AU received install approval from client for 1 updates
    2009-10-23 09:27:06:206 2044 364 AU #############
    2009-10-23 09:27:06:206 2044 364 AU ## START ##  AU: Install updates
    2009-10-23 09:27:06:206 2044 364 AU #########
    2009-10-23 09:27:06:206 2044 364 AU   # Initiating manual install
    2009-10-23 09:27:06:206 2044 364 AU   # Approved updates = 1
    2009-10-23 09:27:06:237 2044 364 AU <<## SUBMITTED ## AU: Install updates / installing updates [CallId = {75B0F19A-0055-4F9F-A70B-53B9EEB2F8BC}]
    2009-10-23 09:27:06:237 2044 388 Agent *************
    2009-10-23 09:27:06:237 2044 388 Agent ** START **  Agent: Installing updates [CallerId = AutomaticUpdates]
    2009-10-23 09:27:06:237 2044 388 Agent *********
    2009-10-23 09:27:06:237 2044 388 Agent   * Updates to install = 1
    2009-10-23 09:27:06:550 2044 388 Agent   *   Title = Update for Root Certificates [September 2009] (KB931125)
    2009-10-23 09:27:06:550 2044 388 Agent   *   UpdateId = {20E6483F-EBA9-40D1-89F4-1940F79CBA3B}.101
    2009-10-23 09:27:06:550 2044 388 Agent   *     Bundles 1 updates:
    2009-10-23 09:27:06:550 2044 388 Agent   *       {2D5D7333-4C16-40E8-891E-55E46D44E976}.101
    2009-10-23 09:27:06:659 2044 388 Handler Attempting to create remote handler process as computer\mamo in session 0
    2009-10-23 09:27:06:862 2044 388 DnldMgr Preparing update for install, updateId = {2D5D7333-4C16-40E8-891E-55E46D44E976}.101.
    2009-10-23 09:27:06:862 3632 14c4 Misc ===========  Logging initialized (build: 7.2.6001.788, tz: +0200)  ===========
    2009-10-23 09:27:06:862 3632 14c4 Misc   = Process: C:\WINDOWS\system32\wuauclt.exe
    2009-10-23 09:27:06:862 3632 14c4 Misc   = Module: C:\WINDOWS\system32\wuaueng.dll
    2009-10-23 09:27:06:862 3632 14c4 Handler :::::::::::::
    2009-10-23 09:27:06:862 3632 14c4 Handler :: START ::  Handler: Command Line Install
    2009-10-23 09:27:06:862 3632 14c4 Handler :::::::::
    2009-10-23 09:27:06:862 3632 14c4 Handler   : Updates to install = 1
    2009-10-23 09:27:07:503 3632 14c4 Handler   : Command line install completed. Return code = 0x00000000, Result = Succeeded, Reboot required = false
    2009-10-23 09:27:07:503 3632 14c4 Handler :::::::::
    2009-10-23 09:27:07:503 3632 14c4 Handler ::  END  ::  Handler: Command Line Install
    2009-10-23 09:27:07:503 3632 14c4 Handler :::::::::::::
    2009-10-23 09:27:07:503 2044 1104 AU >>##  RESUMED  ## AU: Installing update [UpdateId = {20E6483F-EBA9-40D1-89F4-1940F79CBA3B}, succeeded]
    2009-10-23 09:27:07:659 2044 388 Agent *********
    2009-10-23 09:27:07:659 2044 388 Agent **  END  **  Agent: Installing updates [CallerId = AutomaticUpdates]
    2009-10-23 09:27:07:659 2044 388 Agent *************
    2009-10-23 09:27:07:659 2044 1104 AU Install call completed.
    2009-10-23 09:27:07:659 2044 1104 AU   # WARNING: Install call completed, reboot required = No, error = 0x00000000
    2009-10-23 09:27:07:659 2044 1104 AU #########
    2009-10-23 09:27:07:659 2044 1104 AU ##  END  ##  AU: Installing updates [CallId = {75B0F19A-0055-4F9F-A70B-53B9EEB2F8BC}]
    2009-10-23 09:27:07:659 2044 1104 AU #############
    2009-10-23 09:27:07:659 2044 1104 AU Install complete for all calls, reboot NOT needed
    2009-10-23 09:27:07:659 2044 1104 AU Setting AU scheduled install time to 2009-10-24 07:00:00
    2009-10-23 09:27:09:019 2044 a68 AU Triggering Offline detection (non-interactive)
    2009-10-23 09:27:09:034 2044 6b4 AU #############
    2009-10-23 09:27:09:034 2044 6b4 AU ## START ##  AU: Search for updates
    2009-10-23 09:27:09:034 2044 6b4 AU #########
    2009-10-23 09:27:09:034 2044 6b4 AU <<## SUBMITTED ## AU: Search for updates [CallId = {F6ECF133-794B-40DD-9E28-3A9648874EF5}]
    2009-10-23 09:27:09:034 2044 17e4 Agent *************
    2009-10-23 09:27:09:034 2044 17e4 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2009-10-23 09:27:09:034 2044 17e4 Agent *********
    2009-10-23 09:27:09:034 2044 17e4 Agent   * Online = No; Ignore download priority = No
    2009-10-23 09:27:09:034 2044 17e4 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"
    2009-10-23 09:27:09:034 2044 17e4 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    2009-10-23 09:27:09:034 6048 1034 CltUI AU client got new directive = 'Shutdown', serviceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, return = 0x00000000
    2009-10-23 09:27:09:034 2044 17e4 Agent   * Search Scope = {Machine}
    2009-10-23 09:27:09:081 2044 6b4 AU AU received handle event
    2009-10-23 09:27:53:910 2044 17e4 Agent   * Added update {3B151C1D-1C4E-492E-82A3-4BF70484841F}.100 to search result
    2009-10-23 09:27:53:910 2044 17e4 Agent   * Found 1 updates and 51 categories in search; evaluated appl. rules of 615 out of 2206 deployed entities
    2009-10-23 09:27:53:925 2044 17e4 Agent *********
    2009-10-23 09:27:53:925 2044 17e4 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2009-10-23 09:27:53:925 2044 17e4 Agent *************
    2009-10-23 09:27:53:957 2044 17e4 Report REPORT EVENT: {99235A45-4BB1-4496-8C7A-C4F955A760C7} 2009-10-23 09:27:07:503+0200 1 183 101 {20E6483F-EBA9-40D1-89F4-1940F79CBA3B} 101 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Update for Root Certificates [September 2009] (KB931125)
    2009-10-23 09:27:53:957 2044 1104 AU >>##  RESUMED  ## AU: Search for updates [CallId = {F6ECF133-794B-40DD-9E28-3A9648874EF5}]
    2009-10-23 09:27:53:957 2044 1104 AU   # 1 updates detected
    2009-10-23 09:27:53:957 2044 1104 AU #########
    2009-10-23 09:27:53:957 2044 1104 AU ##  END  ##  AU: Search for updates [CallId = {F6ECF133-794B-40DD-9E28-3A9648874EF5}]
    2009-10-23 09:27:53:957 2044 1104 AU #############
    2009-10-23 09:27:53:957 2044 1104 AU Setting AU scheduled install time to 2009-10-24 07:00:00
    2009-10-23 09:27:53:957 2044 1104 AU Auto-approving update for download, updateId = {3B151C1D-1C4E-492E-82A3-4BF70484841F}.100, ForUx=0, IsOwnerUx=0, HasDeadline=0, IsMinor=0
    2009-10-23 09:27:53:957 2044 1104 AU Auto-approved 1 update(s) for download (NOT for Ux)
    2009-10-23 09:27:53:957 2044 1104 AU #############
    2009-10-23 09:27:53:957 2044 1104 AU ## START ##  AU: Download updates
    2009-10-23 09:27:53:957 2044 1104 AU #########
    2009-10-23 09:27:53:957 2044 1104 AU   # Approved updates = 1
    2009-10-23 09:27:53:957 2044 1104 AU AU initiated download, updateId = {3B151C1D-1C4E-492E-82A3-4BF70484841F}.100, callId = {A90B3B31-8CBC-4263-AFFB-E7C34D619D0F}
    2009-10-23 09:27:53:957 2044 1104 AU Setting AU scheduled install time to 2009-10-24 07:00:00
    2009-10-23 09:27:53:957 2044 1104 AU AU setting pending client directive to 'Download Progress'
    2009-10-23 09:27:53:957 2044 1104 AU   # Pending download calls = 1
    2009-10-23 09:27:53:957 2044 1104 AU <<## SUBMITTED ## AU: Download updates
    2009-10-23 09:27:54:035 2044 17e4 DnldMgr *************
    2009-10-23 09:27:54:035 2044 17e4 DnldMgr ** START **  DnldMgr: Downloading updates [CallerId = AutomaticUpdates]
    2009-10-23 09:27:54:035 2044 17e4 DnldMgr *********
    2009-10-23 09:27:54:035 2044 17e4 DnldMgr   * Call ID = {A90B3B31-8CBC-4263-AFFB-E7C34D619D0F}
    2009-10-23 09:27:54:035 2044 17e4 DnldMgr   * Priority = 2, Interactive = 0, Owner is system = 1, Explicit proxy = 0, Proxy session id = -1, ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    2009-10-23 09:27:54:035 2044 17e4 DnldMgr   * Updates to download = 1
    2009-10-23 09:27:54:035 2044 17e4 Agent   *   Title = Update for Root Certificates
    2009-10-23 09:27:54:035 2044 17e4 Agent   *   UpdateId = {3B151C1D-1C4E-492E-82A3-4BF70484841F}.100
    2009-10-23 09:27:54:035 2044 17e4 Agent   *     Bundles 1 updates:
    2009-10-23 09:27:54:035 2044 17e4 Agent   *       {748226C3-998C-4C25-AD91-E681D9B8D3FB}.100
    2009-10-23 09:27:54:050 2044 17e4 DnldMgr ***********  DnldMgr: New download job [UpdateId = {748226C3-998C-4C25-AD91-E681D9B8D3FB}.100]  ***********
    2009-10-23 09:27:54:050 2044 17e4 DnldMgr   * All files for update were already downloaded and are valid.
    2009-10-23 09:27:54:050 2044 1104 AU >>##  RESUMED  ## AU: Download update [UpdateId = {3B151C1D-1C4E-492E-82A3-4BF70484841F}, succeeded]
    2009-10-23 09:27:54:050 2044 17e4 Agent *********
    2009-10-23 09:27:54:050 2044 17e4 Agent **  END  **  Agent: Downloading updates [CallerId = AutomaticUpdates]
    2009-10-23 09:27:54:050 2044 17e4 Agent *************
    2009-10-23 09:27:54:050 2044 1104 AU #########
    2009-10-23 09:27:54:050 2044 1104 AU ##  END  ##  AU: Download updates
    2009-10-23 09:27:54:050 2044 1104 AU #############
    2009-10-23 09:27:54:050 2044 1104 AU Setting AU scheduled install time to 2009-10-24 07:00:00
    2009-10-23 09:27:54:050 2044 1104 AU AU setting pending client directive to 'Install Approval'
    2009-10-23 09:27:59:050 2044 17e4 Report REPORT EVENT: {27201FB0-189E-4616-8909-14D8B6CB935E} 2009-10-23 09:27:54:050+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on ?24 ?????? ?????, ?2009 at 09:00 ?:  - Update for Root Certificates
    2009-10-23 09:28:08:957 2044 6b4 AU Launched new AU client for directive 'Install Approval', session id = 0x0
    2009-10-23 09:28:09:004 5868 a10 Misc ===========  Logging initialized (build: 7.2.6001.788, tz: +0200)  ===========
    2009-10-23 09:28:09:004 5868 a10 Misc   = Process: C:\WINDOWS\system32\wuauclt.exe
    2009-10-23 09:28:09:004 5868 a10 AUClnt Launched Client UI process
    2009-10-23 09:28:09:035 5868 a10 Misc ===========  Logging initialized (build: 7.2.6001.788, tz: +0200)  ===========
    2009-10-23 09:28:09:035 5868 a10 Misc   = Process: C:\WINDOWS\system32\wuauclt.exe
    2009-10-23 09:28:09:035 5868 a10 Misc   = Module: C:\WINDOWS\system32\wucltui.dll
    2009-10-23 09:28:09:035 5868 a10 CltUI AU client got new directive = 'Install Approval', serviceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, return = 0x00000000
    2009-10-23 09:28:09:035 5868 a10 CltUI AU client creating default WU/WSUS UI plugin
    2009-10-23 09:33:47:399 2044 364 AU AU received install approval from client for 1 updates
    2009-10-23 09:33:47:399 2044 364 AU #############
    2009-10-23 09:33:47:399 2044 364 AU ## START ##  AU: Install updates
    2009-10-23 09:33:47:399 2044 364 AU #########
    2009-10-23 09:33:47:399 2044 364 AU   # Initiating manual install
    2009-10-23 09:33:47:399 2044 364 AU   # Approved updates = 1
    2009-10-23 09:33:47:430 2044 364 AU <<## SUBMITTED ## AU: Install updates / installing updates [CallId = {CDF072A4-6406-404D-9E75-835C56533F6A}]
    2009-10-23 09:33:47:430 2044 388 Agent *************
    2009-10-23 09:33:47:430 2044 388 Agent ** START **  Agent: Installing updates [CallerId = AutomaticUpdates]
    2009-10-23 09:33:47:430 2044 388 Agent *********
    2009-10-23 09:33:47:430 2044 388 Agent   * Updates to install = 1
    2009-10-23 09:33:47:742 2044 388 Agent   *   Title = Update for Root Certificates
    2009-10-23 09:33:47:742 2044 388 Agent   *   UpdateId = {3B151C1D-1C4E-492E-82A3-4BF70484841F}.100
    2009-10-23 09:33:47:742 2044 388 Agent   *     Bundles 1 updates:
    2009-10-23 09:33:47:742 2044 388 Agent   *       {748226C3-998C-4C25-AD91-E681D9B8D3FB}.100
    2009-10-23 09:33:47:836 2044 388 Handler Attempting to create remote handler process as computer\mamo in session 0
    2009-10-23 09:33:48:039 2044 388 DnldMgr Preparing update for install, updateId = {748226C3-998C-4C25-AD91-E681D9B8D3FB}.100.
    2009-10-23 09:33:48:039 2720 16f0 Misc ===========  Logging initialized (build: 7.2.6001.788, tz: +0200)  ===========
    2009-10-23 09:33:48:039 2720 16f0 Misc   = Process: C:\WINDOWS\system32\wuauclt.exe
    2009-10-23 09:33:48:039 2720 16f0 Misc   = Module: C:\WINDOWS\system32\wuaueng.dll
    2009-10-23 09:33:48:039 2720 16f0 Handler :::::::::::::
    2009-10-23 09:33:48:039 2720 16f0 Handler :: START ::  Handler: Command Line Install
    2009-10-23 09:33:48:039 2720 16f0 Handler :::::::::
    2009-10-23 09:33:48:039 2720 16f0 Handler   : Updates to install = 1
    2009-10-23 09:33:48:664 2720 16f0 Handler   : Command line install completed. Return code = 0x00000000, Result = Succeeded, Reboot required = false
    2009-10-23 09:33:48:664 2720 16f0 Handler :::::::::
    2009-10-23 09:33:48:664 2720 16f0 Handler ::  END  ::  Handler: Command Line Install
    2009-10-23 09:33:48:664 2720 16f0 Handler :::::::::::::
    2009-10-23 09:33:48:680 2044 1104 AU >>##  RESUMED  ## AU: Installing update [UpdateId = {3B151C1D-1C4E-492E-

  • viernes, 23 de octubre de 2009 14:41Lawrence GarvinMVP, ModeradorMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     Respondida
    2009-10-23 09:00:10:013 2044 6b4 AU Forced install timer expired for scheduled install
    2009-10-23 09:00:10:013 2044 6b4 AU UpdateDownloadProperties: 0 download(s) are still in progress.
    2009-10-23 09:00:10:013 2044 6b4 AU #############
    2009-10-23 09:00:10:013 2044 6b4 AU ## START ##  AU: Install updates
    2009-10-23 09:00:10:013 2044 6b4 AU #########
    2009-10-23 09:00:10:013 2044 6b4 AU   # Initiating scheduled install
    2009-10-23 09:00:10:013 2044 6b4 AU   # Approved updates = 1
    2009-10-23 09:00:10:013 2044 6b4 AU <<## SUBMITTED ## AU: Install updates / installing updates [CallId = {8B4C90AF-07AE-4E1B-A778-ACB70B3B54DD}]
    2009-10-23 09:00:10:013 2044 994 Agent *************
    2009-10-23 09:00:10:013 2044 994 Agent ** START **  Agent: Installing updates [CallerId = AutomaticUpdates]
    2009-10-23 09:00:10:013 2044 994 Agent *********
    2009-10-23 09:00:10:013 2044 994 Agent   * Updates to install = 1
    2009-10-23 09:00:10:013 5568 1784 CltUI AU client got new directive = 'Shutdown', serviceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, return = 0x00000000
    2009-10-23 09:00:10:013 2044 6b4 AU AU received handle event
    2009-10-23 09:00:10:045 2044 994 Agent   *   Title = Update for Root Certificates
    2009-10-23 09:00:10:045 2044 994 Agent   *   UpdateId = {3B151C1D-1C4E-492E-82A3-4BF70484841F}.100
    2009-10-23 09:00:10:045 2044 994 Agent   *     Bundles 1 updates:
    2009-10-23 09:00:10:045 2044 994 Agent   *       {748226C3-998C-4C25-AD91-E681D9B8D3FB}.100
    2009-10-23 09:00:10:263 2044 994 DnldMgr Preparing update for install, updateId = {748226C3-998C-4C25-AD91-E681D9B8D3FB}.100.
    2009-10-23 09:00:10:279 2792 1304 Misc ===========  Logging initialized (build: 7.2.6001.788, tz: +0200)  ===========
    2009-10-23 09:00:10:279 2792 1304 Misc   = Process: C:\WINDOWS\system32\wuauclt.exe
    2009-10-23 09:00:10:279 2792 1304 Misc   = Module: C:\WINDOWS\system32\wuaueng.dll
    2009-10-23 09:00:10:279 2792 1304 Handler :::::::::::::
    2009-10-23 09:00:10:279 2792 1304 Handler :: START ::  Handler: Command Line Install
    2009-10-23 09:00:10:279 2792 1304 Handler :::::::::
    2009-10-23 09:00:10:279 2792 1304 Handler   : Updates to install = 1
    2009-10-23 09:00:10:857 2792 1304 Handler   : Command line install completed. Return code = 0x00000000, Result = Succeeded, Reboot required = false
    2009-10-23 09:00:10:857 2792 1304 Handler :::::::::
    2009-10-23 09:00:10:857 2792 1304 Handler ::  END  ::  Handler: Command Line Install
    2009-10-23 09:00:10:857 2792 1304 Handler :::::::::::::
    2009-10-23 09:00:10:873 2044 a94 AU >>##  RESUMED  ## AU: Installing update [UpdateId = {3B151C1D-1C4E-492E-82A3-4BF70484841F}, succeeded]
    2009-10-23 09:00:10:967 2044 994 Agent *********
    2009-10-23 09:00:10:967 2044 994 Agent **  END  **  Agent: Installing updates [CallerId = AutomaticUpdates]
    2009-10-23 09:00:10:967 2044 a94 AU Install call completed.
    2009-10-23 09:00:10:967 2044 994 Agent *************
    2009-10-23 09:00:10:967 2044 a94 AU   # WARNING: Install call completed, reboot required = No, error = 0x00000000
    2009-10-23 09:00:10:967 2044 a94 AU #########
    2009-10-23 09:00:10:967 2044 a94 AU ##  END  ##  AU: Installing updates [CallId = {8B4C90AF-07AE-4E1B-A778-ACB70B3B54DD}]
    2009-10-23 09:00:10:967 2044 a94 AU #############
    2009-10-23 09:00:10:982 2044 a94 AU Install complete for all calls, reboot NOT needed


    2009-10-23 09:00:45:811 2044 17e4 Report REPORT EVENT: {52F3000E-E4DF-4D50-AFC1-D52936FC62BA} 2009-10-23 09:00:10:873+0200 1 190 101 {3B151C1D-1C4E-492E-82A3-4BF70484841F} 100 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Update for Root Certificates


    The installation was successful; looks like the metadata may have a defective isInstalled rule and is not properly detecting that the update is already installed.

    A quick fix for this is to create a special group on WSUS just for this update. Approve the update only for that group, and then ADD your XP machines to that group until this update successfully installed. One you know the update has been downloaded/installed successfully then remove the machine from the group.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
  • martes, 24 de noviembre de 2009 7:08Mohammed A. Yassin Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    I have the same problem, this update has been installed 100 times on my machine so far, i have download it as stand alone and installed it, and my machine is still detecting that its needed, any solution?
  • martes, 24 de noviembre de 2009 7:33ChristianM82 Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    Weeks ago, I have deployed this Update (september2009) by WSUS. Today +600 Clients are reporting this update to install and keep asking to reinstall.
  • martes, 24 de noviembre de 2009 8:25Yusuf BS Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    I have the exact same problem, anyone?
  • martes, 24 de noviembre de 2009 8:35UBeierlei Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    Hello,

    I have the same problem. What I tried so far:
    - Cleaned the WSUS Server (remove obsolete patches, computers, etc.)
    - Reseted the WSUS Server via "wsusutil.exe reset"
    - Restarted the "Update Service" several times (Server)
    - Restarted the "Automatic Updates Service" several times (Client)
    - Declined that update for every computer (followed by restart of services)

    C:\WINDOWS\SoftwareDistribution\ReportingEvents.log of such a client:

    vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
    {A99DC7FB-4196-47A0-A895-47B61A459B33}    2009-11-24 07:54:27:277+0100    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows Update Client successfully detected 1 updates.
    {BDA4B731-3D95-4193-9101-3240FB2EA714}    2009-11-24 07:54:27:277+0100    1    156    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Pre-Deployment Check    Reporting client status.
    {9063203A-F30F-4528-AE34-52BC049CDCB9}    2009-11-24 07:54:56:105+0100    1    162    101    {4ED17338-4A74-4F8D-8187-DBFCEF0E8610}    100    0    AutomaticUpdates    Success    Content Download    Download succeeded.
    {DF5A98F5-9108-4848-9D1B-36D086F44E0C}    2009-11-24 07:54:56:105+0100    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Dienstag, 24. November 2009 at 11:00:  - Update für Stammzertifikate
    {E78BCA09-D71E-4324-93FD-A38813751B55}    2009-11-24 08:18:25:257+0100    1    183    101    {4ED17338-4A74-4F8D-8187-DBFCEF0E8610}    100    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Update für Stammzertifikate
    {53B77D73-BF42-41A1-855A-5110BA1E4240}    2009-11-24 08:18:55:617+0100    1    162    101    {20E6483F-EBA9-40D1-89F4-1940F79CBA3B}    101    0    AutomaticUpdates    Success    Content Download    Download succeeded.
    {D1C4C069-0333-4938-8030-503C095023AF}    2009-11-24 08:18:55:617+0100    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Dienstag, 24. November 2009 at 11:00:  - Update für Stammzertifikate [September 2009] (KB931125)
    {D19C5018-2851-4BCC-8640-74E80829DF81}    2009-11-24 08:19:28:245+0100    1    183    101    {20E6483F-EBA9-40D1-89F4-1940F79CBA3B}    101    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Update für Stammzertifikate [September 2009] (KB931125)
    {A8632C66-EDC6-42BA-841E-6F5634BF1E42}    2009-11-24 08:19:36:311+0100    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Dienstag, 24. November 2009 at 11:00:  - Update für Stammzertifikate
    {69EEB5B8-CECC-4B48-B6CE-C4A11696B0BF}    2009-11-24 08:27:47:189+0100    1    183    101    {4ED17338-4A74-4F8D-8187-DBFCEF0E8610}    100    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Update für Stammzertifikate
    {92FA9D4D-20E9-41BB-BBBA-DCEAA8853204}    2009-11-24 08:28:14:256+0100    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Dienstag, 24. November 2009 at 11:00:  - Update für Stammzertifikate [September 2009] (KB931125)
    {463732C9-8F33-4224-BEE7-A76D9962EF91}    2009-11-24 08:32:43:300+0100    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Dienstag, 24. November 2009 at 11:00:  - Update für Stammzertifikate [September 2009] (KB931125)
    {F0BE337E-C87C-49FB-AEF3-AB7118B6DE76}    2009-11-24 08:36:45:242+0100    1    183    101    {20E6483F-EBA9-40D1-89F4-1940F79CBA3B}    101    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Update für Stammzertifikate [September 2009] (KB931125)
    {616A8B0E-C898-4316-A061-0E7B8DD65778}    2009-11-24 08:37:10:167+0100    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Dienstag, 24. November 2009 at 11:00:  - Update für Stammzertifikate
    {FF841562-6F44-4913-8BB2-DC65074E3C95}    2009-11-24 08:50:29:741+0100    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Dienstag, 24. November 2009 at 11:00:  - Update für Stammzertifikate
    {FE6E0B23-BE38-4596-A646-FFDFFF3F54BD}    2009-11-24 08:51:12:591+0100    1    183    101    {4ED17338-4A74-4F8D-8187-DBFCEF0E8610}    100    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Update für Stammzertifikate
    {90EE18F8-7588-47B7-B5A0-052790527886}    2009-11-24 08:51:56:457+0100    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Dienstag, 24. November 2009 at 11:00:  - Update für Stammzertifikate [September 2009] (KB931125)
    {66A88EB0-D53C-40E9-BC7F-205DEF5D97AB}    2009-11-24 09:07:17:954+0100    1    183    101    {20E6483F-EBA9-40D1-89F4-1940F79CBA3B}    101    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Update für Stammzertifikate [September 2009] (KB931125)
    {7CAD2C5B-2E48-4C0D-BDFA-FBF13B86C326}    2009-11-24 09:07:39:781+0100    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Dienstag, 24. November 2009 at 11:00:  - Update für Stammzertifikate
    {7E9984D4-8165-48E8-A00C-1E3D6E9E6EA8}    2009-11-24 09:19:33:640+0100    1    183    101    {4ED17338-4A74-4F8D-8187-DBFCEF0E8610}    100    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Update für Stammzertifikate
    {465F3132-DE2A-4E3B-A452-18FF5789B049}    2009-11-24 09:19:57:887+0100    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Dienstag, 24. November 2009 at 11:00:  - Update für Stammzertifikate [September 2009] (KB931125)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

    I do not want to reinstall WSUS - did someone manage to get rid of that problem?
  • martes, 24 de noviembre de 2009 8:49Mandesk Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    I to am having this problem. Started this morning, could be a dodgy update...
  • martes, 24 de noviembre de 2009 9:19Mandesk Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    According to my WSUS Server 1 new update was downloaded last night @02.00, this was for Defender. But 1 Update for ROOT Certificates [MAY 2009] {KB931125} was expired. Maybe this has cuased the updates to redeploy.
  • martes, 24 de noviembre de 2009 9:22Ade234 Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    Yep exactly the same 1 here, MS has got their update IDs mixed up I bet!
  • martes, 24 de noviembre de 2009 9:43Mandesk Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    Just pointed a PC that wants to reinstall the root certs at Microsft Update site and it is saying that I do not need the root cert update. So can only think it is a wsus reporting/id issue. How do we tell Microsft that there is a real issue here?
  • martes, 24 de noviembre de 2009 9:44MarkPT Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    Nothing new to add, just to confirm we are seeing the same issues, cycling round the Root Certificate Update from Feb 2009 and the September 2009 one. All following the sync on the May 09 expired update.
  • martes, 24 de noviembre de 2009 9:52-Kent- Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    Same problem here. Didn't investigate the issue yet.
  • martes, 24 de noviembre de 2009 9:57Pverst Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    Also the same here, further no new info
  • martes, 24 de noviembre de 2009 10:00Mike SSAB Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    The solution for me was to deny rotcertifikaten for May 2009 and Feb 2009.
    Sept. 2009 certificate must be approved

  • martes, 24 de noviembre de 2009 11:01justforthispost Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    The solution for me was to deny rotcertifikaten for May 2009 and Feb 2009.
    Sept. 2009 certificate must be approved


    I disabled all updates wich mentioned Root certificates on my WSUS. Only allowed this one:

    Title = Update for Root Certificates [September 2009] (KB931125)
    UpdateId = {20E6483F-EBA9-40D1-89F4-1940F79CBA3B}.101
    Bundles 1 updates:
    {2D5D7333-4C16-40E8-891E-55E46D44E976}.101


     to install. This update installes and then I'll get a notification for another update:


    Title = Update for Root Certificates
    UpdateId = {4ED17338-4A74-4F8D-8187-DBFCEF0E8610}.100
    Bundles 1 updates:
    {F0963D12-3B3D-4F37-B312-62FF7EBCF335}.100


    This second update is declined in my WSUS. This proces keeps continuing.

    As all the other people above mentioned, this is happening since this morning.
  • martes, 24 de noviembre de 2009 12:36JimPayne Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    I've been struggling with the same problem since this morning. I'm using a WSUS server and unapproved all Root updates (I colud only find 2, Februrary and September) but still the darn thing keeps rolling around. It alternates between an "Update for Root certificates" and "update for root certificates (September)". I switched off the WSUS server but this doesn't seem to make any difference so I guess there's cached updates somewhere !
  • martes, 24 de noviembre de 2009 13:11Party_kroos Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    Have the same problem, 350 xp computers... is there any solution yet?
  • martes, 24 de noviembre de 2009 14:00UBeierlei Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    Hello,

    In the hope that I can deploy a registry key via group policy to tell the update that it is already installed,
    I've traced the activity of "C:\WINDOWS\SoftwareDistribution\Download\Install\rootsupd.exe" using procmon.

    But unfortunately, the update just *writes* to the registry key
    "HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{EF289A85-8E57-408d-BE47-73B55609861A}\IsInstalled"
    but never *reads* it.
  • martes, 24 de noviembre de 2009 14:20Eduardo Menegalli Nazato Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    Same problems, and same behaviors here.
    The (partial) solution was declining every 931125 update, except for the September 2009 one. But all the machines that had already downloaded the older updates still have to install them several times before the update warning finally disappear.
  • martes, 24 de noviembre de 2009 14:48UBeierlei Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    After declining all but the September-Update, the behaviour is still the same - at my site.
    Even declining all 931125-updates did not cure the disease.
  • martes, 24 de noviembre de 2009 15:00Laslon Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    When you write declining all 931125 uppdates. How many are there?? 
    I Can find only two. So 1 is decline feb 2009 but the problems is still there.

    Looks like its stucked in the local computer update
  • martes, 24 de noviembre de 2009 15:20jjstok Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    Same problem here for 2000+ machines. Hopefully MS will pick up on this thread....???
  • martes, 24 de noviembre de 2009 15:21Mike SSAB Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     Respuesta propuesta
    The solution for me was to deny root certificate for May 2009 and Feb 2009.
    Sept. 2009 certificate must be approved. Depending on how often contact is made with the WSUS server, I recommend a reboot of the computer. After that is done there should be only root certificates Sept. 2009 to install. This solved the installation of 2,500 computers.
    • Propuesto como respuestaJen Jen MI martes, 24 de noviembre de 2009 16:45
    •  
  • martes, 24 de noviembre de 2009 15:21UBeierlei Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    Once all 931125-updates have been declined, it seems to be enough to clear
    the log of the automatic update service on the clients, as suggested in here:
    http://en.kioskea.net/faq/sujet-1242-clear-history-updates-with-vista .

    As a (temporary) workaround, I've added the following commands to the logon-script:

    net stop wuauserv
    del "%SystemRoot%\SoftwareDistribution\DataStore\Logs\edb.log"
    net start wuauserv

    ( I think that workaround will become a permanent solution, once I forgot that issue -
      most probably, tomorrow :-)

  • martes, 24 de noviembre de 2009 15:37Mick M. Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    I'm having the same issue with 11 of my machines on my 75 machine network.  I hope MSFT picks up on this one because it's annoying.
  • martes, 24 de noviembre de 2009 15:45Kevin Krasie Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    Having the same issue...took one PC out of the OU for WSUS updates and manually ran windows update...the same thing occurs...each time I search for updates I get one of the two Root Cert updates and that loop continues.  I dont think it is WSUS related.
  • martes, 24 de noviembre de 2009 16:04Party_kroos Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     

    I did as "Mike SSAB" deny root certificate for May 2009 in Wsus and only approved september 2009,
    this works fine after restarts of the machines, did a "shutdown and install updates" (Only tested on 3 machines) lets se if the problem is gone tomorow...

  • martes, 24 de noviembre de 2009 16:08Kevin Krasie Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    I did the same as Mike SSAB also so that the end user is not continually prompted for install of repeated updates...manual windows update continues to cycle between the two updates.
  • martes, 24 de noviembre de 2009 16:26Beaver Tech Guy Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    The solution for me was to deny root certificate for May 2009 and Feb 2009.
    Sept. 2009 certificate must be approved. Depending on how often contact is made with the WSUS server, I recommend a reboot of the computer. After that is done there should be only root certificates Sept. 2009 to install. This solved the installation of 2,500 computers.

    Worked for me.
  • martes, 24 de noviembre de 2009 16:30Kevin Krasie Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    Hey Beaver...just curious...when you say worked for you, does that mean the arent recycling using WSUS and if you go directly to Windows update using IE it doesnt find those updates as available?

  • martes, 24 de noviembre de 2009 16:41SkipPile Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     

    On the client machines where I've had this problem, I re-installed the Windows Update Agent.  You can get that here: http://support.microsoft.com/default.aspx/kb/949104.  You will need to use the /wuforce switch to force it to re-install.  After re-installation, I no longer had the root certificate update looping.

  • martes, 24 de noviembre de 2009 16:46Jen Jen MI Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    The solution for me was to deny root certificate for May 2009 and Feb 2009.
    Sept. 2009 certificate must be approved. Depending on how often contact is made with the WSUS server, I recommend a reboot of the computer. After that is done there should be only root certificates Sept. 2009 to install. This solved the installation of 2,500 computers.

    Worked for me.

    Yes, worked for me also.  Once your computers go through their next update cycle (which you can force with "wuauclt /detectnow" as I am doing right now), the shield and repeated install attempts will be gone.  Thanks all!
  • martes, 24 de noviembre de 2009 16:56Haris Alatovic Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    As Mike SSAB wrote seems to be solution. When I applied what Mike SSAB wrote it did not work. In addition, I have declined "Update for Root Certificate" which is also referenced as 931125 and it is superseded by Feb 2009 or May 2009. Actually, it is necessary to manualy decline all superseded 931125 updates and approve only current one i.e. September 2009. This solved the installation of 150+ computers.
  • martes, 24 de noviembre de 2009 17:01Kevin Krasie Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    Hello Haris...could you tell me if you went to one client PC and ran windows updates from IE will it find and loop the Root Cert updates?  I know we are talking about fixing WSUS so it doesnt continue, which I have, but I still see both updates appearing using Windows Updates, do you have the same issue?

    THanks,

  • martes, 24 de noviembre de 2009 17:23Haris Alatovic Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    Hello Kevin,

    You are right about endless loop for Root Cert update through Microsoft Update site. Probably there is some error in these Root Cert updates and I expect that Microsoft will fix it.


  • martes, 24 de noviembre de 2009 17:25Kevin Krasie Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    TY...fixed the WSUS issue but still saw that issue using win updates...thanks again for confirming!
  • martes, 24 de noviembre de 2009 18:19Lawrence GarvinMVP, ModeradorMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     

    Just to add fat to the frying pan.

    There is now a *NOVEMBER* update to KB931125, scheduled for release today (Last Tuesday of month):


    Update for Root Certificates [November 2009] (KB931125)

    Locale: All
    Deployment: Windows Update, Microsoft Update, Optional Installation, WSUS, and Catalog
    Classification: Updates, Non-Security
    Supersedes: KB931125 on Windows XP
    Target platforms: Windows XP
    Approximate file sizes:
    Windows XP update: ~ 324KB
    Description:
    This item updates the list of root certificates on your computer to the list that is accepted by Microsoft as part of the Microsoft Root Certificate Program. Adding additional root certificates to your computer enables you to use Extended Validation (EV) certificates in Internet Explorer 7, a greater range of security enhanced Web browsing, encrypted e-mail, and security enhanced code delivery. After you install this item, you may have to restart your computer. Once you have installed this item, it cannot be removed.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
  • martes, 24 de noviembre de 2009 19:01Eduardo Menegalli Nazato Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    Lawrence, will we need to decline the "Update for Root Certificates [September 2009]" to keep the problem solved? Any chance to the ever-installing-update problem happen again from now?
  • martes, 24 de noviembre de 2009 19:07Todd Siskin Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     

    We have experienced the same problem with February and September cyclically installing.  Declining the February update in WSUS seems to have alleviated the problem, once each workstation checks in with our WSUS server subsequent to the decline.

    Thank you all for your comments and advice on this issue.

  • martes, 24 de noviembre de 2009 19:34Reksbar Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    We are not seeing the problem go away.  After declining the Update for Root Certificates for May and February and approving the Update for Root Certificates [September 2009]" we are still continually getting the update notice after rebooting the client computers.
  • martes, 24 de noviembre de 2009 20:29jpochedl Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     

    I synced our WSUS server, declined all previous versions of the update, and approved the November 2009 version (the one just released today, per Lawrence's note a few responses prior).  

    So far the couple clients we've had check for updates (wuauclt /detectnow) have all downloaded the November version, installed it, and then not prompted for further updates or to re-apply the old updates...

    Mind that it's been a limited test with only a handful of clients, but so far so good for us.

  • martes, 24 de noviembre de 2009 22:06Lawrence GarvinMVP, ModeradorMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    Lawrence, will we need to decline the "Update for Root Certificates [September 2009]" to keep the problem solved? Any chance to the ever-installing-update problem happen again from now?

    There's *always* a chance of any update having bad behavior. Each update is built in its own little isolated world, sometimes, perhaps, even by different people. Ideally appropriate Q.A. would prevent such things from happening, as would appropriate pre-deployment testing, but lately that seems to be slipping a bit. This, of course, is why it's recommended to implement LOCAL TESTING before deploying updates to PRODUCTION systems! :-)

    Specifically to the question though, it appears to me that the problem is caused by the following:
    1. A metadata defect in the May 2009 update.
    2. Microsoft *expired* the May 2009 update, but despite the update being expired, and superceded by the September 2009 update, some WSUS Administrators failed to decline the May 2009 update. As unforgiving as it may sound, the functional cause of this situation was having not declined the May 2009 update when the September 2009 update became available and the May 2009 update was shown as expired.

    In addition, I just earlier discovered that the Nov 2009 update was actually released last week -- and promptly expired -- as it, also, had a similar (but not identical) metadata defect. Presumably a repaired Nov 2009 update is in the works and should show up in the catalog in the immediate future.

    When the November 2009 update is released (and functional), and shows the Sep 2009 update as superceded, then *YES*  -- I would recommend declining the Sep 2009 update -- not because of any risks of recurrence of this issue, but because declining a Never-Needed-Again superceded update is the appropriate administrative action for the WSUS environment.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com