Solved Cannot install IE 11 Update, Code 9C59 error

[rogerh2]

Hello, I hope someone can help.

I can't install Internet Explorer 11. Windows Update goes through the installation, and then fails with a "Code 9C59" error. Been fighting this for weeks, tried the update nearly a dozen times, still fails.

I have run SURT several times, and it seems to complete normally, but it hasn't fixed the problem. Just ran it again this evening, as instructed in the "Windows Update Posting Instructions".

Then ran 'sfc /scannow' as instructed (this is probably the 5th time I've run it). It completes with a message that it found some corrupted files but could not fix them.

Finally, ran the IE11 update again, which failed again , and grabbed a screen shot.

The screen shot of the update error is attached. I also tried to attach the Zip'ed CBS logs, but the upload failed: think it may be too big (it's 25 MB). Any suggestions on how to work around that?

Appreciate any help you can give me.

Thanks,
Roger H.

 

[koolkat77]

Hello rogerh2,

I'm sure Noel will be here to help in no time.

In that between you could run http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html

 

[rogerh2]

Thanks, koolkat77,

Appreciate the quick reply.

In regards to 'sfc /scannow', I've run it multiple times - but the log files were too large to upload (even Zip'ed).

Think that I've figured a way around it, though - had to split the folder into two pieces, and put the CAB files in a separate Zip archive.

Here they are, attached. One has the all the files in the CBS log folder except the CAB files, and the other has the current CAB files from the most recent times I ran 'sfc /scannow'. (BTW, there were some other CABs in the folder, apparently from other times I ran 'sfc' in the past: but they were larger and I didn't attempt to include them.)

Hopefully this is everything that is needed to figure this thing out.

Thanks,
Roger H.

 

[NoelDP]

Your CheckSUR results show a number of problems...

Checking Component Store
(f) CSI Payload File Corrupt 0x00000000 CntrtextInstaller.dll x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5 
(f) CSI Missing Identity 0x00000000 identity amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_10.2.9200.16866_none_90ffcbac92b25233 
(f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_10.2.9200.16866_none_90ffcbac92b25233.manifest amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_10.2.9200.16866_none_90ffcbac92b25233 
(f) CSI Payload File Corrupt 0x00000000 CntrtextInstaller.dll x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_0b66cb34258c936f 
Summary:
Seconds executed: 1514
 Found 4 errors
  CSI Manifest Failed Catalog Check Total count: 1
  CSI Missing Identity Total count: 1
  CSI Payload File Corrupt Total count: 2
Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_10.2.9200.16866_none_90ffcbac92b25233.manifest

The SFC results show the following problems...

 Line 6643: 2014-10-24 21:05:28, Info                  CSI    0000033d [SR] Repairing 4 components
 Line 6644: 2014-10-24 21:05:28, Info                  CSI    0000033e [SR] Beginning Verify and Repair transaction
 Line 6647: 2014-10-24 21:05:28, Info                  CSI    00000340 [SR] Cannot repair member file [l:24{12}]"chs_boot.ttf" of Microsoft-Windows-BootEnvironment-Core-Fonts-CHS-Boot, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 6650: 2014-10-24 21:05:28, Info                  CSI    00000342 [SR] Cannot repair member file [l:22{11}]"PINTLGT.IMD" of Microsoft-Windows-IME-Simplified-Chinese-TrigramDictionary, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 6653: 2014-10-24 21:05:29, Info                  CSI    00000344 [SR] Cannot repair member file [l:18{9}]"l2057.ngr" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 6656: 2014-10-24 21:05:30, Info                  CSI    00000346 [SR] Cannot repair member file [l:38{19}]"NlsLexicons0816.dll" of Microsoft-Windows-NaturalLanguage6, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

We need to deal with the CheckSUR problems first - I'll post a fix for the easy bit in a minute, and then we can work on the more difficult bits later.

 

[NoelDP]

I've uploaded a file - rh2aa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder rh2aa in the same place.
Open this folder - there should be one folder inside it (Manifests)

Copy the content of the manifests folder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

 

[rogerh2]

HI, Noel,

Thanks for the response, and the Zip file.

Two questions, though, before I run CheckSUR again with the manifest file that you provided - I noticed that the file's name starts "amd64_...": that sounds like it refers to an AMD processor, but my laptop has an Intel i7 CPU. Is the "amd" in the name significant? (Just want to double check.)

Also, when you said to run the CheckSUR tool again, do you mean run installation of the SURT update file again (i.e. 'Windows6.1-KB947821-v33-x64.msu')?

Appreciate your patience - just want to be sure that I understand what I am doing.

Thanks,
Roger

 

[NoelDP]

There are three type of Windows file - x86 (32-bit), amd64 (64-bit normal processor) and IA64 (64-bit Itanium processor). The 'amd64' covers both Intel and AMD processors.

 

[rogerh2]

Thanks, Noel.

OK, I ran SURT again after copying the .manifest file you provided into the folder indicated.

Attached are the new CheckSUR .log and .persist.log files (Zip'ed).

Appreciate all of your help.
Roger

 

[NoelDP]

I was hoping that CheckSUR would be able to repair the missing Identity problem once the correct Manifest file was present - it seems not.
I'll work up a fix for that later.
In the meantime, please run SFC /SCANNOW again, and post the new CBS.log file - then we can get to work on the other missing and corrupt files.

 

[rogerh2]

Appears this one is going to be a bit difficult to fix.

Anyway, ran 'sfc /scannow' again, and here is the new 'cbs.log' file.

Thanks,
Roger

 

[NoelDP]

Nah - just a bit fiddly

Here's the problem files according to SFC...

 Line 21295: 2014-10-27 00:57:28, Info                  CSI    0000033d [SR] Repairing 4 components
 Line 21296: 2014-10-27 00:57:28, Info                  CSI    0000033e [SR] Beginning Verify and Repair transaction
 Line 21299: 2014-10-27 00:57:28, Info                  CSI    00000340 [SR] Cannot repair member file [l:24{12}]"chs_boot.ttf" of Microsoft-Windows-BootEnvironment-Core-Fonts-CHS-Boot, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 21302: 2014-10-27 00:57:30, Info                  CSI    00000342 [SR] Cannot repair member file [l:22{11}]"PINTLGT.IMD" of Microsoft-Windows-IME-Simplified-Chinese-TrigramDictionary, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 21305: 2014-10-27 00:57:31, Info                  CSI    00000344 [SR] Cannot repair member file [l:18{9}]"l2057.ngr" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 21308: 2014-10-27 00:57:33, Info                  CSI    00000346 [SR] Cannot repair member file [l:38{19}]"NlsLexicons0816.dll" of Microsoft-Windows-NaturalLanguage6, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

...add the missing/corrupt CheckSUR files

(f) CSI Payload File Corrupt 0x00000000 CntrtextInstaller.dll x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5 
(f) CSI Payload File Corrupt 0x00000000 CntrtextInstaller.dll x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_0b66cb34258c936f

...and the missing Identity... Unh?? - I misread it earlier, and CheckSUR did in fact manage to fix it!

So we only have the file problems to deal with after all.

I'll post a fix protocol later.

 

[rogerh2]

Hi, Noel,

Just on the off chance, I tried the update again after the last time running SURT using the .manifest file you provided.

It worked! Now I have Internet Explorer 11 installed. (All that work for just to get a new version of IE.

So, while there are apparently still file problems on the PC, it's not causing any noticeable problems at the moment. I certainly would like to get them fixed, sometime, but it's not urgent.

No need to spend more time on this, unless you want to. (And, the file issues may have changed anyway, since I've installed several more Windows Updates now.)

Really do appreciate your time and effort on this problem, and especially for fixing it for me.

Thanks,
Roger

 

[NoelDP]

I've uploaded a file - rh2ab.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\rh2ab
hit the enter key - if you get a 'Not Found' error try
DIR D:\rh2ab
or
DIR E:\rh2ab



The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



XCOPY <drive>:\rh2ab <drive>:\windows\winsxs /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

 

[rogerh2]

Thanks, Noel,

Appreciate the files to fix my computer problem.

Before I do this, though, I want to double-check: it's not a problem that I was able to get the Windows Update to work since the last SFC results I sent you (in fact, installed several updates)? I.e., no possibility that the updates may have replaced one of these problem files, and XCOPYing the ones you sent might replace a new file with a different version?

Just checking - please let me know.

Thanks,
Roger

 

[NoelDP]

Nope - any files that new updates have installed will be either in different locations, or can be safely overwritten by the files here.

 

[rogerh2]

Thanks, Noel.

I followed your directions, then re-ran SFC, and it said that it "found no integrity violations."

Guess that means you fixed it.

I've attached the latest CBS.log, so you can check.

Thanks for all your help!
Roger

 

[NoelDP]

That looks good to me - with any luck it should prevent any more problems wit Windows Update.

Good luck!

 

[rogerh2]

Thanks, Noel,

Appreciate all of your work getting this problem fixed.

Been using the computer for a few days, and everything seems to be fine. Amazing work! I'm glad to find that there are people like you who actually understand how to fix Windows rather than just say "do a fresh reinstall of Windows, that'll fix it. "

One more question, if you don't mind - I think that this problem may have been caused by a problem with the hard disk. It seems to be developing bad sectors: already had to reinstall Windows 7 once before, and Chkdsk has found and marked a number of bad sectors on the drive.

(If you can trust Chkdsk: it seems to be a pretty crude piece of software, kind of like using a sledgehammer - all it can do is erase clusters that have problems or mark disk sectors as bad.)

Do think these corrupted files that you fixed could be related to the apparent problems with the hard disk? I'd appreciate your opinion or any insight on this.

Thanks again for your help,
Roger

 

[NoelDP]

'bad sectors' in CHKDSK are always a BAD sign!
The reason is simple.
All hard drives have a number of 'spare' sectors which the firmware deals with directly - and substitutes for bad sectors so that Windows doesn't even know about them. Once all the available spare sectors have been used, then windows has to do the job - and it's only then that you see bad sectors appearing in the CHKDSK results.
Therefore it's quite possible that the three or four bad sectors that appear are actually only the tip of an iceberg that could be over a thousand sectors large.

Back up your data to external storage NOW - and then test the hard drive with the manufacturer's test utility run the short test first and see if it fails. If that passes, try the long test. If either fail then the drive should be replaced.
The reason for running the short test first is that it doesn't place the same high level of stress on the drive hardware as the long test - so is less likely to destroy the drive completely. - which is why you must back up data before running either test!

CHKDSK is a pretty good tool really - but it's not infallible. If the number of bad sectors it shows is climbing steadily it indicates the drive is failing progressively - and needs replacement sooner rather than later.

 

[rolflin]

This is still happening on 2016!!



Noel You are my last chance!! Got followed all tricks on blogs... but no luck.

Uploaded a CBS.LOG file after sfcfix and sfc /scannow..and a lot more of fixes...