Can't Install SP1

Petey7 · 26 May 2011

Since I hadn't installed any programs or copied my files over yet, I decided to go ahead and just do another clean install. It seemed like the easiest way to fix the problem. I'm still going to give rep all around.

Shadowjk · 27 May 2011

Okay - Unfortunately Due to Time zones - Richard was unable to help you in time

- Thanks for the Rep as well

I will mark this thread as solved

niemiro · 29 May 2011

Hello again!

Sorry for the delay in responding. I am glad that your problems are now resolved! I shall just explain a few things to you:

Code:

Cabinet C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab was either not found or its signature was not valid.  (2148098064)
Deleting.

Have a look at that error code:

Code:

C:\Users\Richard>err 2148098064
# for decimal -2146869232 / hex 0x80096010 :
  TRUST_E_BAD_DIGEST                                            winerror.h
# The digital signature of the object did not verify.

C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab is a cabinet file dropped by the System Update Readiness Tool (SURT). What happened was that the file became corrupt, so that the Digital Signature no longer verified, so SURT "Deleting." it.

Hence, when you went looking for it, you couldn't find that file.

You first ran SURT on 2011-05-26 00:08. That file was dropped at approximately that time. On the same day, about 15 hours later, the file had become corrupt.

Now that the file had been deleted, if you had re-run SURT, it would have re-extracted that file and continued, however, since each run takes several hundred seconds on your computer, and I didn't really need a new run, I allowed it to slide.

What worries me most is that we put a file on your hard disk, and within 15 hours it has become corrupt.

SFC found a corrupt file. SP1 amazingly managed to change the version in System32, the store copy was not corrupt, and the problem went away.

Then this file became corrupt:

servicing\Packages\Microsoft-Windows-Tuner-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.mum servicing\Packages\Microsoft-Windows-Tuner-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.cat

There are many, many reasons for this, and the likeliest is not the hard drive.

Then another file showed up in SFC! Not a very important one, so I ignored it.

Then your servicing stack become corrupt. This was a bit of an odd case.

Then that .cab file became corrupt.

That was the reason I asked you to test your hard disk :)

Have a great day!

Richard