Windows 7 Updates kb2943357 & kb2973112 Fails with Error 800B0100


  1. Posts : 5
    Windows 7 - mixed environment x64 and x86
       #1

    Windows 7 Updates kb2943357 & kb2973112 Fails with Error 800B0100


    I have looked through the threads and copied the Checksur Manifests and Servicing files, as suggested, that have been posted here and reran the readiness tool, but the updates still fail. Attached are the logs. Thank you for your help.
    Windows 7 Updates kb2943357 & kb2973112 Fails with Error 800B0100 Attached Files
      My Computer


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

    The CheckSUR log shows the following problems (as you probably noticed!)
    Code:
    Unavailable repair files:
     winsxs\manifests\amd64_microsoft.transactions.bridge.dtc_b03f5f7f11d50a3a_6.1.7601.22733_none_65085bdd54b4a629.manifest
     winsxs\manifests\amd64_wcf-m_sm_ins_rc_dll_31bf3856ad364e35_6.1.7601.22733_none_2795328d79930284.manifest
     winsxs\manifests\amd64_wcf-system.runtime.serialization.ref_b03f5f7f11d50a3a_6.1.7601.22733_none_424d323c8e896dad.manifest
     winsxs\manifests\amd64_wcf-icardres_dll_vista_31bf3856ad364e35_6.1.7601.18523_none_6f276a738180cba8.manifest
     winsxs\manifests\amd64_wcf-smdiagnostics_b03f5f7f11d50a3a_6.1.7601.18523_none_f5ee0756c06c09cd.manifest
     winsxs\manifests\amd64_wcf-m_sm_ins_rc_dll_31bf3856ad364e35_6.1.7601.18523_none_271663c8606d49a2.manifest
     winsxs\manifests\amd64_wcf-infocard_api_dll_31bf3856ad364e35_6.1.7601.18523_none_02011939c648dcfe.manifest
     winsxs\manifests\amd64_wcf-icardagt_exe_31bf3856ad364e35_6.1.7601.22733_none_907097fea175fea2.manifest
     winsxs\manifests\amd64_wcf-system.runtime.serialization_b03f5f7f11d50a3a_6.1.7601.22733_none_7d243f06e2816846.manifest
     winsxs\manifests\amd64_wcf-m_sm_cfg_ins_exe_31bf3856ad364e35_6.1.7601.22733_none_5eba49464cf449c9.manifest
     winsxs\manifests\amd64_wcf-m_sm_mof_31bf3856ad364e35_6.1.7601.22733_none_230aba46aff3690d.manifest
     winsxs\manifests\amd64_wcf-infocard_api_dll_31bf3856ad364e35_6.1.7601.22733_none_027fe7fedf6e95e0.manifest
     winsxs\manifests\amd64_wcf-smsvchost_b03f5f7f11d50a3a_6.1.7601.22733_none_b0fabad924c43863.manifest
     winsxs\manifests\amd64_wcf-icardagt_exe_31bf3856ad364e35_6.1.7601.18523_none_8ff1c939885045c0.manifest
     winsxs\manifests\amd64_wcf-m_sm_cfg_ins_exe_31bf3856ad364e35_6.1.7601.18523_none_5e3b7a8133ce90e7.manifest
     winsxs\manifests\amd64_wcf-system.runtime.serialization_b03f5f7f11d50a3a_6.1.7601.18523_none_93f0e5a0c8daee98.manifest
     winsxs\manifests\amd64_wcf-smsvchost_b03f5f7f11d50a3a_6.1.7601.18523_none_c7c761730b1dbeb5.manifest
     winsxs\manifests\amd64_wcf-system.identitymodel_b03f5f7f11d50a3a_6.1.7601.22733_none_9b8bf7be024ae1df.manifest
     winsxs\manifests\amd64_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_6.1.7601.22733_none_0476f2837b6cca3b.manifest
     winsxs\manifests\amd64_wcf-m_sm_evt_dll_vista_31bf3856ad364e35_6.1.7601.18523_none_d6844f55af0a470f.manifest
     winsxs\manifests\amd64_wcf-system.servicemodel.ref_b03f5f7f11d50a3a_6.1.7601.18523_none_758bd1fd19f87e7f.manifest
     winsxs\manifests\amd64_wcf-m_sm_mof_31bf3856ad364e35_6.1.7601.18523_none_228beb8196cdb02b.manifest
     winsxs\manifests\amd64_wcf-icardres_dll_vista_31bf3856ad364e35_6.1.7601.22733_none_6fa639389aa6848a.manifest
     winsxs\manifests\amd64_wcf-m_sm_evt_dll_vista_31bf3856ad364e35_6.1.7601.22733_none_d7031e1ac82ffff1.manifest
     winsxs\manifests\amd64_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_6.1.7601.18523_none_03f823be62471159.manifest
     winsxs\manifests\amd64_wcf-system.runtime.serialization.ref_b03f5f7f11d50a3a_6.1.7601.18523_none_5919d8d674e2f3ff.manifest
     winsxs\manifests\amd64_wcf-smdiagnostics_b03f5f7f11d50a3a_6.1.7601.22733_none_df2160bcda12837b.manifest
     winsxs\manifests\amd64_wcf-system.identitymodel_b03f5f7f11d50a3a_6.1.7601.18523_none_b2589e57e8a46831.manifest
    However, what more interesting to me is the results of a coupe of earlier scans you did...

    The first on Jan 7 gave this Summary (the one on Jan 8 was simply a cleaned-up run of the same system)
    Code:
    Summary:
    Seconds executed: 2833
     Found 230 errors
     Fixed 145 errors
      CSI Manifest All Zeros Total count: 65
      CSI Catalog Corrupt Total count: 8
      Fixed: CSI Catalog Corrupt.  Total count: 8
      CSI F Mark Missing Total count: 43
      Fixed: CSI F Mark Missing.  Total count: 43
      CBS MUM Corrupt Total count: 10
      CBS Catalog Corrupt Total count: 10
      CSI Catalog Thumbprint Invalid Total count: 94
      Fixed: CSI Catalog Thumbprint Invalid.  Total count: 94
    The second, on April 30 gave this... (and the latest scan is a cleaned-up version of this one)
    Code:
    Summary:
    Seconds executed: 1307
     Found 104 errors
     Fixed 76 errors
      CSI Manifest All Zeros Total count: 65
      Fixed: CSI Manifest All Zeros.  Total count: 37
      CSI F Mark Missing Total count: 29
      Fixed: CSI F Mark Missing.  Total count: 29
      CBS MUM Corrupt Total count: 10
      Fixed: CBS MUM Corrupt.  Total count: 10
      Fixed: CBS Paired File.  Total count: 10
    Since all runs were done using the same version of CheckSUR, this means that something is repeatedly corrupting installs through Windows Updates.

    I'll post a fix protocol later.
      My Computer


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

    I've uploaded a file - jsmaa.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 jsmaa in the same place.
    Open this folder - there should be one folder inside it (Manifests, )

    Copy 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.

    The run an SFC /SCANNOW, and post the new CBS.log file, and we'll see what else needs fixing (if anything)
      My Computer


  4. Posts : 5
    Windows 7 - mixed environment x64 and x86
    Thread Starter
       #4

    Attached are the updated CheckSur logs. The CBS logs are too big to attach. The SFC /SCANNOW did not return any errors. Thanks!
    Windows 7 Updates kb2943357 & kb2973112 Fails with Error 800B0100 Attached Files
      My Computer


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

    Here's the CheckSUR log summary...
    Summary:
    Seconds executed: 1339
    Found 54 errors
    Fixed 54 errors
    CSI Manifest All Zeros Total count: 28
    Fixed: CSI Manifest All Zeros. Total count: 28
    CSI F Mark Missing Total count: 26
    Fixed: CSI F Mark Missing. Total count: 26
    There appear to be no remaining errors, so with any luck, Windows Update should work now.

    do a Check for updates, and then attempt to install ONLY the oldest update - what happens? If it installs OK, try the rest.
      My Computer


  6. Posts : 5
    Windows 7 - mixed environment x64 and x86
    Thread Starter
       #6

    The oldest update (KB2943357) installed successfully now. The newer one (KB2973112) still fails. Thank you.
      My Computer


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

    Please post your C:\Windows\windowsupdate.log file
      My Computer


  8. Posts : 5
    Windows 7 - mixed environment x64 and x86
    Thread Starter
       #8

    Windows Update log file is attached. Thanks.
    Windows 7 Updates kb2943357 & kb2973112 Fails with Error 800B0100 Attached Files
      My Computer


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

    One surprising thing strikes me immediately - you are still using a very old Windows Update Agent version.

    It would be a good idea to update to the latest version - http://download.windowsupdate.com/wi...nt-7.6-x64.exe

    ( I have no idea why it hasn't already installed - it should have done so more than a year ago!)
      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 12:51.
Find Us