Unable to update to Windows 7 SP1. TRUST_E_NOSIGNATURE (0x800b0100)

Hi All,

I just joined.

After trying almost every method listed on the Internet, I give up trying to install Windows 7 SP1.

Here's what I've done so far:

-I've run sfc /scannow and it came back OK.
-Turned off all AV, Malware, Firewalls.
-Updated every driver I could.
-Applied every hotfix I could
-Downloaded and tried to run the SP1 from ISO image. Still nothing.
-Ran Lenovo Toolbox to updated whatever else I could. But I'll still get the "Trust error".

I've never had such an issue before updating. Really frustrating.

I ran the readiness tool and attached the persist log in the C:Windows\Logs\CBS directory.

Any help is appreciated. And if I need to add any additional information, please let me know and I will do so.

Thanks in advance.

The CheckSUR log reveals the following problems...

Code:

Unavailable repair files:
 winsxs\manifests\msil_system_b77a5c561934e089_6.1.7600.20960_none_9847e45631eced47.manifest
 winsxs\manifests\msil_system.resources_b77a5c561934e089_6.1.7600.20960_en-us_50b433a8b08e3fda.manifest
 winsxs\manifests\amd64_netfx-system_b03f5f7f11d50a3a_6.1.7600.20960_none_a88b599c1721191c.manifest
 winsxs\manifests\amd64_netfx-system_b03f5f7f11d50a3a_6.1.7600.16809_none_bf523197fd8007b5.manifest
 winsxs\manifests\msil_system.resources_b77a5c561934e089_6.1.7600.16809_en-us_677b0ba496ed2e73.manifest
 winsxs\manifests\msil_system_b77a5c561934e089_6.1.7600.16809_none_af0ebc52184bdbe0.manifest
 servicing\packages\Package_1_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_4_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_4_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2539634_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2539634_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_1_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_2_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_2_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_4_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_4_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2539634_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2539634_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.cat

SFC found nothing of note.

I'll post a fix protocol for the CheckSUR failures later.

It's not that the files are missing as such - they are present, but all appear to be empty
This usually occurs where an update install gets interrupted suddenly for some reason (at least that's my guess)- possibly a power outage or a crash at just the wrong time.

back later.

I've uploaded a file - gk7aa.zip - to my SkyDrive at Noel's SkyDrive
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 gk7aa 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 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.

CheckSUR is clear now.
Odd that you should be getting the same error still, but it may be that a dll file has become unregistered somehow...

Open an Elevated Command Prompt, and run the following commands...

Code:

 
net stop wuauserv 
regsvr32 wuapi.dll /s 
regsvr32 wups.dll /s 
regsvr32 wuaueng.dll /s 
regsvr32 wucltui.dll /s 
regsvr32 wuweb.dll /s 
regsvr32 msxml.dll /s 
regsvr32 msxml2.dll /s 
regsvr32 msxml3.dll /s 
regsvr32 urlmon.dll /s 
regsvr32 softpub.dll /s 
regsvr32 initpki.dll /s 
regsvr32 mssip32.dll /s 
regsvr32 wintrust.dll /s 
regsvr32 dssenh.dll /s 
regsvr32 rsaenh.dll /s 
regsvr32 gpkcsp.dll /s 
regsvr32 sccbase.dll /s 
regsvr32 slbcsp.dll /s 
regsvr32 cryptdlg.dll /s 
regsvr32 jscript.dll /s
net start wuauserv 

.

then reboot, and try the update again - from the standalone installer, would probably be best.

From the sound of it, you may have fallen into the trap of attempting to run the installer from a virtual CD/DVD?? If so, that may have been what stalled it the last time - Windows doesn't much like that type of thing for major updates like Service Packs

If you actually created a physical disk, then it's possible that either the download was corrupt, or the burn failed.


Whatever, You have got a nice new updated OS to play with - have fun!