Hello, I know this is a common topic.

Mark7 said:

hi all,
I have a new-to me (meaning it is a refurbished job) hp dv7 4171nr. Have recently been trying to do my updates and have run into several problems surrounding sp1 and a few other of the lovely little patches that is the sustenance of my Microsoft existence. I previously had an xp pro machine and was quite happy with it but alas time to move on... i have tried everything i could find as a result of scouring the net and these forums.There seems to be a lot of issues concerning this latest fix. I have run the SUR and tried to install after and always the same results.... Anyway i am hoping to get this resolved as i am the type to actually lose sleep if my crap aint runnin right if ya know what i mean. Here is the log if anybody would care to see what is happening.... And a very big "THANK YOU" goes out to all those people that tirelessly devote their free time here to help unknown people.

Hello, and welcome to the Seven Forums!

Thanks a lot for posting your log file. That speeds things up a bit :)

WARNING! This fix was created specifically for this user! If you are not this user, do not follow these instructions!
@Mark7: Ignore the above

Download the attached .zip file. Inside it, will be two folders, Packages and Manifests.

Create these folders if they do not already exist: C:\Windows\Temp\CheckSur\Servicing\Packages\ and C:\Windows\Temp\CheckSur\winsxs\Manifests

Extract Packs.zip onto your Desktop. Please place the contents of my Desktop\Packages in C:\Windows\Temp\CheckSur\Servicing\Packages\ and my Desktop\Manifests in C:\Windows\Temp\CheckSur\winsxs\Manifests.

Note that for you there are no manifests, and so just ignore this step.

DO NOT place the .zip file in that folder, or the folders themselves. Make sure that a lot of files are in each of those Checksur folder.

Re-run the System Update Readiness Tool, and get me another copy of C:\Windows\Logs\CBS\CheckSUR.log.

Also, please retest Windows Updates (with fingers slightly crossed, no matter how much we both know that that won't help! lol.)

Thanks a lot!

Richard

Thank you all for your responses. I followed niemiro's instructions to a tee in the order that they were posted and got the same error (800B0100). Also i have another question : should i try to install SP1 separately from everything else? I have downloaded a 903MB version from Microsoft. Update reports that i have 9 important updates with 3 of them checked. The ones that are checked and will not install are: KB2393802 , KB2556532 , and KB976932.

Mark7 said:

Also i have another question : should i try to install SP1 separately from everything else?

IMHO > Yes!

Ok i did the update reset, ran the SUR and here is the log now...

Tried to run the standalone SP1 (the 903MB version). Returned the error "TRUST_E_NOSIGNATURE(0x800b0100)".

Hello again!

Well, your logs are very unusual. You have a rare strain of the error, hence why the usual fix didn't fix it.

Code:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 13.0
2012-01-08 17:19
 
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
 
(f) CBS MUM Corrupt 0x800B0100 servicing\Packages\Package_2_for_KB2556532~31bf3856ad364e35~amd64~~6.1.1.1.mum servicing\Packages\Package_2_for_KB2556532~31bf3856ad364e35~amd64~~6.1.1.1.cat Package manifest cannot be validated by the corresponding catalog
(fix) CBS MUM Corrupt CBS File Replaced Package_2_for_KB2556532~31bf3856ad364e35~amd64~~6.1.1.1.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
 
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
 
Summary:
Seconds executed: 580
 Found 1 errors
 Fixed 1 errors
  CBS MUM Corrupt Total count: 1
  Fixed: CBS MUM Corrupt.  Total count: 1

Notice that the (f) line (FATAL error) is followed by a (fix) line. The error should be fixed.

Also notice where the replacement file came from:

"from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab"

It came out of the cabinet files which I made, using the files I provided you with yesterday.

However, if you look at yesterday's log, there is an inconsistency. All (f) logs are followed by a (fix) line or two, and no (fix) lines are followed by a (fix) failed line.

However, at the bottom there is a

Code:

Unavailable repair files:
 servicing\packages\Package_2_for_KB2556532~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2345886_RTM~31bf3856ad364e35~amd64~~6.1.1.2.cat
 servicing\packages\Package_for_KB2345886_RTM~31bf3856ad364e35~amd64~~6.1.1.2.cat

section, which should only when there are failures in a log file.

The error in today's log was fixed in yesterdays log. It is being repeatedly fixed, but keeps being re-detected as a failure.

The only hint at a problem is "Package manifest cannot be validated by the corresponding catalog".

I just need to test this, one last time. When I get home this evening, I shall examine the fix I sent you yesterday for clues as to what may have caused this.

In the mean time, can you please the System Update Readiness Tool one last time, and then provide me with the C:\Windows\Logs\CBS\CheckSUR.persist.log

Whatever it may seem, your problem is far from common! But there is no reason to be concerned yet. A second fix this evening will probably sort the problem out.

Richard

Ok. I am down to 3 important updates that will not install (the same 3 btw). The checksur log looks a lot cleaner now lol. I tried to install these seperately from each other and still no go. whenever i try the sp1 install its like it doesnt even start before it pops up and tells me that it failed. Here is the file you requested :