Win 7 Service Pack 1 installation fails - AND messes up drive letters!

[NoelDP]

That the CheckSUR/SURT tool that you downloaded to run the Update Posting Instructions for post#4

(just a naming thing - 90% of people call it CheckSUR, but officially the name is the SURT)

The Macrovision entries should be left alone - it may be that your interfering with them messes some else up down the way.

 

[chrisnd]

Ok got it, done it.
New CBS.6.zip includes last update and SUR logs.

Cheers

Chris D View attachment 335431

 

[NoelDP]

Here's the Summary from the CheckSUR log....

Summary:
Seconds executed: 1201
 Found 4 errors
 Fixed 3 errors
  CSI Manifest Missing Total count: 2
  Fixed: CSI Manifest Missing.  Total count: 2
  CSI Payload File Missing Total count: 1
  CSI Store Directory Missing Total count: 1
  Fixed: CSI Store Directory Missing.  Total count: 1

The remaining error is this....

(f) CSI Payload File Missing 0x00000000 secdrv.sys x86_macrovision-protection-safedisc_31bf3856ad364e35_6.1.7600.16385_none_5d832d711e99213d

This error is best dealt with using the SFC scan...

 Line 33817: 2014-10-02 10:08:01, Info                  CSI    000001bf [SR] Repairing 8 components
 Line 33818: 2014-10-02 10:08:01, Info                  CSI    000001c0 [SR] Beginning Verify and Repair transaction
 Line 33819: 2014-10-02 10:08:01, Info                  CSI    000001c1 [SR] Cannot verify component files for Macrovision-Protection, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
 Line 33820: 2014-10-02 10:08:01, Info                  CSI    000001c2 [SR] Cannot verify component files for Macrovision-Protection-SafeDisc, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
 Line 33823: 2014-10-02 10:08:02, Info                  CSI    000001c4 [SR] Cannot repair member file [l:24{12}]"M1033DSK.CSD" of Microsoft-Windows-MulanTTSVoiceENUDsk, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

I'll try and deal with that one tomorrow.

 

[NoelDP]

I've uploaded a file - cndab.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\cndab
hit the enter key - if you get a 'Not Found' error try
DIR D:\cndab
or
DIR E:\cndab



The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



XCOPY <drive>:\cndab <drive>:\windows\winsxs /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

 

[chrisnd]

View attachment 335793

Ok, done "Windows Resource Protection did not find any integrity violations"


Chris D

 

[NoelDP]

Great!
with any luck Windows Update should work.

Do a new Check for Updates, and try installing only the oldest update found - if it fails, what is the KB number, and the error code?

 

[chrisnd]

I am afraid it failed again - but there is some progress: This time it did not just leave me looking at a black, blank screen but rebooted fully and gave me a proper error message, which read, "Installation was not successful(!). The referenced assembly could not be found. Error: ERROR_SXS_ASSEMBLY_MISSING(0x80073701)".

The SP1 has the update number KB976932 contained in the file windows6.1-KB976932-X86.exe

In the error message there was also 'Go online to seek further advice about this problem' which pointed me at Troubleshoot problems installing Service Pack 1 (SP1) for Windows 7 and Windows Server 2008 R2 - Windows Help

So, I am tempted to try again after disabling the AV etc etc - unless you have other ideas?
It seems strange that the update cannot find something though...
Do we still need to add things?

TIA

Chris d

 

[NoelDP]

That's an improvement, of sorts, at least!

The SXS_ASSEMBLY_MISSING error can be caused by a number of things - I doubt that it's interference from an AV.

Please post the new CBS.log files, and the C:\Windows\windowsupdate.log file.

 

[chrisnd]

View attachment 336692
View attachment 336693

Phew, here we are again! (lost the forum for a while?)
Files as requested

Chris D

 

[chrisnd]

View attachment 336879

Whoops, previous CBS file wrong - try this one.

Apols, Chris D

 

[NoelDP]

1) there's no data in the windowsupdate.log file since the 9th Oct
2) there's no errors in the CBS.log file since 8th Oct.

This is somewhat unusual...

Open Event Viewer
click on the Windows logs entry in the left pane to expand it.
Now click on the Application entry - wait while it loads.
Click on 'File' in the menu bar and select Save...
Save the file as Appevt.evtx
Repeat for the System log
then zip both, and upload them.

 

[chrisnd]

View attachment 336975View attachment 336976

Ok, files herewith as requested.
The previous CBS file was produced yesterday whereas the previous windows log was done a few days ago before the forum disappeared over the weekend.

Thanks again,

Chris

 

[NoelDP]

There are a lot of Access Denied errors - but I can't define the source/cause of them.

I think your quickest ( not to mention easiest) solution may be a repair install.

See the instructions here.... http://www.sevenforums.com/tutorials/3413-repair-install.html?ltr=R

 

[chrisnd]

Sadly, even the repair install followed by the service pack upgrade failed to solve this problem. In other words the service pack upgrade appears to work up until the point where windows should display the login option but just gives a blank/black screen. There appears to be no way out of this!

One additional complication is that after doing a system restore to get back to 'standard' Win 7 when I shut down it now keeps trying to redo the service pack upgrade each time :-( I've got round that though by exiting via CTRL-F4 and choosing 'shutdown' rather than 'install upgrades and shutdown'

 

[NoelDP]

If you go into Windows Update you can Hide the Service Pack - then try using the standalone to do the update.

 

[chrisnd]

Of course, thanks. I hadn't noticed that 'automatic download & install' had re-enabled itself :-(

 

[chrisnd]

Before I abandon all hope of ever getting this service pack installed, doing the 'repair install' procedure again using the version of windows with SP1 already installed is not to be recommended, right?

Might it work or will it undoubtedly stuff things up totally?
TIA, Chris

 

[NoelDP]

In theory it should work - but some people have experienced problems, with the installer refusing to even start.

 

[chrisnd]

Well its starts (optimistically) but then flips out saying I need to have SP1 already installed.

I have tried the SP1 install again - but it still failed as before.

This was even after running a little utility I found buried in the 'Windows Update' program link on the start menu which looks for update 'issues'. I have run it twice (before and after the last install attempt) and both times it informed me that 'service registration errors' had been 'found and corrected' <G>. Looking at the windows update failure itself I am informed that 'unspecified changes to system configuration may have caused the problem' <VBG>.

The only way to get the system working again is to enter 'safe mode' which immediately informs me 'failure configuring service pack reverting changes. Do not turn off your computer". (I am unable to use safe mode to do anything else before this appears.) Several minutes later, a reboot and we are back to how it all started. :-/

A couple of other things I have noticed:
When attempting the service pack install, after the reboot, getting past the 'starting windows' and splash screen, and reaching the blank out, the hard disk light is continually on - not so much as flicker - until I have to shut down using the power button. (I have left it a couple of hours sometimes before doing this). If a DVD is in the drive this also runs indefinitely.
The other thing is that without the service pack, if I go into safe mode command prompt and look at the drive letters, they are all messed up in just the same way - and yet everything boots ok!

So, after all this effort, I am still where I started. I think the service pack is actually installing but there is a configuration issue somewhere which stops the boot up completing and the HDD just keeps looking for the next bit and never finding it.

Anyway, thanks for all the help. Chris d

 

[NoelDP]

I'm going to see if I can find the right guru for you - don't run away!