IE10 install failure, Code 9C59

caiken · 28 Mar 2013

Oh, look! An IE10 installation problem. How unique and unusual!

Ok, sarcasm over. I'm trying to install IE10 on an Asus 1016p netbook with Win 7 Pro 32, and I'm getting good ol' error code 9C59. SFC doesn't seem to find any problems, and the error persists after running SURT. I've attempted to manually install all the prerequisite IE10 hotfixes, and all were either not applicable or already installed. Looking through CBS.log it appears as though I'm missing a file link for iecompat.dll in winsxs, and that's what's killing the update. Assuming that's the case, I don't actually know what, if anything, I can do about it. I've attached the cbs and checksur logs.

**cluberti** · 28 Mar 2013

Yes, it's failing due to that file - however, it's an LDR version of the file, and staging is attempted on that branch for that version of the file earlier, here:

Code:

2013-03-28 12:14:06, Info                  CBS    Exec: Staging Package: Package_1_for_KB2598845~31bf3856ad364e35~x86~~6.1.1.0, Update: 2598845-1_neutral_LDR
2013-03-28 12:14:06, Info                  CBS    Exec: Staging Package: Package_1_for_KB2598845~31bf3856ad364e35~x86~~6.1.1.0, Update: 2598845-1_neutral_LDR, PinDeployment: x86_fcb4a272b2af74410cfad37bf480e21d_31bf3856ad364e35_8.0.7601.21789_none_64be921ac0b5be3e

And the failure, here:

Code:

2013-03-28 12:14:08, Info                  CBS    Failed to find file: x86_microsoft-windows-ie-iecompat_31bf3856ad364e35_8.0.7601.21789_none_bdf42a481f80149c\iecompat.dll [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2013-03-28 12:14:08, Info                  CBS    Failed to gather all required files. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2013-03-28 12:14:08, Info                  CBS    Failed to gather all missing files for package: Microsoft-Windows-InternetExplorer-Package-TopLevel~31bf3856ad364e35~x86~~10.2.9200.16521 [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2013-03-28 12:14:08, Info                  CSI    000001c5@2013/3/28:16:14:08.485 CSI Transaction @0x1349aa0 destroyed

So, at some point you installed an LDR-only version of an IE8 update, which got you to this place. You may have better luck if you manually force install the latest version of iecompat.dll in LDR mode to make sure all of your binaries are at their latest LDR bits before upgrading - it would seem your current IE8 install is not quite right:
A Compatibility View list update is available for Windows Internet Explorer 8: October 25, 2011

How to Forcibly Install the LDR Branch from a Particular Hotfix Package - TechNet Articles - United States (English) - TechNet Wiki

caiken · 28 Mar 2013

I can't think of what that update might have been, but it sounds like this might cause other complications with future updates as well. This machine will be sysprepped and cloned out to about 250 devices, so I'm starting to think that my best bet might be to do a full reinstall rather than roll it out in this condition.

**cluberti** · 28 Mar 2013

I would agree - and be very careful what updates you install. If you can keep it *only* from Windows Update (or a WSUS server you control) prior to imaging, that would be the safest bet.

caiken · 28 Mar 2013

That's typically our procedure. I spoke to the coworker who has done the majority of installations and maintenance on the machine, and he denies installing any standalone hotfixes; still, it came from somewhere. I'm going to ensure that the machine is fully updated before installing any third party software.

Thank you for your assistance.

**cluberti** · 29 Mar 2013

LDR fixes don't come from WU (there have been incidents in the past where LDRs were pushed inadvertently and quickly pulled and re-built and replaced as GDRs, but that hasn't happened in a few years that I'm aware of), so while he may not remember it, it happened.

Good luck on your rebuild!