Windows 7: Windows Update error 800B0100,8024200D and 800737712

Hi All,



I rebuild my PC and did a clean install of Windows 7 64 Pro. I have been battling to get Windows update to work about half of the 54 important updates fail.
I have tried:
1. Windows Update Readiness Tool - Didn't do anything as far as I could tell.
2. Microsoft Fix it in default and aggressive mode - still failing.
3. Restored the system back to before the updates 3 times and tried to reinstall the updates. - no joy.

I am out of ideas. I thought of downloading the +- 980 mb standalone SP1 for 7 but I have a feeling it will also fail.

Should I reinstall Windows? What else can I try?

Did you try the correct 'Readiness Tool'?

The following link is for the Windows 7 version:
Windows Update error 800B0100

Some more useful information here too:
Error Code 0x800737712: pertains to Component Store Corrupt, The - Microsoft Answers


Please let us know how it goes, or if you need any further help.

Hello!

Please post your C:\Window\Logs\CBS\CheckSUR.log, and I shall see what I can do. Please don't reinstall yet

Richard

Here it is.CheckSUR.log

I tried sfc/scannow as well, no problems found. When I look at the Checksur.log file, I see a number of corrupt entries. How do I fix them

Thanks for all the advice!

Hello again!

Very well done! Thanks for that log file! Lots of errors! But don't worry, volume of errors doesn't matter, severity does. And none are too severe.

Like so:

WARNING! This fix was created specifically for this user! If you are not this user, do not follow these instructions!
@EFH: 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.

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.persist.log.

Those instructions should fix 102 of your 104 errors. I shall judge the log file, but occasionally, the System Update Readiness Tool (SURT) may refuse to fix so many errors all in one go, and only fix half of them. This is not a problem at all. Just post me the log, and I shall give you your next set of instructions.

Now, you may be wondering what is going to happen to those last two errors! Basically, these are the two remaining unrepaired files:

msil_system.resources_b77a5c561934e089_6.1.7600.16809_en-us_677b0ba496ed2e73.manifest
msil_system.resources_b77a5c561934e089_6.1.7600.20960_en-us_50b433a8b08e3fda.manifest

I believe that they are native components. I should be able to source two good replacements in a couple of hours (I have to help a lot of people, and the only way I can do that is efficient time management - I stack up native components, and only extract copies of them every couple of hours) However, I don't think that this matters too much, because you already have some stuff to get on with!

Thanks a lot!

Richard

Richard,

Thanks a million! Will do as instructed as soon as I get home. Much appreciated!

No problem! The very best of luck to you!

Have a good day!

As instructed I rersn SURT ans as requested here is, the CheckSUR.persist.log CheckSUR.persist.log
and also the checksur.log CheckSUR.log

I reran Windows update and its down to error codes 8024200D and 80073712

Many thanks!

Elmar

Hello Elmar!

Thanks for those logs! Just those two files remaining!

Unfortunately, these files have turned out to be a very slight problem!

Basically, there is never any guarantee that I can actually find a replacement .manifest file just from that log file - a .cat or .mum file, then pretty much yes, but .manifest, only 98% of the time.

Those two were not native components, and nor were they SP1 components, and nor were they part of some of the bigger .net Framework updates. I used all of the techniques which I could to find them myself, but failed.

What this means is that to find this replacement, I need to know from which update that file originates, so I can extract you a replacement.

Have a look at the file name of a .cat file:

Package_3_for_KB2385678~31bf3856ad364e35~amd64~~6.1.1.0.cat

I immediately know which update to download. Easy! .mum as well.

However, a .manifest: msil_system.resources_b77a5c561934e089_6.1.7600.20960_en-us_50b433a8b08e3fda.manifest

No such information. (However, it looks to come from a .net Framework update.)

Basically, the information which tells me where that manifest originated is in your registry, to which I have no easy access!

This is why I need to access your registry. Fortunately, I only need to access the COMPONENTS sub-hive. This hive only contains Windows information (as far as I am aware) It isn't any of your personal hives. I won't be able to see who you are, what programs you have installed, or anything like that. I will however, be able to see:

• Which Windows updates you have installed, and if any are corrupt, only partly installed etc. etc.
• Which language packs you have installed.

However, I am not interested, and will only look at the little bit I need to.

I do take privacy very seriously, and although many people have sent me their hives before, and there is absolutely nothing to cause concern, it is important that you understand what we are asking you or anybody to do online, so that you can make your own choices.

If you are still not comfortable, please do raise any concerns you have with me. If you are not happy with this, we can look at other options, including things like non destructive re-installs, however, we are right on the brink of a repair, if you stick with me for just a little longer.

However, before we get to that, there is one last option.

I actually have a nearly finished program to automate this process (basically, an automated program works out where the .manifest file originated from)

It is completely safe, however, it might not work (because it isn't quite finished yet) However, I would not be giving it to you if it wasn't safe - which it is.

You will be the first person in the world to use this tool, after my beta testers! Hopefully it will work - its maiden run!

Please download the attached .exe file, and run it.

In the "Paste scan here:" box, please paste in the following:

Trace::
msil_system.resources_b77a5c561934e089_6.1.7600.16809_en-us_677b0ba496ed2e73.manifest

and press Run.

One of two things will come up. An error message, or a log file! Hopefully a log file!

Whatever happens, please leave the message box on screen. Then, hold down the Ctrl key on your keyboard, and whilst still holding down this key, press and release the C key. Now release the Ctrl key. Nothing will appear to have happened, except for a possible beep.

Now please right click and paste into a new reply here.

Now please repeat for this scan:

Trace::
msil_system.resources_b77a5c561934e089_6.1.7600.20960_en-us_50b433a8b08e3fda.manifest

In future versions, this will be easier!

Hopefully, you will have pasted the contents of the message!

My fingers are very crossed, but otherwise, I will show you how to upload your COMPONENTS hive, and you can PM me the link.

Thank you very much. Personally, I do not believe that there is anything to be at all concerned about, however, *please do speak to me if there is.

Richard

Hey Richard,

I'll run it as asap. I understand your concerns and I appreciate the trouble you are going to on my behalf. It is much appreciated.

I post the results later today.