Win7 Ultimate x64 - SP1 install error: TRUST_E_NOSIGNATURE(0x800b0100)

I am having a problem installing SP1 onto my Windows 7 Ultimate x64 machine, and I've seen on this forum that I am not the only one. I've tried installing SP1 via Windows Update and manually by downloading and running the SP1 ISO. I keep receiving the error:

"Error on SP1 installation : TRUST_E_NOSIGNATURE(0x800b0100)"

I'm attaching my System Update Readiness Tool log, hoping that I can request some assistance in finding a resolution. Reading the attached log, it looks like a foreign language to me. It appears some files are either missing, corrupt, or un-repairable. Thanks in advance, my fingers are crossed.


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 16.0
2012-11-02 16:32

Checking Windows Servicing Packages

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

Checking Package Watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~nl-NL~0.0.0.0 WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e5~amd64~~7.6.7600.256 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~sr-LATN-CS~0.0.0.0 WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.760.256 Package registry presence failed, possibly an orphaned package on package watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Missing Deployment Key 0x00000000 b92c50bc699..28fa4b13115_31bf3856ad364e35_6.1.7601.21714_d22bb95d9fcde8a8 HKLM\Components\CanonicalData\Deployments
(f) CSI Missing Deployment Key 0x00000000 cfa99af7e45..b1795485a7d_31bf3856ad364e35_6.1.7601.17605_49373aded6529c66 HKLM\Components\CanonicalData\Deployments
(f) CSI Missing Deployment Key 0x00000000 ae8f251b6ae..d9c148dfd8a_31bf3856ad364e35_6.1.7600.16808_96847accbd9de2df HKLM\Components\CanonicalData\Deployments

Summary:
Seconds executed: 540
Found 7 errors
CSI Missing Deployment Key Total count: 3
CBS MUM Corrupt Total count: 1
CBS Catalog Corrupt Total count: 1
CBS Watchlist Package Missing Total count: 2

Unavailable repair files:
servicing\packages\Package_2_for_KB2655992~31bf3856ad364e35~amd64~~6.1.1.3.mum
servicing\packages\Package_2_for_KB2655992~31bf3856ad364e35~amd64~~6.1.1.3.mum
servicing\packages\Package_2_for_KB2655992~31bf3856ad364e35~amd64~~6.1.1.3.cat
servicing\packages\Package_2_for_KB2655992~31bf3856ad364e35~amd64~~6.1.1.3.cat

Hello DruTheFru and welcome to the forums

Windows Update Package Replacement

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Please download the attached file, Packs.zip and save this to your Desktop.
2. Right-click on the file and select Extract All...
3. Tick the box labelled Show extracted files when complete then click Extract
4. A window will open showing two folders, Manifests and Packages
5. Open the Manifests folder and copy the files into the following folder (if there are any files)
   
   C:\Windows\Temp\CheckSur\Winsxs\Manifests
   
   
6. Open the Packages folder and copy the files into the following folder (if there are any files)
   
   C:\Windows\Temp\CheckSur\Servicing\Packages
   
   
7. Run the System Update Readiness Tool (SURT) again
8. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:
   
   C:\Windows\Logs\CBS\CheckSUR.persist.log

You will probably be shown the error code 0x8024200D after performing this fix, if so, please download and install the update from this link. It must be downloaded using Internet Explorer.

http://www.microsoft.com/en-gb/download/details.aspxid=30238

Tom

Thanks for the reply and assistance. I'll move forward with this in the next day or two when life gives me a few minutes to spare, and I'll come back with the results. Thanks again!

Haha, no worries, just post at a time that's convenient for you

Tom

Here's my new result:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 16.0
2012-11-08 16:46

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_2_for_KB2655992~31bf3856ad364e35~amd64~~6.1.1.3.mum Line 1:
(fix) CBS MUM Corrupt CBS File Replaced Package_2_for_KB2655992~31bf3856ad364e35~amd64~~6.1.1.3.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix) CBS Paired File CBS File also Replaced Package_2_for_KB2655992~31bf3856ad364e35~amd64~~6.1.1.3.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.

Checking Package Watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~nl-NL~0.0.0.0 WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e5~amd64~~7.6.7600.256 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~sr-LATN-CS~0.0.0.0 WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.760.256 Package registry presence failed, possibly an orphaned package on package watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Missing Deployment Key 0x00000000 b92c50bc699..28fa4b13115_31bf3856ad364e35_6.1.7601.21714_d22bb95d9fcde8a8 HKLM\Components\CanonicalData\Deployments
(f) CSI Missing Deployment Key 0x00000000 cfa99af7e45..b1795485a7d_31bf3856ad364e35_6.1.7601.17605_49373aded6529c66 HKLM\Components\CanonicalData\Deployments
(f) CSI Missing Deployment Key 0x00000000 ae8f251b6ae..d9c148dfd8a_31bf3856ad364e35_6.1.7600.16808_96847accbd9de2df HKLM\Components\CanonicalData\Deployments

Summary:
Seconds executed: 839
Found 6 errors
Fixed 1 errors
CSI Missing Deployment Key Total count: 3
CBS MUM Corrupt Total count: 1
Fixed: CBS MUM Corrupt. Total count: 1
CBS Watchlist Package Missing Total count: 2
Fixed: CBS Paired File. Total count: 1

OK, so I manually succeeded in installing KB2655992.

Then ran the SURT again.

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 16.0
2012-11-08 19:44

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~nl-NL~0.0.0.0 WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e5~amd64~~7.6.7600.256 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~sr-LATN-CS~0.0.0.0 WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.760.256 Package registry presence failed, possibly an orphaned package on package watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Missing Deployment Key 0x00000000 b92c50bc699..28fa4b13115_31bf3856ad364e35_6.1.7601.21714_d22bb95d9fcde8a8 HKLM\Components\CanonicalData\Deployments
(f) CSI Missing Deployment Key 0x00000000 cfa99af7e45..b1795485a7d_31bf3856ad364e35_6.1.7601.17605_49373aded6529c66 HKLM\Components\CanonicalData\Deployments
(f) CSI Missing Deployment Key 0x00000000 ae8f251b6ae..d9c148dfd8a_31bf3856ad364e35_6.1.7600.16808_96847accbd9de2df HKLM\Components\CanonicalData\Deployments

Summary:
Seconds executed: 737
Found 5 errors
CSI Missing Deployment Key Total count: 3
CBS Watchlist Package Missing Total count: 2

Now upon trying to install SP1, I receive a different error:

The referenced assembly could not be found
Error: ERROR_SXS_ASSEMBLY_MISSING(0x80073701)

I look in the CBS.log file and search for ERROR_SXS_ASSEMBLY_MISSING and see a reference to "Package_2_for_KB2536276". I cannot seem to uninstall this update via command line or the Control Panel.

It seems like I'm one step closer, but not close enough to getting this SP1 update to install

Hi DruTheFru,

That error is a fairly common one as well, so it shouldn't be too hard to fix. I've got to pop out now, but I should be able to post later (if not, tomorrow). Please ignore this, I just don't want to lose my research:

Tom

Hi DruTheFru,

Before we continue, I would like you to backup your registry by following this tutorial:

Backup and Restore the Whole Windows Registry or Selected Hives

Registry Modifications

1. Go to Start > Run to bring up the run box
2. In the box, type notepad.exe and press OK to open Notepad
3. Copy (Ctrl+C) all of the text in the following box and paste (Ctrl+V) it into Notepad
   
   
   Code:

   Windows Registry Editor Version 5.00
   
   [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~nl-NL~0.0.0.0]
   "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e5~amd64~~7.6.7600.256"=-
   
   [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~sr-LATN-CS~0.0.0.0]
   "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.760.256"=-

4. Go to File > Save As... and save it to your Desktop named Fix.reg. Make sure you change the Save as type to All Files (*.*)
5. Locate Fix.reg on your Desktop and double-click on it to merge it with your registry
6. Answer Yes when prompted about merging with the registry

Tom

Ok. I did the registry back up, changes, then ran the SURT again, followed by the SP1 install.

Here's my CheckSUR.log:



.
.
.
.
and then the SP1 failed:

The referenced assembly could not be found.
Error: ERROR_SXS_ASSEMBLY_MISSING(0x80073701)​

, with the CBS.log and searching within the file for the error message (ERROR_SXS_ASSEMBLY_MISSING):

.
.
.
.
.
So it's still not installing...

Thanks for still looking into it.

Hi DruTheFru,

The Watchlist Package Missing errors are easy enough to fix, but the Missing Deployment Key error is very tough to solve. I'm also running Windows 7 x64 Ultimate and I was hoping to be able to export the key directly for me (it's not something you can recreate), but since I'm running SP1, my registry is more updated than yours so it won't work, I'm afraid. I think the best step would be to do a repair install:

http://www.sevenforums.com/tutorials/3413-repair-install.html

Tom

Thanks for all of your efforts and help you've provided. We almost made it.

I'm thinking of ditching Windows 7 for Windows 8, especially with the current upgrade offers out there (for cheap $). Do you think upgrading and installing Win8 over the Win7 installation would "fill in the blanks" and resolve the remaining issue(s)?

Hi DruTheFu (just noticed I've been spelling your username wrong for the whole time - oops!)

I will only ever upgrade to a newer OS after it's been out for a few months. When new OSs are released, a lot of software and drivers need rewriting to give Windows 8 support - this brings on a new wave of bugs in the software, so I like to give it a few months just so they can iron out the creases in their software and I'm dealing with a stable OS with stable software. If I update then I can't use some of my software, it would be really annoying, let alone counterproductive. I know people will argue with me here saying that's what the developer preview is for, but this is just how I feel based on previous experience.

Reinstalling Windows 7 will definitely fix your problem. I, personally, don't like Windows 8, the interface doesn't quite do it for me. If you want to hear what other people here think, I would recommend starting a new thread asking that question

Tom