Error Code 800B0100, what is all about?

Hello again, juanpch!

I am really glad that it has fixed your issue!

Allow me to give you an (albeit slightly simplified) understanding of those logs and what happened to your computer.

Windows Update has to keep track of which update have already been installed, so that it doesn't install the same update twice etc. etc.

However, it is a bit more complicated than that, and it has to keep many lists of a lot of things (SHA-1 hashes, signatures, component lists, lists in the registry etc. etc.) so that it can tell if a file has become corrupted, or is missing etc. etc.

So, it keeps many lists (lists are a bit of an oversimplification. Many sets of data files and registry lists about an update would be more accurate)

On your computer, some data files become corrupt. 61 files become corrupt in fact (more on how I found that out later) and Windows Update become very confused. Is the update installed (some lists say it is, some lists say it isn't) Do I need to reinstall this update. Are all of the prerequisites in place. Windows Update was just not able to understand, and so it failed with error code 800B0100 for you.

Now, it honestly doesn't matter if the update is installed or not. The reason for this may take a 100% brain usage!

It is likely that the update either was installed at some point, or Windows Update tried to install it, failed, and left a mess which it shouldn't have done.

To undo the mess, we must either remove everything about the update from every list, and then reinstall it, or fill in the gaps (patch up the missing files) And it really doesn't matter which way. So it doesn't matter whether you call the update installed or not, just uninstall it, or repair it.

Now, it is actually much easier to fill in the gaps. The reason is that if you closely inspect the other lists, you can piece together what is missing from the corrupt list, and hence the fix. But trying to remove every last trace is destined for epic disaster!

Unfortunately, Windows Update does not look closely. It just fails. The System Update Readiness Tool is the ONLY thing which can look closely. It looks for mismatches between the data files and lists. And it reports them in its logs C:\Windows\Logs\CBS\CheckSUR.log. Look at your very first CheckSUR.log.

It shows 61 errors. The "(f)" before each line means "Fatal" (ie Windows Update is going to fail to install some updates) Other possible values include (w) for Warning, and (fix) for Fix.

All of those files shown there are part of the behind the scenes of Windows Update, but they are missing, and they are causing your error code. We can insert them manually, but it is tedious and fraught with possible issues down the road. So instead, to actually fix these corruptions, I find a known good copy of every single one of those files, I send it to you (Packs.zip) you put them into a temporary directory, your rerun the System Update Readiness Tool (SURT), SURT finds them, and puts them where they should be, and the system is fixed.

Now look at your second CheckSUR.log. Do you see that every line has either 1 or 2 (fix) entries under it? That shows me that you followed my instructions correctly, and that all went well - All errors have been fixed.

You can also look at the summary, which went from:

Code:

Summary:
Seconds executed: 250
 Found 82 errors
  CSI Manifest All Zeros Total count: 40
  CBS MUM Corrupt Total count: 21
  CBS Catalog Corrupt Total count: 21

to:

Code:

Summary:
Seconds executed: 111
 Found 61 errors
 Fixed 61 errors
  CSI Manifest All Zeros Total count: 40
  Fixed: CSI Manifest All Zeros.  Total count: 40
  CBS MUM Corrupt Total count: 21
  Fixed: CBS MUM Corrupt.  Total count: 21
  Fixed: CBS Paired File.  Total count: 21

And that is why I called it an excellent log. All errors fixed.

Now, if you want to learn more, you can read the basics here: System Update Readiness Tool - CheckSur.log File Analyzis

If you want to take this still further, and I do encourage you to do this if you are interested, send me a Private Message, create a new thread about a particular question, or ask me here.

Don't worry about doing this yourself. If you have any more errors in your CheckSUR.log, simply ask, and I will be more than happy to assist and I could show you what and why I am doing what I am doing.

If you don't want to take it this far, then fair play! You have done very well, have a busy life to manage I am sure, and you are always welcome here, whatever the question!

Have a great day!

Richard

Johnathan Lyman said:

I do want to point out that KB2487426 may have been installed as a part of SP1 but according to the KB article, it will actually not take any effect if it's not installed by itself before SP1. So take a look at the KB article on it and keep an eye out for that problem.

A very good point indeed. I missed that. I would +rep, but need to spread

However, I think that it is fine...the update seems to resolve an issue that could occur during SP1 installation...SP1 has been installed, for better or for worse, the applications did not crash as far as I know, and so I don't think that there is anything to worry about.

I admit that I did completely miss that. Do your sharp eyes see anything else which I have missed or misunderstood, as it is a bit of a confusing KB Article.

Thanks a lot!

Richard

Hello!

Everything is working fine so far and no new issues with updates have came up.

I am what can be called a frustrated programmer because I understand that everyhting lies in those endless lines of code but I am a 3D grapichs worker so I am already very busy to go that far on OS knoweledge.

That does not mean that when I suffer a problem I always like to try to solve it by myself and learn as much as possible.

Your explanation about what has happen is clear (I know that is a simplificated one) but let me ask, if the prob was with the registry of uploads (bad logs, files not downloaded well, etc) when I change the folder name I was deleting that record no? so why it doesn't work after that tabularasa cain of fix?

I was also thinking about the mac update app (I work with both system due to my work) and that it never get confused or develope a problem like this and that is the type of fine tune I was talking about before. Again I like Win OS as much as Mac OS (I like sometimes to be able to get into the soul of the OS and that is easy for non programmers with Windows).

Thank you Johnathan for your comment but as I haven't suffer any issues yet related to the KB2487426 update I will assume that everything is fine. I will let you know if something change.

Thank you again for all your help and time spend on this and If you need some 3D graphics someday u can ask for )))



Cheers,


JC

Hello,

Ceartainly each OS has its pros and cons and Windows do more to be more open to third parties softs and hardwares.

Thank for comments, I am learning from each one.


JC