Solved Unable to install SP1 windows 7 home premium 64bit. error 800B0100

[ultimaa]

Hello, I am having an issue getting windows 7 service pack 1 to install (windows6.1-KB976932-X64.exe).
I get error code TRUST_E_NOSIGNATURE(0x800b0100). These are troubleshooting steps i have already attempted. I had antivirus and firewall disabled during this whole process.

1.First i attempted to use the microsoft fixit tool located here Troubleshoot problems with installing updates - Windows Help
2.Ran a Sfc scannow test on command promt (no errors found)
3.Ran a diskchk on the harddrive which my windows OS was located on (no errors)
4.Ran System Update readiness tool which completed (log is attached)
5.Added Windows6.1KB947821-v34-x64.msu to my %Windir%\Temp\CheckSUR \servicing\packages\ directory. Reran System update readiness tool (same missing manifests, mum, and cat file errors in log).

So basically the next step from what I read is to do a install repair or to manually copy in the missing manifest, mum and cat files. I would prefer to do that latter but i don't have another 64bit machine to get the files from. I dont know where i would attain these files.

 

[NoelDP]

Here's the CheckSUR summary

Summary:
Seconds executed: 3009
 Found 16 errors
  CSI Manifest All Zeros Total count: 10
  CBS MUM Corrupt Total count: 3
  CBS Catalog Corrupt Total count: 3
Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7600.20789_none_366f2ebb2946b708.manifest
 winsxs\manifests\amd64_microsoft-windows-smbserver-v1_31bf3856ad364e35_6.1.7600.20789_none_3679fea7293e9b17.manifest
 winsxs\manifests\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.1.7600.20789_none_6058c38042f219f9.manifest
 winsxs\manifests\amd64_microsoft-windows-smbserver-v1_31bf3856ad364e35_6.1.7600.16664_none_36010042101544b8.manifest
 winsxs\manifests\amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.20789_none_55777e451da680d3.manifest
 winsxs\manifests\wow64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.20789_none_5fcc2897520742ce.manifest
 winsxs\manifests\amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.16664_none_54fe7fe0047d2a74.manifest
 winsxs\manifests\wow64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.16664_none_5f532a3238ddec6f.manifest
 winsxs\manifests\amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7600.16664_none_35f63056101d60a9.manifest
 winsxs\manifests\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.1.7600.16664_none_5fdfc51b29c8c39a.manifest
 servicing\packages\Package_1_for_KB2345886~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_1_for_KB2345886~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_for_KB2345886_RTM~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_for_KB2345886_RTM~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_for_KB2345886~31bf3856ad364e35~amd64~~6.1.1.2.mum
 servicing\packages\Package_for_KB2345886~31bf3856ad364e35~amd64~~6.1.1.2.mum

I'll post a fix protocol later.

 

[NoelDP]

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

 

[ultimaa]

Update

Ok i copyed in the folders to the places here are my new logs

 

[NoelDP]

Odd - it fixed the Packages, but not the Manifests?

Did you copy the files to the correct place?

 

[ultimaa]

I believe so it was where in directory you told me here is screenshot of where i put them

 

[ultimaa]

Actually on second glance i put the packages in wrong spot had an extra packages folder after trying to fix it by following this guys advice Using CheckSUR and update packages to fix corruption - The Windows Servicing Guy - Site Home - TechNet Blogs rerunning SUR will post new logs when done

 

[ultimaa]

Ok here is latest logs from last repair

 

[NoelDP]

I think that looks OK now - you appear to have uploaded the logs before the scan completed.

Try a Check for Updates, and see what happens.

 

[ultimaa]

Alright it worked perfectly, thank you so much for taking time to help me resolve this issue! Rep++

 

[NoelDP]

You're welcome - good luck!