Windows 7 Ultimate x64: SP1 Error TRUST_E_NOSIGNATURE (0x800b100)


  1. Posts : 2
    Windows 7 Ulitimate x64
       #1

    Windows 7 Ultimate x64: SP1 Error TRUST_E_NOSIGNATURE (0x800b100)


    I've been trying to install the Windows Service Pack 1 for few days now and it keeps failing. I followed the support page and tried to resolve it but I was unable to. I've installed "System Update Readiness" tool, ran Windows Fixit Doctor and even tried to manually install in a clean boot. Anyone know what's wrong? Attached is my CheckSUR.log Thanks!
      My Computer


  2. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #2

    Here's the error list from the CheckSUR log -
    Code:
    Unavailable repair files:
     winsxs\manifests\amd64_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7600.16748_none_07ebd26bfd1a9d00.manifest
     winsxs\manifests\amd64_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7600.20888_none_084a2f871658ac8e.manifest
     servicing\packages\Package_1_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
     servicing\packages\Package_1_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
     servicing\packages\Package_2_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
     servicing\packages\Package_2_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
     servicing\packages\Package_3_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
     servicing\packages\Package_3_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
     servicing\packages\Package_4_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
     servicing\packages\Package_4_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
     servicing\packages\Package_5_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
     servicing\packages\Package_5_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
     servicing\packages\Package_6_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
     servicing\packages\Package_6_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
     servicing\packages\Package_7_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
     servicing\packages\Package_7_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
     servicing\packages\Package_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.mum
     servicing\packages\Package_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.mum
     servicing\packages\Package_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
     servicing\packages\Package_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
     servicing\packages\Package_1_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
     servicing\packages\Package_1_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
     servicing\packages\Package_2_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
     servicing\packages\Package_2_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
     servicing\packages\Package_3_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
     servicing\packages\Package_3_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
     servicing\packages\Package_4_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
     servicing\packages\Package_4_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
     servicing\packages\Package_5_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
     servicing\packages\Package_5_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
     servicing\packages\Package_6_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
     servicing\packages\Package_6_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
     servicing\packages\Package_7_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
     servicing\packages\Package_7_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
     servicing\packages\Package_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.cat
     servicing\packages\Package_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.cat
     servicing\packages\Package_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
     servicing\packages\Package_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
    I'll post a fix protocol later.
      My Computer


  3. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #3

    I've uploaded a file - ffpaa.zip - to my OneDrive at Noel's OneDrive
    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 ffpaa 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.
      My Computer


  4. Posts : 2
    Windows 7 Ulitimate x64
    Thread Starter
       #4

    Sorry about the late reply I had school related stuff

    Anyhow the fix worked absolutely flawlessly! I updated to SP1 and installed a ton of other critical updates I've been missing out on. You're a lifesaver dude, thanks so much!

    Even though the problem is resolved and everything seems to be working properly I'll still attach the CheckSUR.log and CheckSUR.persist.log as you requested.

    Have a good one!
      My Computer


  5. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #5

    That looks good - please now do another SFC /scannow and post the new CBS.log file.

    If it comes back 'nothing found', then try a Check for Updates, and attempt to install ONLY the oldest update found. post back with results and error messages (if any!)
      My Computer


 

  Related Discussions
Our Sites
Site Links
About 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 10:15.
Find Us