Solved Windows Updates corrupt OS

[dboiler]

My old hard drive died so I put in a new 320GB drive from Dell as the part was still under warranty. I then used my Windows 7 Pro CD to reinstall Windows. Once installed and drivers for the wireless run, I ran Windows Updates which showed I needed 140 critical updates. Some were Windows Security updates and some were normal Windows Updates.

The first attempt at running the updates, I simply selected them all and let it go. It failed and upon restart, the message "Windows is loading files" remains on for a very long time before going into a Startup Repair routine. Then a message saying Startup Repair cannot repair this computer automatically. At that point, I can select a system recovery option menu which gives Startup Repair (which does nothing), System restore, system image recovery, windows memory diags, or command prompt. Oh yea, I ran the Dell built in diagnostics on the hardware and it shows no problems.

At this point I simply reformatted the drive again as I had no data on it and re-ran the W7 install. I then ran just the Windows Security updates and they all ran just fine. I then ran the Windows Updates and once again I ran into the same problem as the above paragraph.

I reformatted and ran W7 install again but this time after running the Windows 7 Security updates I started running the Windows Updates one at a time. On the very first Windows update attempt, I again ran into the same problem.

I did create a system restore cd but this isnt important as I dont have any data.

I really have no idea what is going on. Any help would be appreciated.

Dave

 

[MilesAhead]

Do the same experiment but skip the first Windows Update. Maybe that was the cause of the issue.

 

[dboiler]

That was my thought. I'm in the process of reformatting again. I will keep you updated.

 

[MilesAhead]

That was my thought. I'm in the process of reformatting again. I will keep you updated.

I suspect that pun was intentional. Heh heh.

 

[dboiler]

Ok, here's the "update" (heh heh, although this is no laughing matter); I have formatted and re-installed W7 Pro at least a dozen times. Each time I try running the Windows Updates a little differently. The bottom line is that it really doesn't matter how the updates are installed, i.e.; which order, eventually, after a restart, I get the Startup Repair window where it tries, always unsuccessfully, to repair the damaged files.

Any ideas would be most appreciated.

 

[Layback Bear]

Just a thought.
Where did you get you Windows C/D from?

 

[dboiler]

It's the CD that came with the Laptop.

 

[Layback Bear]

I don't believe that C/D will allow you to do a clean install. (format and install) I believe that C/D is a repair C/D only. If you have a COA sticker on the computer here are two Tutorials by two experts that will guide you in a clean install.


By Brink:
http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html

By gregrocker
http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html

 

[NoelDP]

Recovery DVDs (not CDs, note!) can ONLY do clean installs as a rule -

Before attempting yet another install, Please follow the Windows Update Posting Instructions and post the requested data

 

[dboiler]

I attempted another install before reading NoelDP's last post. This time, though, I used Layback Bears advice using "By gregrocker
Clean Reinstall - Factory OEM Windows 7"

Once again, the system went into the Startup Repair after I had installed several of the Windows Updates one at a time.

Under the Windows Update Posting Instructions from NoelDP there are 5 instructions to respond to. Here are my replies to those 5 instructions:

1. I am unable to download and run the SURT after the OS becomes corrupt. The Windows Updates run just fine and then said a restart was necessary. When I restart and it tries to reload the OS is when I see problems and it automatically goes into the Startup Repair. It never repairs anything and simply states it cannot repair the computer automatically. When I view the problem details, it reports the following:

Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: Unknown
Problem Signature 04: 21199558
Problem Signature 05: AutoFailover
Problem Signature 06: 2
Problem Signature 07: CorruptFile
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

2. I then am able to get to a command prompt to run sfc /scannow which results in a message saying "There is a system repair pending which requires reboot to complete. Restart Windows and run sfc again."

So I restart and wait for the Startup Repair to run which comes back and says Startup Repair could not detect a problem. So I click back into the View advanced options link and go back to a command prompt to try to run the sfc command again.

Again, it results in the same message stating there is a system repair pending.

3. Windows Updates error codes. There were none.

4. Log Collection:

In the c:\windows\logs directory (I'm only able to access this through the command prompt and, therefore, am not able to copy and past any of the logs contents from that machine) there are no logs but there are 3 directories containing files:

...\cbs contains an 86MB file called cbs.log and two cbsPersist.cab files
...\dpx contains a 75KB file called setupact.log which has a bunch of lines basically saying it started a dpx phase and then ended a dpx phase
...\systemrestore contains a file called restore.0.etl

5. Start a new thread. Don't think I should do that.

So, its at this point where I reformat the drive and reinstall windows. However, I have tried reinstalling windows from my Dell supplied reinstallation CD which apparently isn't the right thing to do and then I tried the clean reinstall suggested by gregrocker (from Bears post above) and it didn't work either.

I am stumped what might be going on.

Dave

 

[NoelDP]

It is increasingly likely to be a hardware problem.

Let's have a look at the CBS.log and see what it has to say - compress it and upload it (it should come down to about 5 MB)

 

[dboiler]

Here's the compressed CBS.log file.View attachment 298842

 

[dboiler]

Another tidbit on this problem; Before reformatting again, tried entering Safe Mode - unsuccessful. But then rather than trying to start the machine normally or in command prompt or the several other options, I selected the debug mode. Using this, I was able to start windows normally, it seemed. That's how I was able to get the cbs.log file off and send. I'm also, at this time, attempting to run more of the windows updates.

 

[NoelDP]

This appears to be the first error-set in the CBS.log file....

2013-12-26 12:16:47, Info                  CBS    External EvaluateApplicability, package: Package_for_KB2560656~31bf3856ad364e35~x86~~6.1.1.2, package applicable State: Installed, highest update applicable state: Installed, resulting applicable state:Installed
2013-12-26 12:16:47, Info                  CBS    Session: 30343774_1110934142 initialized by client WindowsUpdateAgent.
2013-12-26 12:16:47, Info                  CBS    Exec: This is a PSF Package.  Job has been saved and we are returning to client.
2013-12-26 12:16:47, Info                  CSI    [EMAIL="000000a9@2013/12/26:17:16:47.814"]000000a9@2013/12/26:17:16:47.814[/EMAIL] CSI Transaction @0x38f480 destroyed
2013-12-26 12:16:47, Info                  CBS    Exec: DPX job state saved for one or more packages, aborting the staging and install of execution.
2013-12-26 12:16:47, Info                  CBS    Perf: Stage chain complete.
2013-12-26 12:16:47, Info                  CBS    Failed to stage execution chain. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]
2013-12-26 12:16:47, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]
2013-12-26 12:16:47, Info                  CBS    WER: Failure is not worth reporting [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]
2013-12-26 12:16:49, Info                  CBS    Reboot mark refs: 0

The log is stuffed with a similar 79 errors (over 8 reboots? - so 10 updates are in a failure state of some kind, even if WER thinks it's not worth reporting.
I can't see any other obvious errors in there.

 

[dboiler]

Here's an update on my Windows Updates problems; Since the last time during a restart when the system horked-up and couldn't repair itself, I have NOT reformatted and reinstalled Windows but, rather, as I mentioned earlier, I selected the Debugging Mode after pressing F8 while the system was coming up. Ever since then, I have been able to install all the Windows Updates and all the Security Updates, Framework Updates, IE Updates, and even the Windows Malicious Software Removal Tool and the Windows Update Agent.

What I have not run are IE 9, 10, and 11 for Windows 7 and Security Update for Windows 7 KB2862330 as I read there might still be issues with that.

Also, I notice in my Update History that these updates Failed:

Update for Windows 7 KB2719857 and KB2732500
and
Security Updates KB2868623 and KB2893984

All the rest of the 130+ updates installed successfully.

I've also been able to install my recently purchased Office 2013 without problems. I'll load all my data and other programs later but for now the laptop seems to be behaving.

Again, the only thing done differently this time was entering the Debugging Mode. I have no idea what that did but despite the 4 failed updates, I'm going to go cautiously forward.

 

[NoelDP]

A couple of failed updates is par for the course - the sequencing isn't perfect, and there's at least one update which doesn't install for the simple reason that another higher-priority one is installed first which contains later versions of the files involved.
You'll probably find that the rest of the files installed happily at the second attempt

I've never had problems with any of your remaining files on any fresh install I've done.

 

[dboiler]

All updates are installed, with the exception of IE 9, 10, and 11, and Office 2013 is installed and functioning. All seems fine thus far so, for now, I'll go ahead and mark this Post as Solved. Thanks very much for all your help Noel, Miles, and Bear.

Dave

 

[NoelDP]

You're welcome - good luck!

...and I really do recommend installing all versions of IE (in sequence, obviously) - IE11 is a lot better than IE8, and I prefer it to Chrome (and refuse to use FireFox - it's too buggy)