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: Another TRUST_E NOSIGNATURE (0x8006100) problem with KB976932

29 Nov 2012   #1

Windows 7 64 bit Home Premium
 
 
Another TRUST_E NOSIGNATURE (0x8006100) problem with KB976932

Have tried unsuccessfully to install SP1 for Windows 7 x64 system on my PC on numerous occasions. Decided to try and solve problem once and for all and found your forum which appears to have offered helpful advice to other people with similar difficulties.

Following advice in a previous thread, I have downloaded and installed System Update Readiness Tool (KB947821) and I have run a SFC Scan - I hope that I have attached the relevant CBS logs.

I then tried yet again to install KB976932 and the installation stopped at 33% and showed the error code TRUST_E NOSIGNATURE(0x8006010).

I'd be grateful for any help in solving this problem. If further information is needed, please let me know.


Rob

My System SpecsSystem Spec
.

29 Nov 2012   #2

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

The CBS.log shows nothing out of the ordinary - but the CheckSUR shows the following......
Code:
 winsxs\manifests\amd64_wpf-presentationframework_31bf3856ad364e35_6.1.7600.20658_none_cb285ee688aa009a.manifest
 winsxs\manifests\x86_wpf-presentationframework_31bf3856ad364e35_6.1.7600.20658_none_6f09c362d04c8f64.manifest
 winsxs\manifests\amd64_wpf-presentationhostdll_31bf3856ad364e35_6.1.7600.16542_none_cc28a17e399280f3.manifest
 winsxs\manifests\x86_wpf-presentationhostdll_31bf3856ad364e35_6.1.7600.16542_none_700a05fa81350fbd.manifest
 winsxs\manifests\amd64_wpf-presentationhostdll_31bf3856ad364e35_6.1.7600.20658_none_ccad701952b2d4b8.manifest
 winsxs\manifests\x86_wpf-presentationhostdll_31bf3856ad364e35_6.1.7600.20658_none_708ed4959a556382.manifest
 winsxs\manifests\amd64_wpf-windowsbase_31bf3856ad364e35_6.1.7600.20658_none_b40f0fc47a79b870.manifest
 winsxs\manifests\x86_wpf-windowsbase_31bf3856ad364e35_6.1.7600.20658_none_57f07440c21c473a.manifest
 winsxs\manifests\amd64_wpf-presentationhostproxy_31bf3856ad364e35_6.1.7600.16542_none_86a84af193626297.manifest
 winsxs\manifests\x86_wpf-presentationhostproxy_31bf3856ad364e35_6.1.7600.16542_none_2a89af6ddb04f161.manifest
 winsxs\manifests\amd64_wpf-presentationhostexe_31bf3856ad364e35_6.1.7600.16542_none_cc11679639b12365.manifest
 winsxs\manifests\x86_wpf-presentationhostexe_31bf3856ad364e35_6.1.7600.16542_none_6ff2cc128153b22f.manifest
 winsxs\manifests\amd64_wpf-presentationhostexe_31bf3856ad364e35_6.1.7600.20658_none_cc96363152d1772a.manifest
 winsxs\manifests\x86_wpf-presentationhostexe_31bf3856ad364e35_6.1.7600.20658_none_70779aad9a7405f4.manifest
 winsxs\manifests\x86_presentationcore_31bf3856ad364e35_6.1.7600.20658_none_acb4799c0a4a7137.manifest
 winsxs\manifests\amd64_presentationcore_31bf3856ad364e35_6.1.7600.20658_none_08d3151fc2a7e26d.manifest
 winsxs\manifests\amd64_wpf-presentationhostproxy_31bf3856ad364e35_6.1.7600.20658_none_872d198cac82b65c.manifest
 winsxs\manifests\x86_wpf-presentationhostproxy_31bf3856ad364e35_6.1.7600.20658_none_2b0e7e08f4254526.manifest
 winsxs\manifests\amd64_wpf-windowsbase_31bf3856ad364e35_6.1.7600.16542_none_b38a4129615964ab.manifest
 winsxs\manifests\x86_wpf-windowsbase_31bf3856ad364e35_6.1.7600.16542_none_576ba5a5a8fbf375.manifest
 winsxs\manifests\amd64_wpf-presentationframework_31bf3856ad364e35_6.1.7600.16542_none_caa3904b6f89acd5.manifest
 winsxs\manifests\x86_wpf-presentationframework_31bf3856ad364e35_6.1.7600.16542_none_6e84f4c7b72c3b9f.manifest
 servicing\packages\Package_1_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB979900_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB979900_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_1_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB979900_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB979900_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.cat
It shouldn't be too difficault to craft a repair protocol - back soon
(posting now so that Tom doesn't get his oar in as well )
My System SpecsSystem Spec
29 Nov 2012   #3

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

Back again

I've uploaded a file - rob6491.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 rob6491 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.
My System SpecsSystem Spec
.


29 Nov 2012   #4

Microsoft Community Contributor Award Recipient

Windows 8.1 Pro x64
 
 

Quote   Quote: Originally Posted by NoelDP View Post
(posting now so that Tom doesn't get his oar in as well )
I wouldn't dream of such a thing!
My System SpecsSystem Spec
30 Nov 2012   #5

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

..just that there's no point in both of us working on the same post
My System SpecsSystem Spec
30 Nov 2012   #6

Windows 7 64 bit Home Premium
 
 

I'm grateful for Noel's prompt response and for Tom's interest.

I'll download Noel's zip file, copy the relevant files, run the CheckSUR again and post the results.

Many thanks for help so far.

Rgds.


Rob
My System SpecsSystem Spec
30 Nov 2012   #7

Windows 7 64 bit Home Premium
 
 

Noel,

I've downloaded the zip file, unzipped it and have tried to copy the contents of the package and manifest files to the stipulated locations. When I attempted to check on the file contents at these locations, the folders are shown as empty. When trying to copy the files to the packages location, an error message appear indicating something along the lines that I did not have permission to access the folder. I pressed the `Continue' button and attempted the copy the files to this folder.

Are the files present, but hidden? Should I run the CheckSUR tool yet?

Rgds.


Rob
My System SpecsSystem Spec
30 Nov 2012   #8

Windows 7 64 bit Home Premium
 
 

Noel,

Apologies for delay in responding. Just been to a neighbour's funeral.

Copy of Command Prompt Screen attached.

Rgds.


Rob


Attached Files
File Type: zip ICACLS #1.zip (222.0 KB, 2 views)
My System SpecsSystem Spec
30 Nov 2012   #9

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

(sorry about your neighbour!)

That looks normal enough to me?
Try running the CheckSUR again anyhow - we'll see what happens
My System SpecsSystem Spec
30 Nov 2012   #10

Windows 7 64 bit Home Premium
 
 

Noel,

Just got back home from wake.

Have run CheckSUR Tool without any apparent problems.

Copies of CheckSUR.log and CheckSUR.persist.log attached.

Rgds.


Rob


Attached Files
File Type: zip CheckSUR.persist.zip (9.4 KB, 3 views)
My System SpecsSystem Spec
Reply

 Another TRUST_E NOSIGNATURE (0x8006100) problem with KB976932





Thread Tools



Similar help and support threads for2: Another TRUST_E NOSIGNATURE (0x8006100) problem with KB976932
Thread Forum
Is the kb976932 update really that important? Windows Updates & Activation
Win 7 SP1 update (KB976932) won't install Error 0x800f0826 Windows Updates & Activation
Update error 800B0100 for KB976932 and couple more Windows Updates & Activation
Unable to download Windows 7 SP1 (KB976932) Windows Updates & Activation
Can't install Win7 SP1 for x64 (KB976932) Windows Updates & Activation
Win7 x64 SP1 (KB976932) Update Code 80010108 Windows Updates & Activation
Uninstall Service Pack KB976932 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 11:57 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