Error 9C59 While trying to install IE10 on Win7

I've uploaded a file - pm9aa.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 pm9aa 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.

OK - fix part deux :)


I've uploaded a file - pm9ab.zip - to my SkyDrive at Noel's SkyDrive
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:\pm9ab
hit the enter key - if you get a 'Not Found' error try
DIR D:\pm9ab
or
DIR E:\pm9ab

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

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

The forum software (it's not my forum!) is based on vBulletin www.vbulletin.com

First - please open an Elevated Command Prompt, and run the following command
vssadmin list writers

Is System Writer listed?

If not, proceed as follows...

(filched from an MS techie's post on a similar problem - with mods)

1. perform a clean boot and check if the issue still exists

2. Click Start,in the Search box, type msconfig and press Enter

3. Click Services tab and select Hide All Microsoft Services and Disable All third party Services.

4. Click Startup tab and Disable All startup items

5. Click OK and choose Restart


After the reboot, please run "vssadmin list writers" to check if the "System Writer" can be displayed.

If the issue still exists, please open a CMD prompt as Run As Administrator and type the following commands to see if it repairs the system writer

CD c:\windows\system32
Takeown /f %windir%\winsxs\filemaps\* /a
icacls %windir%\winsxs\filemaps\*.* /grant "NT AUTHORITY\SYSTEM:(RX)"
icacls %windir%\winsxs\filemaps\*.* /grant "NT Service\trustedinstaller:(F)"
icacls %windir%\winsxs\filemaps\*.* /grant "BUILTIN\Users:(RX)"



Reboot and run the vssadmin list writers command again

It has been also reported that there are permissions issues which can cause this kind of issue.
I need to check for the details on that, as the original post was written for Server

That was disappointing

The SFC run worked - there's only two files remaining in the fix list now...

Code:

2013-03-27 14:47:29, Info                  CSI    0000032e [SR] Repairing 2 components
2013-03-27 14:47:29, Info                  CSI    0000032f [SR] Beginning Verify and Repair transaction
2013-03-27 14:47:29, Info                  CSI    00000330 Manifest hash for component [ml:280{140},l:184{92}]"amd64_5f1280df3a4bb949039fc60bc2d4ada9_31bf3856ad364e35_6.1.7601.17578_none_5309bbfea6693aa7" does not match expected value. 
 Expected:{l:32 b:1d570a39941dd1d1a30c85d7af46ec5ca9001db8b4b59d3ea262971c32659a95}
 Found:{l:32 b:f7bbca9cff03652441feb8d7873b624927f2df9701b9d08871ef2084cde69aa5}.
2013-03-27 14:47:29, Info                  CSI    00000331 Unable to load manifest for component [ml:280{140},l:184{92}]"amd64_5f1280df3a4bb949039fc60bc2d4ada9_31bf3856ad364e35_6.1.7601.17578_none_5309bbfea6693aa7"
2013-03-27 14:47:29, Info                  CSI    00000332 [SR] Cannot verify component files for 5f1280df3a4bb949039fc60bc2d4ada9, Version = 6.1.7601.17578, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2013-03-27 14:47:29, Info                  CSI    00000333 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.1833_none_bc1b16f50be25ff5\mfc80JPN.dll do not match actual file [l:24{12}]"mfc80JPN.dll" :
  Found: {l:20 b:fajNsXhQh77rZOYynUsrP890z6Y=} Expected: {l:20 b:EtSVuQJ2cDS5lKkLaOhTjetI2Jg=}
2013-03-27 14:47:29, Info                  CSI    00000334 [SR] Cannot repair member file [l:24{12}]"mfc80JPN.dll" of Microsoft.VC80.MFCLOC, Version = 8.0.50727.1833, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-03-27 14:47:29, Info                  CSI    00000335 Repair results created:
POQ 136 starts:
 
POQ 136 ends.
2013-03-27 14:47:29, Info                  CSI    00000336 [SR] Repair complete

The CheckSUR completely failed - there's no difference to the earlier log, which probably means that you copied the folders to the destination, rather than just the content.
Please try it again, referring closely to the instructions in post #11

Ah - that would explain it - simply run the big download again. (from the Windows Update posting instructions)
It's doesn't actually 'Install' - it simply uses the TrustedInstaller service's built-in routines to do the job