Can't install ie 11 - error code 9C59 on MacBook Pro windows partition

[G10EGG]

I have a new high spec MacBook Pro with VM Ware Fusion Pro Windows 7 Pro virtual machine.
It seems to work however I cannot upgrade from Windows IE 10 to 11. I get error code 9C59. I have tried updating from Windows update and freestanding update downloaded from MS.
I am not able to use a Certificate for specific websites though the certificate has been renewed and checked. It returns error 403.7 when I go to the web sites. It works if I reset the ie10 to default browser settings but then if I change to a new tab or open a new window it does not work!

I have followed the instructions for Windows update Instructions and ran the SURT (which only took a few minutes and returned a message "did not find any integrity violations") and the SFC scan. I have tried attaching a zipped copy of the scan log but it is 250 Mb and too large to upload. I have attached a screen print of the install error message.

This is my first thread and I hope that I have provided enough information. The limit for the upload is 8 MB - my log file is 250MB - am I saving the wrong file? I have put the zip file in my public dropbox with the link https://www.dropbox.com/s/z72xc2ci483e88i/CBS.zip

Regards

 

[Vuxy]

Hello G10Egg,

Sorry to hear you can't install IE 11.

I've got a few steps for you to try, which should resolve this issue and allow you to install the latest version of IE.

Troubleshooting a failed installation of Internet Explorer 11
Prerequisite updates for Internet Explorer 11
Use the System File Checker tool to repair missing or corrupted system files

If the above suggestions don't help, please do let me know.

Thank you,
VinnyBuxton

 

[techtitan100]

Please follow the http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html and post the requested data

 

[G10EGG]

Thanks

Thanks for the suggestions. The problem is resolved. I spoke to the techies at VM Ware who originally installed Fusion Pro. They fixed the problems - don't ask me how! They spent over 2 hours on line fixing it remotely from the other side of the world.
Thanks again for your suggestions but I can now mark this as resolved.

 

[NoelDP]

Just for reference, the CBS.log file alone was 250MB uncompressed! (just under 13MB compressed)
Here's the error-sequence that I found in the file...

 Line 803603: 2014-07-14 14:53:16, Error                 CSI    [EMAIL="00000722@2014/7/14:13:53:16.303"]00000722@2014/7/14:13:53:16.303[/EMAIL] (F) d:\win7sp1_gdr\base\wcp\componentstore\csd_winners.cpp(1302): Error 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] originated in function CCSDirectTransaction::AddImplicationsToCatalogsAndVerifyComponentHashes expression: (null)
 Line 803605: 2014-07-14 14:53:16, Error                 CSI    00000723 (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #9224351# from CCSDirectTransaction::PrepareForCommit(...)[gle=0x90092004]
 Line 803606: 2014-07-14 14:53:16, Error                 CSI    00000724 (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #9224350# from CCSDirectTransaction::ExamineTransaction(...)[gle=0x90092004]
 Line 803607: 2014-07-14 14:53:16, Error                 CSI    00000725 (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #9224349# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(...)[gle=0x90092004]
 Line 803608: 2014-07-14 14:53:16, Error                 CSI    00000726 (F) CRYPT_E_NOT_FOUND #9224101# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Analyze(...)[gle=0x80092004]
 Line 803609: 2014-07-14 14:53:16, Error                 CSI    00000727 (F) CRYPT_E_NOT_FOUND #9223578# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 38 (0x00000026), pSink = NULL, disp = 0, coldpatching = FALSE)[gle=0x80092004]
 Line 803610: 2014-07-14 14:53:16, Error                 CSI    00000728 (F) CRYPT_E_NOT_FOUND #9223577# 154458 us from Windows::ServicingAPI::CCSITransaction_ICSITransaction::Commit(flags = 0x00000026, pSink = NULL, disp = 0)
 Line 803612: 2014-07-14 14:53:16, Error                 CBS    Exec: Failed to commit CSI transaction to resolve execution chain. [HRESULT = 0x80092004 - CRYPT_E_NOT_FOUND]
 Line 803616: 2014-07-14 14:53:16, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80092004 - CRYPT_E_NOT_FOUND]

This seems to have sprung from this failure..

2014-07-14 14:53:16, Info                  CSI    00000721 Couldn't find the hash of component: Microsoft-Windows-ieframe, Version = 11.2.9600.17207, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the catalog [l:192{96}]"\SystemRoot\WinSxS\Catalogs\854a4fa1015dcfe133f699224ddaf8184bc76218d56440730bb5bcbf88d59ade.cat".

I'd love to know how they dealt with that!

 

[G10EGG]

Thanks Noel

Unfortunately this is meaningless to me! I neither understand the error or the failure. I have been able to install IE 11 and it is now updated. Is this something which now needs correcting. If so how is this done. You have identified the problem (though I can't imagine how from all the information!) have you identified the solution? I appreciate what you have done so far. I thought the techie had solved the problem - perhaps not!
I would welcome your comments

 

[NoelDP]

That data is from before they fixed the problem so shouldn't be relevant any more - if you want to check, please run through the Posting Instructions again, and I'll take a look at the new data and see if anything is still showing.

 

[G10EGG]

Hi Noel

I have posted the log in my dropbox again as it is 25Mb!

https://www.dropbox.com/s/z72xc2ci483e88i/CBS.zip

I ran the scf /scannow a couple of times and each time it returned "did not find any integrity violations"

Thanks again for your help

Regards

Geoff

 

[NoelDP]

The lack of problems with SFC is no surprise - if there had been anything significant, then IE would have refused to install. There is no point in running it more than once, since it will almost always fix everything it's capable of fixing on the first pass.

I was interest more in the changes that happened between the earlier scan and this one.
I haven't had time for a good look - but it does appear that they managed to fix all the background problems. (I just wish I knew how! )

Thanks for posting that.