[SOLVED] Win7 update installation failure (error 80073712) for SP1

T

toomanyhobbies

Contributor
Joined
Mar 26, 2014
Posts
6
Location
Colorado
Hi guys- Was up 'til 1 last night reading and doing all sorts of things on the web to try & solve this issue, but you all seem like the friendliest and most helpful place to post. So, thank you for this forum!

>>Problem<<
For several years, we have been unable to install SP1 on this Win7 machine. It has always failed with the 80073712 code. Nearly every other update since that time goes through just fine (except for KB2604114 and KB2729451, which also fail). Whether I try to update just one of those at a time or all three, it always fails with that same error code.

I've read through Microsoft's thread here (Error Code 0x80073712 occurs in Windows Update or Microsoft Update) and done each step other than the "in place upgrade" option. None of them helped. If at all possible, I'd like to avoid the repair installation if I can, since this was an OEM installation and came with no DVD. Not sure if the "hidden" partition with the OS install files would work for that in this case. Plus, I believe it would involve lots of re-installation of programs, etc. I'm willing to do it if I must, but want to exhaust all other resources first.

In any event, I think I've got all of the log files that might be needed to suss out this issue.

To wit:
System Update Readiness tool log: View attachment CheckSUR.log

SFC log (CBS): View attachment 7490

Link to COMPONENTS hive: https://www.dropbox.com/s/o7pzzbnxh5c792c/COMPONENTS.zip

I believe those are the three things you might need to help, but if there's anything else, please let me know. I'm happy to help in any way that I can, and am highly motivated. :smile9:
 
Hello, and welcome to Sysnative!

I'm so sorry about the delay here. Thank you for the reminder.

To start with, some good news! The system isn't a total right-off yet, as the COMPONENTS hive looks to be in a fairly good way yet. Two small corruptions immediately spring out, so I'll fix those first then re-assess afterwards.

Windows Update Package Replacement

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Please download the attached file, Packs.zip and save this to your Desktop.
  2. Right-click on the file and select Extract All...
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing two folders, Manifests and Packages
  5. Open the Manifests folder and copy the files into the following folder (if there are any files)

    C:\Windows\Temp\CheckSur\Winsxs\Manifests
  6. Open the Packages folder and copy the files into the following folder (if there are any files)

    C:\Windows\Temp\CheckSur\Servicing\Packages
  7. Run the System Update Readiness Tool (SURT) again.
  8. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:

    C:\Windows\Logs\CBS\CheckSUR.persist.log
Also, please re-test Windows Update and let me know whether it now succeeds.

Richard
 

Attachments

Hi Richard-
Thanks so much for your help!

There are a couple of interesting things now.

Firstly, two of the three updates that would consistently fail (KB2604114 and KB2729451) seem to have successfully updated after I applied the fixes you created. It looks like they're working correctly.

SP1, on the other hand, is curious. I tried to install it and Windows Update CLAIMS that it installs correctly (no error code). During the re-boot, the computer lists the completion percentage of SP1 installation, and seems to stall for a LOOOONG time at 8% (more than an hour), then proceeds to 9% for a while, and the next time I checked, it had booted into windows. But then when you check the Windows Update status, it shows that SP1 failed. Actually, it shows that it both succeeded AND failed, which is curious. But I think the fail is the more accurate description, since when I check the current version of the installed OS, it does not list SP1.

In fact, when you look at Windows Update to see what has installed successfully and what has failed, there is a huge list of failed hotfixes listed alongside SP1, but I'm assuming those fixes are all a part of SP1.

So I'm not sure what's going on with it, because the error that appears now seems to be fundamentally different from the original error that I started this post with. The new error code is 80071A90.

Once again, I've attached the requisite files below for your perusal. Thanks again for your help!

SFC Log: View attachment CBS2.zip

CheckSUR: View attachment CheckSUR2.log

Link to COMPONENTS hive: https://www.dropbox.com/s/8cor5py855zxb43/COMPONENTS2.zip

Thank you!
 
Thanks, Tom. I appreciate the check in. Luckily the computer has stopped trying to reboot itself to apply SP1 over and over and over. It seems to have realized that it fails each time. :-) I'll look forward to your future response. Keep up the good work. You guys a doing a great job helping everyone. I can't imagine what keeps you going, but I'm happy you've got it inside you. It's a huge benefit to everyone!
 
Whoops! I read the emailed post instead of your edited one, and replied to that wording instead of your updated post.

So this is very strange indeed.....

As I mentioned in the post above, after I applied your fixes, the computer was improved, but still would not install SP1. It would fail at installation points (roughly 9-14% of the way completed), then reboot and try again. (and again, and again....)

So we got to the point where we wouldn't let the computer reboot anymore, because whenever it tried to install, it would be completely useless for HOURS (minimum of 3 hours, usually closer to 5), and we do use that computer for other things.

However, I just went and checked on the problem, and holy crap!! SP1 is installed. No errors.

I have no idea what changed or why it happened, but apparently rebooting ad nauseum eventually worked? I don't know, but it truly does appear that everything is working as it should now. None of the other updates have failed since then, according to the installed list.

So I really couldn't say why it's fixed, but it's fixed!

Thanks again for your help. Making my way to the tip jar now....
 
Hi toomanyhobbies,

That's great news! Thanks for letting us know you're all up and running again. I'm not entirely sure how it fixed itself, but I'm not going to complain!

Richard fixed all of the problems in your CheckSUR log so it should be okay but if it does ever give you problems in the future then you know where to come!

Tom

P.S. Thank you so much for your donation!
 
You must log in or register to reply here.
Back
Top