Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Code 800b0100: Windows Encountered an unkown error

12 Nov 2014   #1
Ar6entino

Windows 7 64bit
 
 
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 System SpecsSystem Spec
.
12 Nov 2014   #2
Ar6entino

Windows 7 64bit
 
 

i also tried to install updates manually but it fails
My System SpecsSystem Spec
13 Nov 2014   #3
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

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 System SpecsSystem Spec
.

13 Nov 2014   #4
Ar6entino

Windows 7 64bit
 
 

I appreciate your help!
My System SpecsSystem Spec
16 Nov 2014   #5
Ar6entino

Windows 7 64bit
 
 

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

Thanks
My System SpecsSystem Spec
17 Nov 2014   #6
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

Sorry about that - busy weekend
I'll post a fix protocol later today
My System SpecsSystem Spec
17 Nov 2014   #7
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

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 System SpecsSystem Spec
17 Nov 2014   #8
Ar6entino

Windows 7 64bit
 
 

Thanks will try this tonight.
My System SpecsSystem Spec
17 Nov 2014   #9
Ar6entino

Windows 7 64bit
 
 

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 System SpecsSystem Spec
17 Nov 2014   #10
Ar6entino

Windows 7 64bit
 
 

Here is the new logs...

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

I wasnt able to attach it.
My System SpecsSystem Spec
Reply

 Code 800b0100: Windows Encountered an unkown error




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Windows 7: Code 800B0100 : Windows Update encountered an unknown error
Windows 7 SP1 I've done Windows suggested things and DSIM SURT and SFC Scan. I had trouble Zipping the CheckSUR, so here it is. Can you help as I can't do any updates? Thanks. ================================= Checking System Update Readiness. Binary Version 6.1.7601.18489 2014-12-19...
Windows Updates & Activation
Windows Update encountered an unknown error. Code 800B0100
Hello. This is my first posting so here goes! I'm fixing a computer for a friend. I can't get SP1 to complete installation. I followed the instructions for creating the CBS log file and have attached it here. I took a look inside the checkSUR log file and I can see the following: (f) ...
Windows Updates & Activation
Fix Code 800B0100: Windows Encountered an unkown error on DELL M6400
I am having issues installing Windows update - getting "Code 800B0100: Windows Encountered an unkown error". I have ran the Download System Update Readiness Tool for Windows 7 but it doesnt help. I also ran the "sfc /scannow" and got "Windows Resource Protection did not find any integrity...
Windows Updates & Activation
Windows error: Code 800B0100
Hi, I hope someone can help me with this I get the error code 800B0100 when I try to install the Windows Updates KB2676562 KB2847311 KB2973201 KB2993651 KB2853952 I already did run the System Update Readiness Tool the SFC Scan and the chkdsk C: /F disk check, also this is a new Windows...
Windows Updates & Activation
Code 800B0100 : Windows Update encountered an unknown error.
I have ran the fix-it, downloaded SP1 straight from the microsoft website (still wouldn't install), etc. etc. No avail. I'm running Windows 7 Ultimate 64-bit i also get Code 8024200D I'm sure if i uploaded the correct CheckSUR, but it was the only one that showed up when i searched for...
Windows Updates & Activation
Windows Update error code 800B0100
Suddenly yesterday Windows update starting returning an error each time I tried to install updates. The updates are being downloaded ok but when I select install I get the following: Code 800B0100 Windows update encountered an unknown error I have researched this but the information I found...
Windows Updates & Activation


Our Sites

Site Links

About Us

Find 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 08:14.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App