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: Error 0x800b0100 when installing KB2727528 and/or KB2761217


20 Dec 2012   #1
Y3k

Windows 7 Professional x64
 
 
Error 0x800b0100 when installing KB2727528 and/or KB2761217

Greetings. I'm reporting error 0x800b0100 when installing updates KB2727528 and/or KB2761217. I tried to run KB947821 (The Readiness Tool) to no avail. I attached the CheckSUR.log and CheckSUR.persist.log generated by such tool. I must also point out that I'm in a Windows AD domain and I'm trying to update from an intranet WSUS server which keeps all the updates, but I don't think this is relevant because even if I try to download such updates directly from microsoft I get the same error.

Thank you in advance.




Attached Files
File Type: log CheckSUR.log (14.0 KB, 10 views)
File Type: log CheckSUR.persist.log (70.5 KB, 3 views)
My System SpecsSystem Spec
.

20 Dec 2012   #2

Microsoft Community Contributor Award Recipient

Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
 
 

Try to go back to a restore point prior to installing KB2727528 and KB2761217
So go back in time before first time trying to install them. Disable windows updates afterwards immediately! Then run The Readiness Tool again and post both log files. Also run from elevated command prompt (after going back in time): sfc/scannow
My System SpecsSystem Spec
20 Dec 2012   #3
Y3k

Windows 7 Professional x64
 
 

Quote   Quote: Originally Posted by Kaktussoft View Post
Try to go back to a restore point prior to installing KB2727528 and KB2761217
So go back in time before first time trying to install them. Disable windows updates afterwards immediately! Then run The Readiness Tool again and post both log files. Also run from elevated command prompt (after going back in time): sfc/scannow
Thank you for the kind reply. I did what you suggested and I have attached all required files. Updates are turned off as of now so that I stay in this environment until you tell me what to do =)


Attached Images
 
Attached Files
File Type: log CheckSUR.log (14.0 KB, 6 views)
File Type: log CheckSUR.persist.log (88.4 KB, 3 views)
My System SpecsSystem Spec
.


21 Dec 2012   #4

Microsoft Community Contributor Award Recipient

Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
 
 

Quote   Quote: Originally Posted by Y3k View Post
Quote   Quote: Originally Posted by Kaktussoft View Post
Try to go back to a restore point prior to installing KB2727528 and KB2761217
So go back in time before first time trying to install them. Disable windows updates afterwards immediately! Then run The Readiness Tool again and post both log files. Also run from elevated command prompt (after going back in time): sfc/scannow
Thank you for the kind reply. I did what you suggested and I have attached all required files. Updates are turned off as of now so that I stay in this environment until you tell me what to do =)
Don't know exactly what you did, but you did run the tool many times. In the checkusr.persist.log I see

2012-12-20 18:25 (time you run the tool) with some errors, but not that many. Can you go to that state, because it's the best state it was. Then make a new thread the checkusr gives errors. Of course post bothe log files as well. But empty them first before running the tool
My System SpecsSystem Spec
21 Dec 2012   #5

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

There are a large number of missing/corrupt files in teh log - I'll get a fix posted later, but here's the list for ease-of-access...
Code:
Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-synceng_31bf3856ad364e35_6.1.7600.17130_none_188e2f6957667415.manifest
 winsxs\manifests\x86_microsoft-windows-synceng_31bf3856ad364e35_6.1.7600.17130_none_bc6f93e59f0902df.manifest
 winsxs\manifests\amd64_microsoft-windows-g..validatefntcache-06_31bf3856ad364e35_6.1.7601.22118_none_a7612cac4a5ea0e2.manifest
 winsxs\manifests\amd64_microsoft-windows-g..validatefntcache-06_31bf3856ad364e35_6.1.7600.17130_none_a4d38ecd3432052f.manifest
 winsxs\manifests\amd64_microsoft-windows-font-truetype-calibri_31bf3856ad364e35_6.1.7600.17130_none_46cc128a0951a80d.manifest
 winsxs\manifests\amd64_microsoft-windows-synceng_31bf3856ad364e35_6.1.7601.17959_none_1a6818f55494c5d7.manifest
 winsxs\manifests\x86_microsoft-windows-synceng_31bf3856ad364e35_6.1.7601.17959_none_be497d719c3754a1.manifest
 winsxs\manifests\amd64_microsoft-windows-g..validatefntcache-06_31bf3856ad364e35_6.1.7600.21329_none_a57100044d3f6a3e.manifest
 winsxs\manifests\amd64_microsoft-windows-synceng_31bf3856ad364e35_6.1.7600.21330_none_1917ce1a70841106.manifest
 winsxs\manifests\x86_microsoft-windows-synceng_31bf3856ad364e35_6.1.7600.21330_none_bcf93296b8269fd0.manifest
 winsxs\manifests\amd64_microsoft-windows-font-truetype-calibri_31bf3856ad364e35_6.1.7601.22118_none_4959b0691f7e43c0.manifest
 winsxs\manifests\amd64_microsoft-windows-synceng_31bf3856ad364e35_6.1.7601.22119_none_1b1ccd926d92291f.manifest
 winsxs\manifests\x86_microsoft-windows-synceng_31bf3856ad364e35_6.1.7601.22119_none_befe320eb534b7e9.manifest
 winsxs\manifests\amd64_microsoft-windows-font-truetype-calibri_31bf3856ad364e35_6.1.7601.17959_none_48a5fc16067ff9cf.manifest
 winsxs\manifests\amd64_microsoft-windows-g..validatefntcache-06_31bf3856ad364e35_6.1.7601.17959_none_a6ad7859316056f1.manifest
 winsxs\manifests\amd64_microsoft-windows-font-truetype-calibri_31bf3856ad364e35_6.1.7600.21329_none_476983c1225f0d1c.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\Package_1_for_KB2727528~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_1_for_KB2727528~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_1_for_KB2761217~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB2761217~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_3_for_KB2727528~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_3_for_KB2727528~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_4_for_KB2761217~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_4_for_KB2761217~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_6_for_KB2761217~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_6_for_KB2761217~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_9_for_KB2761217~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_9_for_KB2761217~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2727528_RTM~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2727528_RTM~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2727528_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2727528_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2727528~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2727528~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2761217_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2761217_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2761217_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2761217_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2761217~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2761217~31bf3856ad364e35~amd64~~6.1.1.0.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
 servicing\packages\Package_1_for_KB2727528~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_1_for_KB2727528~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_1_for_KB2761217~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_1_for_KB2761217~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_3_for_KB2727528~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_3_for_KB2727528~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_4_for_KB2761217~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_4_for_KB2761217~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_6_for_KB2761217~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_6_for_KB2761217~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_9_for_KB2761217~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_9_for_KB2761217~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2727528_RTM~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2727528_RTM~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2727528_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2727528_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2727528~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2727528~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2761217_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2761217_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2761217_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2761217_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2761217~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2761217~31bf3856ad364e35~amd64~~6.1.1.0.cat
My System SpecsSystem Spec
21 Dec 2012   #6

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

Quote   Quote: Originally Posted by Kaktussoft View Post

2012-12-20 18:25 (time you run the tool) with some errors, but not that many. Can you go to that state, because it's the best state it was. Then make a new thread the checkusr gives errors. Of course post bothe log files as well. But empty them first before running the tool
Please don't do that!
we are currently in a know state - reverting the changes takes us to a new unknown state.
Please DO NOT delete the CheckSUR logs! - running CheckSUR replaces the existing .log file, and append its data to the persist file.
My System SpecsSystem Spec
21 Dec 2012   #7
Y3k

Windows 7 Professional x64
 
 

Ok, I've just checked this thread right now. As kaktu states I had run that tool many times in slightly different conditions, hoping that it could handle the problem. I haven't rolled back to the state suggested by kaktu as you said, I wait for your solution =)
My System SpecsSystem Spec
21 Dec 2012   #8

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

I think I've got them all, apart from the IE10 packages, which appear to be the wrong version!


I've uploaded a file - y3kxx.zip - to my SkyDrive at https://skydrive.live.com/#cid=936736BB8FCEB92F&id=936736BB8FCEB92F%21526
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 y3kxx 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
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.


Please also explain the history of your IE 10 install?
My System SpecsSystem Spec
21 Dec 2012   #9
Y3k

Windows 7 Professional x64
 
 

Quote   Quote: Originally Posted by NoelDP View Post
I think I've got them all, apart from the IE10 packages, which appear to be the wrong version!


I've uploaded a file - y3kxx.zip - to my SkyDrive at https://skydrive.live.com/#cid=936736BB8FCEB92F&id=936736BB8FCEB92F%21526
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 y3kxx 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
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.


Please also explain the history of your IE 10 install?
Thank you so much for taking such interest in my issue. I've done what you asked and attached the required files. Regarding IE10...I've seen a couple of days ago on MS site that IE10 was available on windows 7, so I downloaded the installer to give it a try. The installation succeeded and IE10 is working properly as you can tell from the attached picture. By the way I don't use it, I'm stick to chrome, so if it must be removed to solve the issue at hand there's no problem =)


Attached Images
 
Attached Files
File Type: log CheckSUR.log (14.7 KB, 2 views)
File Type: log CheckSUR.persist.log (103.1 KB, 0 views)
My System SpecsSystem Spec
21 Dec 2012   #10

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

I *think* I may have found the proper files - there's only one way to find out


I've uploaded a file - packages.zip - to my SkyDrive at https://skydrive.live.com/#cid=936736BB8FCEB92F&id=936736BB8FCEB92F%21526
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 packages in the same place.
Open this folder -
Copy the content of the Packages folder to the
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.


Then do a manual scan for updates and see what happens.
My System SpecsSystem Spec
Reply

 Error 0x800b0100 when installing KB2727528 and/or KB2761217




Thread Tools



Similar help and support threads for2: Error 0x800b0100 when installing KB2727528 and/or KB2761217
Thread Forum
Error: TRUST_E_NOSIGNATURE(0x800b0100) Windows Updates & Activation
Solved 0x800b0100 error Windows Updates & Activation
Solved Windows Update Error 8007065E on Update KB2761217 Windows Updates & Activation
Solved Windows 7 Updates Not installing Error TRUST_E_NOSIGNATURE(0x800b0100 Windows Updates & Activation
Windows 7 Updates Not installing Error TRUST_E_NOSIGNATURE 0x800b0100 Windows Updates & Activation
Error trust_e_nosignature 0x800b0100 when installing W7 SP1 Windows Updates & Activation
TRUST_E_NOSIGNATURE(0x800b0100) error installing SP1 for Win 7 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 12:14 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33