Setup exit code: 0x00009C59 installing IE10 and Empty Win Feature List

[tanman]

Hi,

I'd be grateful if someone can help me with this problem.

I have trawled this forum and others to find a resolution to this issue, but to no avail.

The story so far:
1. I tried to install IE 10 and it gave a 9C59 error IE10_main.log attached
2. Following instructions to resolve this I ran SFC /scannow
3. Then the System Update Readiness tool CBS.log and CheckSUR.log files attached.
4. I found a post that suggests looking at the Windows features dialog, only to find out mine is blank.
5. I checked the forum for a solution to this and found Fix for Blank or Empty Windows Features List in Vista and 7, which started me on the road to analyzing the CheckSUR.log
6. At this point I ran out of talent...

Does anyone have any ideas as to what is going on. I really do not want to reinstall windows from scratch to fix these issues, is there another option?

many thanks,

Anthony

 

[NoelDP]

You have a number of files showing as damaged or missing in the CheckSUR

Unavailable repair files:
 winsxs\manifests\wow64_microsoft-windows-i..etexplorer-optional_31bf3856ad364e35_9.4.8112.20565_none_180ba330ce04c164.manifest
 winsxs\manifests\amd64_529c66a331c42e841855b95307e29b0b_31bf3856ad364e35_9.4.8112.20546_none_4f545362907c8875.manifest
 winsxs\manifests\amd64_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_9.4.8112.20586_none_76d4f0748dc09ab4.manifest
 servicing\packages\Microsoft-Windows-PlatformUpdate-Win7-SRV08R2-Package-MiniLP~31bf3856ad364e35~amd64~ko-KR~7.1.7601.16492.mum
 servicing\packages\Microsoft-Windows-PlatformUpdate-Win7-SRV08R2-Package-MiniLP~31bf3856ad364e35~amd64~ko-KR~7.1.7601.16492.mum
 servicing\packages\Microsoft-Windows-PlatformUpdate-Win7-SRV08R2-Package~31bf3856ad364e35~amd64~ko-KR~7.1.7601.16492.mum
 servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Com-WinIP-Package~31bf3856ad364e35~amd64~el-GR~7.1.7601.16492.mum
 servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Shell-WinIP-Package~31bf3856ad364e35~amd64~el-GR~7.1.7601.16492.mum
 servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Windows-WinIP-Package~31bf3856ad364e35~amd64~et-EE~7.1.7601.16492.mum
 servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Windows-WinIP-Package~31bf3856ad364e35~amd64~et-EE~7.1.7601.16492.mum
 servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Windows-WinIP-Package~31bf3856ad364e35~amd64~hi-IN~7.1.7601.16492.mum
 servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Windows-WinIP-Package~31bf3856ad364e35~amd64~hi-IN~7.1.7601.16492.mum
 servicing\packages\Win8IP-Microsoft-Windows-Multimedia-Package~31bf3856ad364e35~amd64~el-GR~7.1.7601.16492.mum
 servicing\packages\Microsoft-Windows-PlatformUpdate-Win7-SRV08R2-Package-MiniLP~31bf3856ad364e35~amd64~ko-KR~7.1.7601.16492.cat
 servicing\packages\Microsoft-Windows-PlatformUpdate-Win7-SRV08R2-Package-MiniLP~31bf3856ad364e35~amd64~ko-KR~7.1.7601.16492.cat
 servicing\packages\Microsoft-Windows-PlatformUpdate-Win7-SRV08R2-Package~31bf3856ad364e35~amd64~ko-KR~7.1.7601.16492.cat
 servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Com-WinIP-Package~31bf3856ad364e35~amd64~el-GR~7.1.7601.16492.cat
 servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Shell-WinIP-Package~31bf3856ad364e35~amd64~el-GR~7.1.7601.16492.cat
 servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Windows-WinIP-Package~31bf3856ad364e35~amd64~et-EE~7.1.7601.16492.cat
 servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Windows-WinIP-Package~31bf3856ad364e35~amd64~et-EE~7.1.7601.16492.cat
 servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Windows-WinIP-Package~31bf3856ad364e35~amd64~hi-IN~7.1.7601.16492.cat
 servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Windows-WinIP-Package~31bf3856ad364e35~amd64~hi-IN~7.1.7601.16492.cat
 servicing\packages\Win8IP-Microsoft-Windows-Multimedia-Package~31bf3856ad364e35~amd64~el-GR~7.1.7601.16492.cat

I'll post a fix for these later, and we'll see how things look then.

 

[NoelDP]

I've uploaded a file - tmnaa.zip - to my SkyDrive at Noel's SkyDrive
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 tmnaa in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

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

And 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.

 

[tanman]

Hi Noel,

Many thanks for the time you've spent.
These are my new logs. Still errors I'm afraid.

Anthony

 

[tanman]

Hi Noel,
Sorry I just checked through your instructions again and I copied the manifest files to the wrong directory. Doh!

I've run CHeckSur again and these are the new files


Anthony

 

[NoelDP]

We're getting there

One question, before I post a new fix - you now appear to be using an older copy of the CheckSUR tool??

Please make sure that you are using file named Windows6.1-KB947821-v26-x64.msu - if not, please download a new copy from....
Download System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [February 2013] from Official Microsoft Download Center

 

[tanman]

I've copied the latest version of the CheckSur tool, do you want me to run it?:huh:

Anthony

 

[NoelDP]

Yes please - it may find more

 

[tanman]

Results of more recent CheckSur

 

[NoelDP]

That's still the old version??
Here's the headers from my run (and an earlier run of yours)

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
[B]Package Version 18.0
[/B]2013-04-27 15:28

Here's the header from your latest run...

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
[B]Package Version 9.0[/B]
2013-04-27 14:53

 

[tanman]

I'm sure I just downloaded your linked file...

Could this command set the version to use?
CheckSURPackage.EXE /Quiet /WindowsUpdate /DeleteBadCab /pkgversion=9.0 /fixcab=%windir%\CheckSur\v1.0\*.CAB /fixcab=%windir%\CheckSur\*.CAB /pkgdownload

This is what I use to run CheckSUR.exe from this website.

regards,

Anthony

 

[NoelDP]

WHY are you fiddling about with it? it's designed to 'just run'!
Please forget anything you see on that page (it's just some idiot showing off)

Just download it and follow the instructions in the http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html and post the log file.

 

[tanman]

I could never find CheckSUR.exe and this was the only explanation I could see to run it more frequently, other than that I seem to have to run the MSU file each time? Maybe I was just supposed to run the msu each time, but lots of sites said run CheckSUR.exe?

Most recent files attached.

Again thanks for your help.

Anthony

 

[NoelDP]

That's all you need to do - run the .msu each time.
It never actually installs anything, but it does use the TrustedInstaller service a lot, and corrects problems.

That log's more like it - and we can have some confidence in it now.

Unavailable repair files:
 winsxs\manifests\wow64_microsoft-windows-i..etexplorer-optional_31bf3856ad364e35_9.4.8112.20565_none_180ba330ce04c164.manifest
 servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Windows-WinIP-Package~31bf3856ad364e35~amd64~et-EE~7.1.7601.16492.mum
 servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Windows-WinIP-Package~31bf3856ad364e35~amd64~et-EE~7.1.7601.16492.mum
 servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Windows-WinIP-Package~31bf3856ad364e35~amd64~hi-IN~7.1.7601.16492.mum
 servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Windows-WinIP-Package~31bf3856ad364e35~amd64~hi-IN~7.1.7601.16492.mum
 servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Windows-WinIP-Package~31bf3856ad364e35~amd64~et-EE~7.1.7601.16492.cat
 servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Windows-WinIP-Package~31bf3856ad364e35~amd64~et-EE~7.1.7601.16492.cat
 servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Windows-WinIP-Package~31bf3856ad364e35~amd64~hi-IN~7.1.7601.16492.cat
 servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Windows-WinIP-Package~31bf3856ad364e35~amd64~hi-IN~7.1.7601.16492.cat

I'll post the new fix protocol in a few minutes.

 

[NoelDP]

I've uploaded a file - tmnab.zip - to my SkyDrive at Noel's SkyDrive
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 tmnab in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

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

And 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.

 

[tanman]

New logs as requested.

Have you any idea how my system got in to this mess and where are you getting the missing packages / manifests from?

Thanks for all of the help.

 

[NoelDP]

I have most of the updates for Windows downloaded and extracted for just this purpose (It uses rather a lot of disk space, what with 4 versions, and various languages included!)

Your system is nowhere near as bad as some I've seen - the CheckSUR log is clean now - as to the cause, it could be any of a number of things including forcibly shutting the machine down during updates.

Please run another SFC /SCANNOW and post the new log, so we can check that the rest of the file system isn't affected by the changes we've achieved.

 

[tanman]

Hi Noel,

Thanks for all the help so far.

CBS.Log attached, still some errors present!

regards,

Anthony

 

[NoelDP]

The SFC scan appears to have corrected the only remaining error

Time to try Windows Update again - do a manual scan first, and see what happens.

 

[tanman]

Hi Noel,

IE 10 appears to have installed, but not correctly. The program has not created any icons either on the desktop or in the start menu. The install also still appears in the Windows Update list.

I have attached new CBS.log, ie10_main.log, CheckSUR.log and CheckSUR.persist.log for info.

It still looks as though a couple of errors.

Thanks

Anthony