Cannot install IE 11 Update, Code 9C59 error

Nah - just a bit fiddly

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

Code:

 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

Code:

(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.

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

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

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

Good luck!

'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.