Cannot Install ie10 (9c59)

Hi Noel,

Thanks very much for all of your help. I am now using ie11 after a successful ie10 install. I thought I'd give it a try and it worked!

I really can't thank you enough as I have been trying everything I could think of since 10 was released.

It must have been that one file you got me to install. Out of interest isn't the winsxs folder just backups of old updates or something? Why would one corrupt file that seems to have nothing to do with anything have blocked the update

Cheers
Mick

The Winsxs folder is a lot more than just backups!
many of the files in Windows7 only actually exist in the winsxs folder - what you see elsewhere may be nothing but a hardlink to the winsxs file. Also if a file is damaged elsewhere, then the system will attempt to replace it from the winsxs copy.

In this case the file is actually an integral part of the ServicingStack package - which as its name implies takes control of servicing operations. It's this package (in conjunction with a few others) that actually does the work involved in installing new patches and programs - so you can see why things fail if that's not working properly.

Hi,
Same for me, first time I post something here and 2nd IE10 installation failed on WIN7 64bit (IE11 failed too). I tried every item found in the internet...
Finally, SURT, 3xSFC Scan with errors, cleaned event log, started win IE10 update, SFC Scan. CBS log & error screenshot is attached. Now I am here.
I am not a computer crack, I tried to follow your steps so please be patient with me.
Thanks for your help guys.

There's only the one file error in your SFC scan -

Code:

2014-03-23 01:27:49, Info                  CSI    00000311 [SR] Cannot repair member file [l:22{11}]"wdscore.dll" of Microsoft-Windows-ServicingStack, Version = 6.1.7601.17592, 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

- but it's possible that there are other problems.

Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it to your reply.

That has found the same error - and nothing else, so it should be a fairly simple fix.
I'll post the protocol later.

Sorry about the delay!


I've uploaded a file - skmaa.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:\skmaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\skmaa
or
DIR E:\skmaa



The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



XCOPY <drive>:\skmaa <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

seaklarmacher be very careful.
Many of Noels posts/repairs are designed only for the computer in question.

I would suggest that you start a new thread of your own so you can get exact instruction for your exact needs.