none
TRUST_E_NOSIGNATURE (0x800b0100) when installing W7 SP1 or KB2758857

    General discussion

  • Hello,

    I can't install W7 64 SP1 or KB2758857 on my computer because of the too well known TRUST_E_NOSIGNATURE error.

    I have read all the other threads talking about it, specially the one from Himanshu. Thanks for his very good explanation, but it seems I'm not in that case, because the solution proposed by Himanshu doesn't work for me.

    I ran SFC  /SCANNOW that changed some files, but without sucess for SP1.

    I tried CheckSUR tool, without sucess.

    When I look at CBS.log file, the first error I see is :

    2013-01-29 01:21:44, Info                  CBS    WinVerifyTrust failed [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
    2013-01-29 01:21:44, Error                 CBS    Failed to verify if catalog file Windows\Servicing\Packages\Package_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat is valid. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]

    I checked securty configuration for this file... Everything is OK.

    Can you please help me ?

    Thanks

    Olivier Franceschi

    Wednesday, January 30, 2013 11:27 AM

All replies

  • Hi Olivier,


    First, please refer to this article and see if the issue can be resolved: Windows Update Error 800B0100

     

    If the issue persists, please try the following suggestions to check the result:

     

    Disable Windows Firewall and other security software and then run Windows Update.

     

    If the issue persists, access Clean Boot and manually download the failed update via Download Center to install the updates.

     

    Also, here is an article for your reference:


    Advanced guidelines for diagnosing and fixing servicing corruption

    http://technet.microsoft.com/en-us/library/ee619779(WS.10).aspx

     

    Hope this helps.


    Vincent Wang
    TechNet Community Support

    Thursday, January 31, 2013 8:13 AM
    Moderator
  • Hello,

    I used the System Update Readiness Tool (downloaded via Download center) that reported my some errors in CheckSUR.log : 

    Summary:
    Seconds executed: 1238
     Found 46 errors
      CSI Manifest All Zeros Total count: 1
      CSI Payload File Missing Total count: 19
      CBS MUM Corrupt Total count: 13
      CBS Catalog Corrupt Total count: 13

    Unavailable repair files:
    winsxs\manifests\amd64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.22125_none_c6cb7a5c0713b8fa.manifest
    servicing\packages\Package_183_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_183_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_185_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_185_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_204_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_204_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_220_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_220_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_222_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_222_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_37_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_37_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_39_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_39_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_58_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_58_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_74_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_74_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_76_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_76_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2758857_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2758857_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2758857_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2758857_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_183_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_183_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_185_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_185_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_204_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_204_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_220_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_220_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_222_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_222_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_37_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_37_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_39_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_39_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_58_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_58_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_74_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_74_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_76_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_76_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2758857_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2758857_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2758857_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2758857_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.cat

    All those files are on my disk.

    So I tried to use the Automatic Troubleshooter, as suggested, that said to me that everything was corrected.

    Than I desactivated my firewall (Comodo), my anti-virus (Avast), and tried to install again  KB2758857 (downloaded via Download center). It failed, with this error in CBS.log, as usual !

    2013-01-31 20:31:30, Info                  CBS    Failed to parse the manifest from the buffer. [HRESULT = 0x800f0900 - CBS_E_XML_PARSER_FAILURE]
    2013-01-31 20:31:30, Error                 CBS    Failed to parse package manifest: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2\Windows\Servicing\Packages\Package_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0.mum [HRESULT = 0x800f0900 - CBS_E_XML_PARSER_FAILURE]

    It finally tried Clean boot also, without success...

    I have now to read ee619779. I'll let you know.

    Thanks

    Olivier Franceschi

    Thursday, January 31, 2013 9:02 PM
  • Well, I copied all the above files in the windows servicing temp directory, as described in your suggested article ee619779. I could get those files from another computer in W7 x64.

    I applied the System Update Readiness Tool once more, and..... IT WORKED !!!!

    I could next apply KB2758857 and SP1 !!!

    I'm so glad you helped to solve this. Thanks a lot !

    Friday, February 01, 2013 10:16 AM
  • Hi Olivier ,


    Glad to hear this issue has been solved after using the  System Update Readiness Tool twice.


    Regards,


    Vincent Wang
    TechNet Community Support

    Monday, February 04, 2013 1:41 AM
    Moderator
  • Hi Vincent,

    I'm having issues with Windows Update.

    Ran the System Update Readiness Tool, and here's the log:

    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.21645
    Package Version 20.0
    2013-08-28 08:50

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs
    (f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_1_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum        Line 1:
    (f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_1_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat        
    (f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_3_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum        Line 1:
    (f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_3_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat        
    (f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB2685811_RTM~31bf3856ad364e35~amd64~~6.1.1.11.cat        
    (f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum        Line 1:
    (f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.cat        

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store

    Summary:
    Seconds executed: 678
     Found 7 errors
      CBS MUM Corrupt Total count: 3
      CBS Catalog Corrupt Total count: 4

    Unavailable repair files:
        servicing\packages\Package_1_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum
        servicing\packages\Package_1_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum
        servicing\packages\Package_3_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum
        servicing\packages\Package_3_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum
        servicing\packages\Package_for_KB2685811_RTM~31bf3856ad364e35~amd64~~6.1.1.11.mum
        servicing\packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum
        servicing\packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum
        servicing\packages\Package_1_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat
        servicing\packages\Package_1_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat
        servicing\packages\Package_3_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat
        servicing\packages\Package_3_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat
        servicing\packages\Package_for_KB2685811_RTM~31bf3856ad364e35~amd64~~6.1.1.11.cat
        servicing\packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.cat
        servicing\packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.cat

    Any idea how to fix this?

    Thanks.

    Wednesday, August 28, 2013 8:12 AM