Win7 SP1 fail Trust-E-Nosignature(0X800b0100)


  1. Posts : 17
    Windows 7 32-bit
       #1

    Win7 SP1 fail Trust-E-Nosignature(0X800b0100)


    Hi,
    I have a Windows 7 laptop that can't update to SP1, it gives me the Trust-E-Nosignature(0X800b0100) error. Can anyone help me resolve this? I've run the System Readiness Tool, my CheckSUR.log is attached.
      My Computer


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

    You have a fair number of errors there
    Code:
    Unavailable repair files:
     winsxs\manifests\x86_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7600.16912_none_156666936aaf85a2.manifest
     winsxs\manifests\x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.21855_en-us_85dc1d26f945c1de.manifest
     winsxs\manifests\x86_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7600.21085_none_15a72b0484036b23.manifest
     winsxs\manifests\x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7600.21085_en-us_83d52698fc37dfe0.manifest
     winsxs\manifests\x86_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.17720_none_173ff31967dfdad1.manifest
     winsxs\manifests\x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7600.16912_en-us_83946227e2e3fa5f.manifest
     winsxs\manifests\x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.17720_en-us_856deeade0144f8e.manifest
     winsxs\manifests\x86_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.21855_none_17ae219281114d21.manifest
     servicing\packages\Package_145_for_KB2633952~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_145_for_KB2633952~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_147_for_KB2633952~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_147_for_KB2633952~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_37_for_KB2633952~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_37_for_KB2633952~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_38_for_KB2633952~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_38_for_KB2633952~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_for_KB2633952_RTM~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_for_KB2633952_RTM~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_for_KB2633952_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_for_KB2633952_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_for_KB2633952~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_for_KB2633952~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_145_for_KB2633952~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_145_for_KB2633952~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_147_for_KB2633952~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_147_for_KB2633952~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_37_for_KB2633952~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_37_for_KB2633952~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_38_for_KB2633952~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_38_for_KB2633952~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_for_KB2633952_RTM~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_for_KB2633952_RTM~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_for_KB2633952_SP1~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_for_KB2633952_SP1~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_for_KB2633952~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_for_KB2633952~31bf3856ad364e35~x86~~6.1.1.0.cat
    I'll post a fix for them later.
      My Computer


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

    I've uploaded a file - h78aa.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 h78aa 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.

    Also, then run SFC /SCANNOW, and post the CBS.log file (you'll have to copy it to the desktop first, as it can't be manipulated directly).
      My Computer


  4. Posts : 17
    Windows 7 32-bit
    Thread Starter
       #4

    Thank you NoelDP, I wish I had your skills. CheckSUR files are attached, CBS was too big to attach alone so I split it as CBS1 and CBS2. Awaiting further instruction.
      My Computer


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

    Good - CheckSUR managed to replace all the required files this time :)
    ...and the CBS/SFC scan is clear, now

    With any luck, SP1 should now install!
      My Computer


  6. Posts : 17
    Windows 7 32-bit
    Thread Starter
       #6

    Sure enough, it did! Thanks again NoelDB! :)
      My Computer


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

    Great! - you're welcome, and good luck!
      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 12:39.
Find Us