Cannot install IE 11 Update, Code 9C59 error

Page 1 of 3 123 LastLast

  1. Posts : 9
    Windows 7 Home Premium x64
       #1

    Cannot install IE 11 Update, Code 9C59 error


    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.
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Hello rogerh2,

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

    In that between you could run SFC /SCANNOW : Run in Command Prompt at Boot
      My Computer


  3. Posts : 9
    Windows 7 Home Premium x64
    Thread Starter
       #3

    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.
      My Computer


  4. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #4

    Your CheckSUR results show a number of problems...
    Code:
    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...
    Code:
     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.
      My Computer


  5. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #5

    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.

      My Computer


  6. Posts : 9
    Windows 7 Home Premium x64
    Thread Starter
       #6

    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
      My Computer


  7. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #7

    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.
      My Computer


  8. Posts : 9
    Windows 7 Home Premium x64
    Thread Starter
       #8

    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
      My Computer


  9. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #9

    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.
      My Computer


  10. Posts : 9
    Windows 7 Home Premium x64
    Thread Starter
       #10

    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
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 06:13.
Find Us