locked
WSUS updates/computers with errors RRS feed

  • Question

  • I have WSUS setup and of late i have noticed several computer updates have errors,this means that the updates are not being installed..

    I cant figure why this could be the case..please see the attached screenshot.Kindly advise.


    Wednesday, March 19, 2014 12:58 PM

Answers

  • see attached log file..it's quite long...

    This log file does not cover the installation events for the two listed updates that failed, thus it'll be mostly useless in this converation (even assuming the WindowsUpdate.log would provide any relevant information about an update installation failure -- typically it does not).

    The first step in any installation failure is to determine why it is failing. The best way to do that is to go to the system in question (or Remote Desktop) and install the update using the Control Panel -> Windows Update applet ... which sometimes will provide more relevant information related to the failure.

    One common cause for update installation failures of OS updates on Windows 7 systems is a corrupted CBS, so it's almost standard practice now to also run the lastest System Update Readiness Tool (which can be obtained from the Microsoft Download Center).

    The other thing to do is to research community resources and see if others have experienced any issues with the update(s). So far, I have not seen any reported issues with these updates.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by Daniel JiSun Thursday, March 27, 2014 6:35 AM
    Tuesday, March 25, 2014 3:40 PM

All replies

  • Hi,

    According to the picture we can see KB2929733 and KB2930275 failed. In order to diagnose the reason why it is failed, we should check windowsupdate.log of your client.

    So could share a snippet contain these errors with us?

    Thursday, March 20, 2014 6:24 AM
  • Yes i can share.The queer thing is that this failure to install started in one machine only.. and now the other computers ,some are getting the same error message.

    see attached log file..it's quite long...

    2014-03-19 09:47:18:158 712 e50 Agent *********
    2014-03-19 09:47:18:158 712 e50 Agent  * Updates to install = 1
    2014-03-19 09:47:18:463 712 e50 Agent  *   Title = Update for Microsoft InfoPath 2010 (KB2817369) 32-Bit Edition
    2014-03-19 09:47:18:463 712 e50 Agent  *   UpdateId = {7982F5F8-EA1F-403C-A0F3-6533439E935A}.200
    2014-03-19 09:47:18:463 712 e50 Agent  *     Bundles 1 updates:
    2014-03-19 09:47:18:463 712 e50 Agent  *       {1D985CFF-82C7-4BC9-B068-5738069688EA}.200
    2014-03-19 09:47:38:335 712 e50 DnldMgr Preparing update for install, updateId = {1D985CFF-82C7-4BC9-B068-5738069688EA}.200.
    2014-03-19 09:47:38:336 2760 18c4 Misc ===========  Logging initialized (build: 7.6.7600.256, tz: +0300)  ===========
    2014-03-19 09:47:38:336 2760 18c4 Misc  = Process: C:\Windows\system32\wuauclt.exe
    2014-03-19 09:47:38:336 2760 18c4 Misc  = Module: C:\Windows\system32\wuaueng.dll
    2014-03-19 09:47:38:336 2760 18c4 Handler :::::::::::::
    2014-03-19 09:47:38:337 2760 18c4 Handler :: START ::  Handler: MSI Install
    2014-03-19 09:47:38:337 2760 18c4 Handler :::::::::
    2014-03-19 09:47:38:337 2760 18c4 Handler  : Updates to install = 1
    2014-03-19 09:47:38:371 2760 18c4 Handler Extracting MSP file stored in CAB ipeditor-x-none.cab
    2014-03-19 09:47:39:675 2760 18c4 Handler MSP update {00000000-0000-0000-0000-000000000000}.0 using full-file patch
    2014-03-19 09:47:39:675 2760 18c4 Handler  : Batch installing 1 updates
    2014-03-19 09:47:39:866 2760 18c4 Handler List of MSPs in transaction:
    2014-03-19 09:47:39:866 2760 18c4 Handler  C:\Windows\SoftwareDistribution\Download\9574b3c7b6909aacca488b65d38c056f\img\ipeditor-x-none.MSP
    2014-03-19 09:47:39:866 2760 18c4 Handler MSP final command line: DISABLESRCPROMPT=1 LOCALCACHESRCRES=0 NOLOCALCACHEROLLBACK=1 REBOOT=REALLYSUPPRESS 

    MSIRESTARTMANAGERCONTROL=Disable
    2014-03-19 09:47:44:109 2760 18c4 Handler MSP Error List:
    2014-03-19 09:47:44:109 2760 18c4 Handler  No messages in the MSP error list.
    2014-03-19 09:47:44:109 2760 18c4 Handler  : MSI transaction completed. MSI: 0x80070659, Handler: 0x8024200b, Source: No, Reboot: 0
    2014-03-19 09:47:44:109 2760 18c4 Handler  : WARNING: First failure for update {1D985CFF-82C7-4BC9-B068-5738069688EA}, transaction error = 0x8024200b, MSI result 

    = 0x80070659, MSI action = 
    2014-03-19 09:47:44:109 712 7e0 AU >>##  RESUMED  ## AU: Installing update [UpdateId = {7982F5F8-EA1F-403C-A0F3-6533439E935A}]
    2014-03-19 09:47:44:109 712 7e0 AU  # WARNING: Install failed, error = 0x80070659 / 0x80070659
    2014-03-19 09:47:44:163 2760 18c4 Handler  : WARNING: Operation failed at update 0, Exit code = 0x8024200B
    2014-03-19 09:47:44:163 2760 18c4 Handler :::::::::
    2014-03-19 09:47:44:163 2760 18c4 Handler ::  END  ::  Handler: MSI Install
    2014-03-19 09:47:44:163 2760 18c4 Handler :::::::::::::
    2014-03-19 09:47:45:749 712 e50 Agent *********
    2014-03-19 09:47:45:749 712 7e0 AU Install call completed.
    2014-03-19 09:47:45:749 712 e50 Agent **  END  **  Agent: Installing updates [CallerId = AutomaticUpdates]
    2014-03-19 09:47:45:749 712 7e0 AU  # WARNING: Install call completed, reboot required = No, error = 0x00000000
    2014-03-19 09:47:45:749 712 e50 Agent *************
    2014-03-19 09:47:45:749 712 7e0 AU #########
    2014-03-19 09:47:45:749 712 7e0 AU ##  END  ##  AU: Installing updates [CallId = {3201BFB1-CC8E-467F-899A-5CE8B7E25299}]
    2014-03-19 09:47:45:749 712 7e0 AU #############
    2014-03-19 09:47:45:749 712 7e0 AU Install complete for all calls, reboot NOT needed
    2014-03-19 09:47:45:750 712 7e0 AU Successfully wrote event for AU health state:0
    2014-03-19 09:47:46:215 712 7e0 AU AU setting pending client directive to 'Install Approval'
    2014-03-19 09:47:46:257 712 7e0 AU Successfully wrote event for AU health state:0
    2014-03-19 09:47:46:257 712 7e0 AU Triggering Offline detection (non-interactive)
    2014-03-19 09:47:46:257 712 1388 AU #############
    2014-03-19 09:47:46:257 712 1388 AU ## START ##  AU: Search for updates
    2014-03-19 09:47:46:257 712 1388 AU #########
    2014-03-19 09:47:46:363 712 1388 AU <<## SUBMITTED ## AU: Search for updates [CallId = {D7EF9052-66B3-4C11-91A9-ECF1E5DE4D4D}]
    2014-03-19 09:47:46:363 712 1cf4 Agent *************
    2014-03-19 09:47:46:363 712 1cf4 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-03-19 09:47:46:363 712 1cf4 Agent *********
    2014-03-19 09:47:46:363 712 1cf4 Agent  * Online = No; Ignore download priority = No
    2014-03-19 09:47:46:363 712 1cf4 Agent  * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or 

    IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2014-03-19 09:47:46:363 712 1cf4 Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-03-19 09:47:46:363 712 1cf4 Agent  * Search Scope = {Machine}
    2014-03-19 09:47:52:999 712 1388 AU Forced install timer expired for deadline install
    2014-03-19 09:47:52:999 712 1388 AU UpdateDownloadProperties: 0 download(s) are still in progress.
    2014-03-19 09:47:52:999 712 1388 AU #############
    2014-03-19 09:47:52:999 712 1388 AU ## START ##  AU: Install updates
    2014-03-19 09:47:52:999 712 1388 AU #########
    2014-03-19 09:47:52:999 712 1388 AU  # Initiating deadline install
    2014-03-19 09:47:52:999 712 1388 AU  # Approved updates = 1
    2014-03-19 09:47:53:000 712 1388 AU <<## SUBMITTED ## AU: Install updates / installing updates [CallId = {D6D6659B-E948-4DEA-9C20-78AB87F344E3}]
    2014-03-19 09:47:53:000 712 e50 Agent *************
    2014-03-19 09:47:53:000 712 e50 Agent ** START **  Agent: Installing updates [CallerId = AutomaticUpdates]
    2014-03-19 09:47:53:000 712 e50 Agent *********
    2014-03-19 09:47:53:000 712 e50 Agent  * Updates to install = 1
    2014-03-19 09:47:53:004 712 e50 Agent  *   Title = Update for Microsoft OneNote 2010 (KB2837595) 32-Bit Edition
    2014-03-19 09:47:53:004 712 e50 Agent  *   UpdateId = {6CC3FFC4-27B9-4F6E-A869-B23B7F509259}.200
    2014-03-19 09:47:53:005 712 e50 Agent  *     Bundles 1 updates:
    2014-03-19 09:47:53:005 712 e50 Agent  *       {08691BE4-B386-4109-8080-0CB7B8FC0B77}.200
    2014-03-19 09:48:04:955 712 e50 DnldMgr Preparing update for install, updateId = {08691BE4-B386-4109-8080-0CB7B8FC0B77}.200.
    2014-03-19 09:48:05:133 4184 1930 Misc ===========  Logging initialized (build: 7.6.7600.256, tz: +0300)  ===========
    2014-03-19 09:48:05:133 4184 1930 Misc  = Process: C:\Windows\system32\wuauclt.exe
    2014-03-19 09:48:05:133 4184 1930 Misc  = Module: C:\Windows\system32\wuaueng.dll
    2014-03-19 09:48:05:132 4184 1930 Handler :::::::::::::
    2014-03-19 09:48:05:133 4184 1930 Handler :: START ::  Handler: MSI Install
    2014-03-19 09:48:05:133 4184 1930 Handler :::::::::
    2014-03-19 09:48:05:133 4184 1930 Handler  : Updates to install = 1
    2014-03-19 09:48:05:134 4184 1930 Handler Extracting MSP file stored in CAB onenote-x-none.cab
    2014-03-19 09:48:09:611 4184 1930 Handler MSP update {00000000-0000-0000-0000-000000000000}.0 using full-file patch
    2014-03-19 09:48:09:611 4184 1930 Handler  : Batch installing 1 updates
    2014-03-19 09:48:10:512 4184 1930 Handler List of MSPs in transaction:
    2014-03-19 09:48:10:512 4184 1930 Handler  C:\Windows\SoftwareDistribution\Download\1e5344c0a4f9072e2414dd1a144025c3\img\onenote-x-none.MSP
    2014-03-19 09:48:10:512 4184 1930 Handler MSP final command line: DISABLESRCPROMPT=1 LOCALCACHESRCRES=0 NOLOCALCACHEROLLBACK=1 REBOOT=REALLYSUPPRESS 

    MSIRESTARTMANAGERCONTROL=Disable
    2014-03-19 09:48:12:668 4184 1930 Handler MSP Error List:
    2014-03-19 09:48:12:668 4184 1930 Handler  No messages in the MSP error list.
    2014-03-19 09:48:12:668 4184 1930 Handler  : MSI transaction completed. MSI: 0x80070659, Handler: 0x8024200b, Source: No, Reboot: 0



    Thursday, March 20, 2014 6:57 AM
  • see attached log file..it's quite long...

    This log file does not cover the installation events for the two listed updates that failed, thus it'll be mostly useless in this converation (even assuming the WindowsUpdate.log would provide any relevant information about an update installation failure -- typically it does not).

    The first step in any installation failure is to determine why it is failing. The best way to do that is to go to the system in question (or Remote Desktop) and install the update using the Control Panel -> Windows Update applet ... which sometimes will provide more relevant information related to the failure.

    One common cause for update installation failures of OS updates on Windows 7 systems is a corrupted CBS, so it's almost standard practice now to also run the lastest System Update Readiness Tool (which can be obtained from the Microsoft Download Center).

    The other thing to do is to research community resources and see if others have experienced any issues with the update(s). So far, I have not seen any reported issues with these updates.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by Daniel JiSun Thursday, March 27, 2014 6:35 AM
    Tuesday, March 25, 2014 3:40 PM