[SOLVED] Windows 7 x64: KB2904266 fails to install with error 0x80073712

azhur · May 21, 2014

There was a lot of other windows update errors at subj. PC, but CheckSUR fixed almost all of them, except last 5.
And I fixed that 5 myself with help of Googling and other topics of this forum, by copying missing files and registry
keys from another PC with same (or almost same) patch level (both automatically updating from 1 WSUS server).
And now CheckSUR finds no more errors, but I still have problem installing KB2904266.
Reading CBS.log i've nailed down problem to 1 file, but can't find correct file version or other solution:
Here is a log except:

Code:

2014-05-19 16:58:00, Info                  CBS    Appl: Evaluating package applicability for package Package_74_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0, applicable state: Installed
2014-05-19 16:58:00, Info                  CBS    Plan: Package: Package_74_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0, current: Installed, pending: Default, start: Installed, applicable: Installed, targeted: Installed, limit: Installed
2014-05-19 16:58:00, Info                  CSI    0000000e Manifest hash for component [ml:280{140},l:202{101}]"amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.22113_en-us_e223d3b4b184be32" does not match expected value. 
 Expected:{l:32 b:eeea185b6fd16193d1354153df5374af3a6ed1341660f2e3e524b3345316215c}
 Found:{l:32 b:eeea185b2f3e162c289999df9a87a508289a03fa0ffecaa8425d6f4f08811ea6}.
2014-05-19 16:58:00, Info                  CSI    0000000f Looking for manifest in Backup Dir...
2014-05-19 16:58:00, Error                 CSI    00000010 (F) Unable to load manifest for component [ml:280{140},l:202{101}]"amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.22113_en-us_e223d3b4b184be32"[gle=0x80004005]
2014-05-19 16:58:00, Error                 CSI    00000011@2014/5/19:10:58:00.479 (F) d:\win7sp1_gdr\base\wcp\componentstore\storelayout.cpp(2714): Store corruption detected in function ComponentStore::CRawStoreLayout::FetchManifestContent expression: 0
  FileHashMismatch on resource [128]"\winsxs\manifests\amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.22113_en-us_e223d3b4b184be32.manifest"[gle=0x80004005]
2014-05-19 16:58:00, Error                 CSI    00000012 (F) HRESULT_FROM_WIN32(14098) #56621# from Windows::ServicingAPI::CCSITransactionAnalysis_ICSIInventory::GetDeploymentInformation(flags = 0, class = ICSIINVENTORY_GET_DEPLOYMENT_INFORMATION_CLASS_CLOSURE (1), information = {dwFlags=00000000})
[gle=0x80073712]

Any help finding correct version of that manifest?

niemiro · May 21, 2014

Hello, and welcome to Sysnative!

Can you please first run sfc /scannow from an elevated command prompt and then upload the entire CBS folder as per the posting instructions, most importantly the CheckSUR.persist.log file. When fixing a lot of Windows Update errors, I need to use all the clues available to me, including what was initially corrupt (even the stuff CheckSUR fixed on its own) as it gives a lot of information about the why which gives me the best information on how best to fix the remaining problems. I don't like fixing off logfile snippets as then I miss any other factors at work, and there are a surprising number which can cause problems.

Thank you very much!

Richard

azhur · May 21, 2014

OK, if you want to do it that way - here it is.
sfc /scannow finished with message like "found some errors and succefuly fixed them".
CBS.zip attached.

niemiro · May 21, 2014

Thank you very much for uploading that. I've sourced the replacement file and one of the trainees here, Go The Power, will be performing the replacement. We all had to start somewhere, but this does mean that there will be a slight delay whilst I check the fix he provides prior to posting. This ensures that we can provide real world experience for senior trainees. We'll be back shortly :)

Richard

Go The Power · May 21, 2014

Hello axhur

SFCFix Script

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.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

View attachment SFCFix.zip

azhur · May 22, 2014

niemiro, Go The Power - thanks for trying to help.
Today results:
1. Your tool SFCFix.exe maybe good for "common user", but I am trying to fix another PC remotely.
I tried to run it as other cli tools with DameWare Remote Support RCmd (kind of remote shell) - but for no good.
Command: SFCFix.exe SFCFix.zip
Result 1 - program closed after self-update error.
Result 2 - warning message like "corrupt archive".
Looks like some software incompatibility for me.
In any case IMHO it's overkill to use it to copy 1 file.
2. I unpacked SFCFix.zip (no errors) and checked manifest file included.
It's copy of file I already have, SHA-256 EEEA185B2F3E162C289999DF9A87A508289A03FA0FFECAA8425D6F4F08811EA6.
But updater looking for file with SHA-256 EEEA185B6FD16193D1354153DF5374AF3A6ED1341660F2E3E524B3345316215C.
Result - FileHashMismatch error.
Conclusion: required another version of this file, or correction to database where CRCs stored.

niemiro · May 22, 2014

The problem on your particular computer is actually that the registry value holding the SHA256 value is corrupt. I knew (well, very strongly suspected) this right from your first post. This was why I asked for the CheckSUR.log: with a registry corruption like this, it's all the more important to know the full story prior to a fix.

There are always two causes of a manifest corruption: either the manifest is corrupt, or CBS incorrectly thinks that the manifest is corrupt (the hash of the manifest stored in the registry is corrupt). You've worked this all out already.

Now, we could use the found and expected hashes to our advantage - if I know what the expected hash for this manifest *should* be (simple, just hash it), and it doesn't match with the expected hash in the logfile, registry corruption. If the expected hash I know matches that of the logfile's expected hash, but not the logfile's "found" hash, file corruption. If it doesn't match either, either the registry and file system of the OP's system are corrupt, or I've made some error somewhere.

However, hashes such as SHA256 are designed to give a lot of entropy for a very small change. The matching characters at the beginning (EEEA185B) make this, almost to within statistical impossibility (I haven't actually calculated the probability, but it's going to be minute) a case of registry corruption, hands down.

However, I chose not to do this. I chose to go down the "repair the manifest, if no go, repair the registry" route. You're probably thinking WHY??? if I (supposedly) knew this all already.

It was actually because you mentioned you were on a WSUS server, and then this final line "Any help finding correct version of that manifest?". I knew that you were an IT guy. And the sad reality is that I get a huge amount of flak off IT guys. Sometimes it's just because I've overexplained something - it's not that I'm trying to be patronizing in any way, it's because I don't know how skilled each member is, so I have generic canned speeches to use, and future search engine users to think about. I've just completely given up to be honest, and now seek any method which avoids yet another discussion along these lines. From your final comment, it seemed to me that you had already decided that the manifest was corrupt, and that if I said "no, actually, it's the registry" we'd end up with a huge problem over whether or not I fully understood the meaning of "FileHashMismatch". So I decided to get my trainee to go down the not strictly necessary file replace option just to give me some easy ammo to work with on investigating the registry side of things.

But you sussed it out. However, before you are too quick to judge, please take a look at the situation from my shoes. I get IT guys everyday, and in the time it takes me to write this post, I could have answered virtually every other one of today's threads in this forum. With important university entrance exams coming up, I need to save all the time I can. You don't have to agree with this, but do you understand what I'm trying to do and why?

As for using SFCFix, I do that because we have backend tools which help us write the scripts extremely quickly, and it helps us by doing all the permissions, ownership, backups, attributes, etc. It also double checks, under the right conditions, file replacements prior to performing them so that it picks up and prevents mistakes. It's the safest way for us to perform replacements, even if not absolutely necessary.

If you want my assistance and if your willing to work with me, then great. Otherwise I suggest you find another forum to ask your question on.

Richard

azhur · May 22, 2014

Richard, I meant no offense, really.
Maybe it's my "speak style", or maybe my far from perfect skills in English.
I wasn't sure myself at the beginning what is corrupted - file or crc record in registry.
File is easier to check and replace in my situation - and so I asked for file replacement as first option.
File checked and valid.
So, now it's time to check registry, no?

Alex

azhur · May 27, 2014

Thanks for search directions, everyone!
Looks like I found key with wrong CRC and fixed it.

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.22113_en-us_e223d3b4b184be32]
"S256H"=hex:ee,ea,18,5b,2f,3e,16,2c,28,99,99,df,9a,87,a5,08,28,9a,03,fa,0f,fe,\
  ca,a8,42,5d,6f,4f,08,81,1e,a6

After applying of this reg file, KB2904266 installed successfully.
And at least for now target PC is fully patched.

Search

Search

[SOLVED] Windows 7 x64: KB2904266 fails to install with error 0x80073712

azhur

Member

niemiro

Senior Administrator, Windows Update Expert

azhur

Member

niemiro

Senior Administrator, Windows Update Expert

Go The Power

Senior Administrator, Windows Update Expert, Contributor

azhur

Member

niemiro

Senior Administrator, Windows Update Expert

azhur

Member

azhur

Member