IE 11 Update Won't Install Error Code 9C59

[Cyber Coach]

Running Windows 7 Home Premium on an Asus X53U Laptop. Windows build 6.1.7601. AMD c-60 Proc, 1.0 Ghz, 8.0GB Physical memory installed.

Can't get IE 11 to install, error code 9C59 after running SURT. The old error message was 9c47. Updates shows that IE10 is an optional update, if you attempt install it ends on 9C48. Likely because IE10 is already installed. (saw somewhere that is what the 48 code means in the error message).

Before reading this forum I read I should uninstall ie10. That was not good, got browser with no address bar and it was not in full screen. Ran system restore and found this forum.

Ran SURT KB947821, took 4.5 hours, no errors, no msgs just a long execution. Ran sfc /scannow as Administrator, ended with message "Windows Resource did not find any Integrity Violations.

I've attached to CBS zip files as I read system only accepted 8.0MB file size. My zip was 9.xMB so I split into two and will have to post second file. Sorry if I've done this wrong.

Not sure what I should do next.

 

[Cyber Coach]

Second cbs zip file. Hope I didn't break a rule but wanted all required information to reach forum.

 

[NoelDP]

You 'done good' - thanks!

Here's the source of your problems, in summary, from the CheckSUR results...

Summary:
Seconds executed: 17352
[B] Found 411 errors
 Fixed 353 errors
[/B]  CBS MUM Missing Total count: 411
  Fixed: CBS MUM Missing.  Total count: 353
  Fixed: CBS Paired File.  Total count: 348

It also explains why CheckSUR took so long!

It's going to take me a while to source all the remaining files for you and craft the repair.
Don't run away!

 

[NoelDP]

...and here's the detailed error list (for my reference!)

Unavailable repair files:
 servicing\packages\Package_110_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_146_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_147_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_148_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_149_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_150_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_151_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_152_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_153_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_154_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_155_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_156_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_157_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_158_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_159_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_160_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_161_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_162_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_163_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_164_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_165_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_166_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_167_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_168_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_169_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_170_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_171_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_172_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_173_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_174_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_175_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_176_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_177_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_178_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_179_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_180_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB2817183~31bf3856ad364e35~amd64~~10.2.1.0.mum
 servicing\packages\Package_1_for_KB2829530~31bf3856ad364e35~amd64~~10.2.1.0.mum
 servicing\packages\Package_1_for_KB2838727~31bf3856ad364e35~amd64~~10.2.1.0.mum
 servicing\packages\Package_1_for_KB2846071~31bf3856ad364e35~amd64~~10.2.1.0.mum
 servicing\packages\Package_1_for_KB2859903~31bf3856ad364e35~amd64~~10.2.1.0.mum
 servicing\packages\Package_1_for_KB2862772~31bf3856ad364e35~amd64~~10.2.1.0.mum
 servicing\packages\Package_217_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_237_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_253_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_254_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2524375~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_2_for_KB2817183~31bf3856ad364e35~amd64~~10.2.1.0.mum
 servicing\packages\Package_2_for_KB2829530~31bf3856ad364e35~amd64~~10.2.1.0.mum
 servicing\packages\Package_2_for_KB2838727~31bf3856ad364e35~amd64~~10.2.1.0.mum
 servicing\packages\Package_2_for_KB2846071~31bf3856ad364e35~amd64~~10.2.1.0.mum
 servicing\packages\Package_2_for_KB2862772~31bf3856ad364e35~amd64~~10.2.1.0.mum
 servicing\packages\Package_37_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_4_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_4_for_KB2524375~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_57_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Microsoft-Windows-InternetExplorer-LanguagePack~31bf3856ad364e35~amd64~es-ES~9.4.8112.16421.cat
 servicing\packages\Microsoft-Windows-InternetExplorer-LanguagePack~31bf3856ad364e35~amd64~fr-FR~9.4.8112.16421.cat
 servicing\packages\Microsoft-Windows-InternetExplorer-LanguagePack~31bf3856ad364e35~amd64~pt-PT~9.4.8112.16421.cat
 servicing\packages\Microsoft-Windows-InternetExplorer-LanguagePack~31bf3856ad364e35~amd64~zh-CN~9.4.8112.16421.cat
 servicing\packages\Microsoft-Windows-InternetExplorer-LanguagePack~31bf3856ad364e35~amd64~zh-TW~9.4.8112.16421.cat

 

[Cyber Coach]

Thank you. I won't run.

 

[NoelDP]

That's got most of them, I hope....


I've uploaded a file - cchaa.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 cchaa in the same place.
Open this folder - there should be one folders inside it (Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

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

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

 

[Cyber Coach]

Wow, thanks. Will execute and provide logs as requested.

 

[Cyber Coach]

Thanks again.

Followed instructions and reran CheckSur, not bad, it ran in 28 minutes. Major improvement from 4.5 hours.

Still have few errors but a real improvement.

Copy of two logs attached.

 

[NoelDP]

A lot better
I'll go for the (new) ones that aren't related to IE9 next - the IE9 ones need some fairly complex manipulations, and I don't have time for that at present.

I've uploaded a file - cchab.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 cchab in the same place.
Open this folder - there should be one folders inside it (Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

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

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

 

[Cyber Coach]

Thanks for the next batch. Downloaded and installed. One package said it was already in folder. I told it to copy and replace. Ran CheckSur, down to 18 minutes. Said it found 8 errors and fixed 8 errors. Hope this means we are good to execute IE11 update.

Attached is new cbs zip file. Both logs are contained, I checked before posting.

Thank you.

 

[NoelDP]

That was definitely unexpected! - the three fixes I applied also fixed the other detected problems (with a little help from CheckSUR)!

By all means, go ahead and see if IE11 - success or failure, please post new CBS/CheckSUR and windowsupdate logs so we can try and work out why

 

[Cyber Coach]

So close but long story short.. it failed.

I went straight to updates from the icon is system tray. Said 1 important update to install. This is progress as it is no longer offering up IE10 as an update. The machine has IE10 on it and accepts that it has IE10. The attempt failed with 9c59.

Decided to reboot and forced it to check fo updates. Now it wants four, three related to IE 10, KB2925418, KB2909210, KB2936068 and IE 11. Three installed successfully and IE11 failed 9c59. Rebooted again and tried IE11 update because I'm wired that way. Failed 9c59.

Ran CheckSur and attached results. At least I am over the IE10 hump.

Hopefully the logs will give you the answer. and again Thank you.

 

[NoelDP]

CheckSUR found 5 new errors, and managed to fix them all.
Give IE 11 another go, and see what happens - if it fails again, run a new SFC /SCANNOW and post the CBS.log file.

 

[Cyber Coach]

Thanks Noel.

Do you think there is some sort of loop. Ran CheckSur again. It found what looks like the same 5 errors and fixed them again. Not sure why language packs would be causing grief. Can these packages be replaced?

Attached are logs from this attempt.

(This machine is also BSOD'ing on awake from Sleep. I will post in BSOD section but wanted you to know in case it has a bearing. Can only wake with power button if I want to avoid BSOD>)

Ken

 

[NoelDP]

Very odd.
Let's see what happens if you do this....

Reboot
Run CheckSUR
reboot
Run CheckSUR again
reboot
Attempt to install IE again
run CheckSUR again.

post the new CheckSUR.persist.log file - this should tell us whether the problem is caused by Windows or by the IE install itself.

 

[Cyber Coach]

Executed as per plan. Reboot, run CheckSur, Reboot, Run CheckSur, Reboot, IE 11 Install.
Failed.

Ran CheckSur. Same error reports in persist log. 5 found, 5 fixed. Same language packs. Can we replace these packages?

Thank you for your help

 

[NoelDP]

Looks like it's definitely a windows problem, then - all the logs in that sequence show the 'repair' happening and apparently succeeding - but reverting after a reboot.

We need to work out why this is happening, as no repair can succeed until that is understood and corrected.

The Event Logs will help- it could be that your BSOD problems are related, so please follow the http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html and post the resulting file here - I'll ask the BSOD experts to look in on this thread for analysis.

 

[Cyber Coach]

Thanks. Suspect is Video. Wish I understood more. As I mentioned to them machine wakes fine when I sleep with Windows and use power button to awake. Only crashes when I use hardware to induce sleep and awake with Keyboard.

Is there a way I can remove something and let it be put down fresh to resolve this. Like maybe removing ie10 again?

 

[Cyber Coach]

Noel, i just wanted to ensure you knew that I did not have any bsod while I was running chechsur and rebooting. I can avoid all bsod's by just using power button so bsod is not undoing changes by checksur.

I saw in another post you recommended the manual download and install of ie11.

Would that be something i should do?

 

[NoelDP]

There's no point, until we get the background problems ironed out - it'll undoubtedly fail.
Are you saying that you used the power button each time after running CheckSUR? If so, that may be the reason that the modifications aren't being properly retained.
Please run CheckSUR again and go through a normal reboot (complete with crashes), and then run CheckSUR again, posting the results.