WUpdates fail, error code 80073712


  1. Posts : 5
    Windows 7 Pro SP1 64 bit
       #1

    WUpdates fail, error code 80073712


    Windows Updates fail with error code 80073712. Have deleted Software Distribution, stopped and restarted the Windows Update service, SUR tool installed and ran, SFC /scannow reports no integrity violations. CBS log file attached for DISM.exe /Online /Cleanup-image /Scanhealth

    DISM.exe /Online /Cleanup-image /Restorehealth
    Error: 87
    The restorehealth option is not recognized in this context.
    For mor information, refer to the help.
    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
      My Computer


  2. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #2

    CheckSUR found the followingproblems...
    Code:
    Unavailable repair files:
     winsxs\manifests\amd64_microsoft-windows-w..lient-ui.deployment_31bf3856ad364e35_7.6.7600.320_none_2bc45c3e65319d38.manifest
     winsxs\manifests\amd64_microsoft-windows-w..oyment-languagepack_31bf3856ad364e35_7.6.7600.320_en-us_9480e83e143a2b9d.manifest
     winsxs\manifests\amd64_microsoft-windows-w..ent-core.deployment_31bf3856ad364e35_7.6.7600.320_none_af4247f6d9404079.manifest
     winsxs\manifests\amd64_microsoft-windows-w..-activex.deployment_31bf3856ad364e35_7.6.7600.320_none_3bdffcf0c6c9baea.manifest
     winsxs\manifests\amd64_microsoft-windows-w..oyment-languagepack_31bf3856ad364e35_7.6.7600.320_en-us_f472bced9fa3f21b.manifest
     winsxs\manifests\amd64_microsoft-windows-w..oyment-languagepack_31bf3856ad364e35_7.6.7600.320_en-us_743e1b456f9dad72.manifest
     winsxs\manifests\amd64_microsoft-windows-w..oyment-languagepack_31bf3856ad364e35_7.6.7600.320_en-us_7f238fa6bfd1b97a.manifest
     winsxs\manifests\amd64_microsoft-windows-w..date-adm.deployment_31bf3856ad364e35_7.6.7600.320_none_2c005c4c3b15478b.manifest
     winsxs\manifests\amd64_microsoft-windows-w..ient-aux.deployment_31bf3856ad364e35_7.6.7600.320_none_0999a9f081cc9852.manifest
     winsxs\manifests\wow64_microsoft-windows-w..owsupdateclient-aux_31bf3856ad364e35_7.6.7600.320_none_c65c31ce99b0eafe.manifest
     winsxs\manifests\amd64_microsoft-windows-windowsupdateclient-ui_31bf3856ad364e35_7.6.7600.320_none_53a370daf19412b1.manifest
     winsxs\manifests\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7600.320_none_d5f64d30518fd000.manifest
     winsxs\manifests\amd64_microsoft-windows-w..pdate-adm.resources_31bf3856ad364e35_7.6.7600.320_en-us_8521eb3f6ab8462d.manifest
     winsxs\manifests\amd64_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_7.6.7600.320_none_661247bd0b075aff.manifest
     winsxs\manifests\wow64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7600.320_en-us_dfecc4b83531fac7.manifest
     winsxs\manifests\amd64_microsoft-windows-w..client-ui.resources_31bf3856ad364e35_7.6.7600.320_en-us_3cc2c1c213d77748.manifest
     winsxs\manifests\wow64_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_7.6.7600.320_none_7066f20f3f681cfa.manifest
     winsxs\manifests\amd64_microsoft-windows-windowsupdate-adm_31bf3856ad364e35_7.6.7600.320_none_92880415bab4fe68.manifest
     winsxs\manifests\amd64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7600.320_en-us_d5981a6600d138cc.manifest
     winsxs\manifests\amd64_microsoft-windows-w..owsupdateclient-aux_31bf3856ad364e35_7.6.7600.320_none_bc07877c65502903.manifest
     winsxs\manifests\amd64_microsoft-windows-w..ient-core.resources_31bf3856ad364e35_7.6.7600.320_en-us_2b6abab786297fc7.manifest
     servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
     servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
     servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
     servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
    I'll post a fix protocol tomorrow.
      My Computer


  3. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #3

    I've uploaded a file - sttaa.zip - to my OneDrive at Noel's OneDrive
    Please download and save it.
    Right-click on the downloaded file, and select Extract all…
    Extract to the default location - which will create a new folder sttaa in the same place.
    Open this folder - there should be two folders inside it (Manifests, and Packages)

    Copy the content of the Packages folder to the folder
    C:\Windows\Temp\CheckSur\Servicing\Packages

    And the content of the manifests folder (.manifest files) into this folder:

    C:\Windows\Temp\CheckSur\Winsxs\Manifests

    Now run the CheckSUR tool again (it may take a while)

    Post the new CheckSUR.log file, and the CheckSUR.persist.log file.
      My Computer


  4. Posts : 5
    Windows 7 Pro SP1 64 bit
    Thread Starter
       #4

    This is a work machine. Will be applying your suggestions and posting update after the weekend. Thank you, thank you!
      My Computer


  5. Posts : 5
    Windows 7 Pro SP1 64 bit
    Thread Starter
       #5

    I have copied the contents and ran DISM.exe /Online /Cleanup-image /Scanhealth

    The Checksur and Checksur.persist files are attached. They are named Checksur2.zip and Checksur2.persist.zip

    Interestingly enough, the same lines appear in the CheckSur file as before.
    Last edited by shetektn; 24 Oct 2014 at 12:32. Reason: missing information
      My Computer


  6. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #6

    WTH did you run DISM for?
    Please read the instructions.
    ChecSUR is NOT DISM.
      My Computer


  7. Posts : 5
    Windows 7 Pro SP1 64 bit
    Thread Starter
       #7

    CheckSUR ran. Files attached.
      My Computer


  8. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #8

    The CheckSUR summary looks like this...
    Code:
    Summary:
    Seconds executed: 640
     Found 53 errors
     Fixed 35 errors
      CSI Manifest Missing Total count: 21
      Fixed: CSI Manifest Missing.  Total count: 21
      CSI Payload File Missing Total count: 20
      Fixed: CSI Payload File Missing.  Total count: 2
      CSI Store Directory Missing Total count: 12
      Fixed: CSI Store Directory Missing.  Total count: 12
    There are still 18 Payload file errors - but we need to get a new SFC /SCANNOW result first, as these errors will significantly affect that.

    Please run SFC /SCANNOW again and post the new CBS.log file
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:30.
Find Us