Solved Error: TRUST_E_NOSIGNATURE(0x800b0100)

[KodeShark]

I have the error when i try to install service pack 1.
I already tried with System Update Readiness Tools and it doesn't work.
I unchecked antivirus and firewall too.

I have attached the checksur.log

 

[Jacee]

See the answer that worked here how do I fix CBS Catalog Corrupt 0x800B0100 error - Microsoft Community

 

[KodeShark]

After following those steps I had to recheck updates, then redownload the updates. Seemed like it was going to work but then I got the same error with the same log. Currently checking to see if I may have missed a package or something.

Thanks for the quick reply, though!

 

[NoelDP]

Every fix for 800b0100 errors has to be crafted individually - there is no one-size-fits-all solution.

This one will take a little time to sort, but shouldn't be too difficult.
The problem files here - for reference and easy access - are

Unavailable repair files:
 winsxs\manifests\wow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.22084_none_4f8f581815246a4c.manifest
 winsxs\manifests\amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.22084_none_453aadc5e0c3a851.manifest
 winsxs\manifests\amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.17926_none_44f41adac7735d74.manifest
 winsxs\manifests\wow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.17926_none_4f48c52cfbd41f6f.manifest
 winsxs\manifests\amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7600.17095_none_42c0e26cca86d4bc.manifest
 winsxs\manifests\wow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7600.17095_none_4d158cbefee796b7.manifest
 winsxs\manifests\wow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7600.21298_none_4da22c4e18027fad.manifest
 winsxs\manifests\amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7600.21298_none_434d81fbe3a1bdb2.manifest
 servicing\packages\Package_1_for_KB2748349~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_1_for_KB2748349~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_2_for_KB2743555~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_2_for_KB2743555~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_2_for_KB2748349~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_2_for_KB2748349~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_5_for_KB2743555~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_5_for_KB2743555~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2743555_RTM~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2743555_RTM~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2743555_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2743555_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2743555~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2743555~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2748349_RTM~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2748349_RTM~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2748349~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2748349~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_1_for_KB2748349~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_1_for_KB2748349~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_2_for_KB2743555~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_2_for_KB2743555~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_2_for_KB2748349~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_2_for_KB2748349~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_5_for_KB2743555~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_5_for_KB2743555~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2743555_RTM~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2743555_RTM~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2743555_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2743555_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2743555~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2743555~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2748349_RTM~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2748349_RTM~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2748349~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2748349~31bf3856ad364e35~amd64~~6.1.1.1.cat

 

[NoelDP]

I've uploaded a file - kdsaa.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
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.

 

[KodeShark]

I'm not really sure how I broke it. I may have reconfigured something when optimizing it for SSD (for the first time so I was bound to break something). It is working now and I really appreciate it NoelDP. Thank you!

 

[NoelDP]

Please post the CheckSUR log so we can check it's OK now.