Code 800b0100: Windows Encountered an unkown error

Page 1 of 2 12 LastLast

  1. Posts : 52
    Windows 7 64bit
       #1

    Code 800b0100: Windows Encountered an unkown error


    I am having issues installing Windows update and I keep getting "Code 800b0100: Windows Encountered an unkown error".
    I have ran the Download System Update Readiness Tool for Windows 7 and that fixed another error that was coming up before but I am now getting this one.

    I also ran the "sfc /scannow" and got "Windows Resource Protection did not find any integrity violations" at the end.

    Attaching the CBS folder as well as the list of updates it is failing on.

    Thanks in advance!
      My Computer


  2. Posts : 52
    Windows 7 64bit
    Thread Starter
       #2

    i also tried to install updates manually but it fails
      My Computer


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

    You appear to have some fairly serious corruption.
    Code:
    Summary:
    Seconds executed: 1150
     Found 80 errors
      CSI Manifest All Zeros Total count: 36
      CBS MUM Corrupt Total count: 22
      CBS Catalog Corrupt Total count: 22
    Unavailable repair files:
     winsxs\manifests\amd64_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.18637_en-us_b818f58670898bbd.manifest
     winsxs\manifests\amd64_microsoft-windows-a..de-compat-telemetry_31bf3856ad364e35_6.1.7601.18653_none_e5a5eb8210168b23.manifest
     winsxs\manifests\amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.22843_none_80a46a3e85194f37.manifest
     winsxs\manifests\amd64_microsoft-windows-a..ence-telemetry-sdbs_31bf3856ad364e35_6.1.7601.18653_none_661d8f7a60be9912.manifest
     winsxs\manifests\amd64_microsoft-windows-msauditevtlog_31bf3856ad364e35_6.1.7601.22843_none_25d0997ea843ed32.manifest
     winsxs\manifests\x86_microsoft-windows-msauditevtlog_31bf3856ad364e35_6.1.7601.18637_none_c937305dd6bd2876.manifest
     winsxs\manifests\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7601.18637_none_ecb2935b6af13c52.manifest
     winsxs\manifests\wow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7601.18637_none_f7073dad9f51fe4d.manifest
     winsxs\manifests\x86_microsoft-windows-c..ityclient.resources_31bf3856ad364e35_6.1.7601.22843_en-us_672eda97174dc073.manifest
     winsxs\manifests\amd64_microsoft-windows-lsa.resources_31bf3856ad364e35_6.1.7601.22843_en-us_e535f381c671cf9d.manifest
     winsxs\manifests\amd64_microsoft-windows-c..ityclient.resources_31bf3856ad364e35_6.1.7601.22843_en-us_c34d761acfab31a9.manifest
     winsxs\manifests\wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.18637_none_0eb286a7a7d91f21.manifest
     winsxs\manifests\wow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.22843_none_4fb9a6ae1504ca69.manifest
     winsxs\manifests\x86_microsoft-windows-security-credssp_31bf3856ad364e35_6.1.7601.22843_none_c627b51c19090c11.manifest
     winsxs\manifests\amd64_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.22843_none_bc6c74c221728719.manifest
     winsxs\manifests\amd64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.22843_none_db410c0392613b8e.manifest
     winsxs\manifests\amd64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.22843_none_995b6a47ac8b8c3f.manifest
     winsxs\manifests\wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.22843_none_0f2d5444c10272a7.manifest
     winsxs\manifests\amd64_microsoft-windows-security-credssp_31bf3856ad364e35_6.1.7601.22843_none_2246509fd1667d47.manifest
     winsxs\manifests\amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.22843_none_4564fc5be0a4086e.manifest
     winsxs\manifests\amd64_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.22843_none_360bd4ac6c7e009c.manifest
     winsxs\manifests\amd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.22843_none_04d8a9f28ca1b0ac.manifest
     winsxs\manifests\x86_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.22843_none_604dd93e691515e3.manifest
     winsxs\manifests\wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.22843_none_8af91490b97a1132.manifest
     winsxs\manifests\wow64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.22843_none_e595b655c6c1fd89.manifest
     winsxs\manifests\wow64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.22843_none_a3b01499e0ec4e3a.manifest
     winsxs\manifests\x86_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.22843_en-us_5c75279fd1556e0d.manifest
     winsxs\manifests\amd64_microsoft-windows-msauditevtlog_31bf3856ad364e35_6.1.7601.18637_none_2555cbe18f1a99ac.manifest
     winsxs\manifests\x86_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.22843_none_d9ed3928b4208f66.manifest
     winsxs\manifests\x86_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.18637_en-us_5bfa5a02b82c1a87.manifest
     winsxs\manifests\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7601.22843_none_ed2d60f8841a8fd8.manifest
     winsxs\manifests\wow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7601.22843_none_f7820b4ab87b51d3.manifest
     winsxs\manifests\amd64_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.22843_en-us_b893c32389b2df43.manifest
     winsxs\manifests\amd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.18637_none_045ddc5573785d26.manifest
     winsxs\manifests\amd64_microsoft-windows-a..rience-program-data_31bf3856ad364e35_6.1.7601.18653_none_cf6202c799c9818b.manifest
     winsxs\manifests\x86_microsoft-windows-msauditevtlog_31bf3856ad364e35_6.1.7601.22843_none_c9b1fdfaefe67bfc.manifest
     servicing\packages\Package_105_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_105_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_106_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_106_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_107_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_107_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_108_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_108_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_109_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_109_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_111_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_111_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_112_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_112_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_113_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_113_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_114_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_114_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_115_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_115_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.6.1.mum
     servicing\packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.6.1.mum
     servicing\packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.6.1.mum
     servicing\packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.6.1.mum
     servicing\packages\Package_49_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_49_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_50_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_50_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_51_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_51_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_53_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_53_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_54_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_54_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_80_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_80_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.6.1.mum
     servicing\packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.6.1.mum
     servicing\packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.6.1.mum
     servicing\packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.6.1.mum
     servicing\packages\Package_for_KB3003743_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB3003743_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
    The SFC/CBS errors all seem to point back to the above ones.
    I'll post a fix when I can, but it may not be until the weekend sometime.
      My Computer


  4. Posts : 52
    Windows 7 64bit
    Thread Starter
       #4

    I appreciate your help!
      My Computer


  5. Posts : 52
    Windows 7 64bit
    Thread Starter
       #5

    Hi,
    Just checking if you had a chance to look at this or if someone else could see what I need.

    Thanks
      My Computer


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

    Sorry about that - busy weekend
    I'll post a fix protocol later today
      My Computer


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

    I've uploaded afile - ar6aa.zip - to my OneDrive at Noel's OneDrive

    Please downloadand save it.

    Right-click onthe downloaded file, and select Extract all…

    Extract to thedefault location - which will create a new folder ar6aa 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 thefolder

    C:\Windows\Temp\CheckSur\Servicing\Packages

    Andthe content of the manifestsfolder (.manifest files) into this folder:

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

    Nowrun the CheckSUR tool again (it may take a while)

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


  8. Posts : 52
    Windows 7 64bit
    Thread Starter
       #8

    Thanks will try this tonight.
      My Computer


  9. Posts : 52
    Windows 7 64bit
    Thread Starter
       #9

    I cleared my temp folder during the weekend so I had to run the tool one time first to get those folders created, I hope that is ok. I'll let you know what happens.
      My Computer


  10. Posts : 52
    Windows 7 64bit
    Thread Starter
       #10

    Here is the new logs...

    https://dl.dropboxusercontent.com/u/...S_11172014.zip

    I wasnt able to attach it.
      My Computer


 
Page 1 of 2 12 LastLast

  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 06:01.
Find Us