Error 9C59 While trying to install IE10 on Win7

PhilM99 · Mar 25, 2013

I have tried to use Windows update to install IE10 (it was offered as an update).
Downloaded ok, but failed with error 9C59.
Followed instructions for manually installing all prerequisite for this update. Only one that failed was 2533623 (said it was not available for this environment).
Ran the SUR check. Shows some corrupted files that it was unable to fix. I have tried several times to upload the cbs.zip as instructed but it times out. Thanks for anything you can tell me. Environment is as stated in my profile, Win7 Pro SP on Intel Core 2 Duo.
(Edit I uploaded the Logs without the cabs, unfortunately as a .rar can you read that ok, sorry, miserably slow internet connection)

NoelDP · Mar 26, 2013

You have a fair amount of corruption.

Code:

Summary:
Seconds executed: 1205
Found 30 errors
CSI Manifest and S256H Do Not Match Total count: 8
CSI Manifest Failed Catalog Check Total count: 7
CSI Payload File Corrupt Total count: 1
CBS MUM Corrupt Total count: 3
CBS Catalog Corrupt Total count: 11

Code:

Unavailable repair files:
 winsxs\manifests\amd64_5f1280df3a4bb949039fc60bc2d4ada9_31bf3856ad364e35_6.1.7601.17578_none_5309bbfea6693aa7.manifest
 winsxs\manifests\amd64_netfx-mscorwks_dll_b03f5f7f11d50a3a_6.1.7601.21660_none_a8442f37f0ac7eac.manifest
 winsxs\manifests\amd64_97f3bdc71de4614f40adb69a3a54dd92_31bf3856ad364e35_6.1.7600.20826_none_58f3e4c6bf84ef50.manifest
 winsxs\manifests\x86_microsoft-windows-ie-extcompat_31bf3856ad364e35_9.4.8112.16441_none_5519aee8f0f08f71.manifest
 winsxs\manifests\amd64_50aa88ae6356e2e48df0ca6c1b530ffb_31bf3856ad364e35_6.1.7600.16748_none_a51f15b91a4679d6.manifest
 winsxs\manifests\amd64_d4a45643465c0ab9e3d0165e2fb87340_31bf3856ad364e35_6.1.7600.16695_none_9007e04fdce2ee2e.manifest
 winsxs\manifests\amd64_eb1b3c30d6ff6a141beaa20073335122_31bf3856ad364e35_6.1.7600.20826_none_4940c9a1e4c1a5b0.manifest
 winsxs\manifests\amd64_8b41c6355286c58628d9f154fd393b7f_31bf3856ad364e35_6.1.7600.20923_none_2810cc14965fd5f7.manifest
 winsxs\manifests\amd64_fbc3d1116bf4f04b54afe28d79392193_31bf3856ad364e35_6.1.7600.20826_none_e0371cfd3d407a8e.manifest
 winsxs\manifests\amd64_f12193eb83447cb197449568ffee709f_31bf3856ad364e35_6.1.7600.16695_none_589b074fb67ee19b.manifest
 winsxs\manifests\amd64_9e125dd21e70d8a1f8575312da37d4fc_31bf3856ad364e35_6.1.7600.16695_none_cc5621e37452d0d6.manifest
 winsxs\manifests\amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7600.16695_en-us_df5f79779b7f9fad.manifest
 winsxs\manifests\amd64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7600.16695_none_71317de3234b2af0.manifest
 winsxs\manifests\amd64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7600.20826_none_7207cc523c2f1da1.manifest
 winsxs\manifests\amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7600.20826_en-us_e035c7e6b463925e.manifest
 servicing\packages\Microsoft-Windows-Security-WindowsActivationTechnologies-Package~31bf3856ad364e35~amd64~~7.1.7600.16395.mum
 servicing\packages\Package_1_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_2_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_37_for_KB2443685~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_57_for_KB2443685~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_5_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_73_for_KB2443685~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2443685_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2443685~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Microsoft-Windows-Security-WindowsActivationTechnologies-Package~31bf3856ad364e35~amd64~~7.1.7600.16395.cat
 servicing\packages\Package_1_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_2_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_37_for_KB2443685~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_57_for_KB2443685~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_5_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_73_for_KB2443685~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2443685_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2443685~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat

Code:

 Line 3850: 2013-03-25 18:39:23, Info                  CSI    000003bb [SR] Beginning Verify and Repair transaction
 Line 3855: 2013-03-25 18:39:23, Info                  CSI    000003be [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)
 Line 3858: 2013-03-25 18:39:23, Info                  CSI    000003c0 [SR] Cannot repair member file [l:22{11}]"amdsata.sys" of amdsata.inf, Version = 6.1.7601.17577, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3861: 2013-03-25 18:39:23, Info                  CSI    000003c2 [SR] Cannot repair member file [l:26{13}]"CPFilters.dll" of Microsoft-Windows-CPFilters, Version = 6.1.7601.17528, 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
 Line 3864: 2013-03-25 18:39:23, Info                  CSI    000003c4 [SR] Cannot repair member file [l:22{11}]"mpg2splt.ax" of Microsoft-Windows-DirectShow-MPEG2, Version = 6.1.7601.17528, 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
 Line 3867: 2013-03-25 18:39:23, Info                  CSI    000003c6 [SR] Cannot repair member file [l:24{12}]"adojavas.inc" of Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-ADO15-JVS, Version = 6.1.7600.16385, 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
 Line 3870: 2013-03-25 18:39:23, Info                  CSI    000003c8 [SR] Cannot repair member file [l:22{11}]"Ribbons.scr" of Microsoft-Windows-Ribbons, Version = 6.1.7601.17514, 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
 Line 3873: 2013-03-25 18:39:24, Info                  CSI    000003ca [SR] Cannot repair member file [l:20{10}]"PkgMgr.exe" 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
 Line 3876: 2013-03-25 18:39:24, Info                  CSI    000003cc [SR] Cannot repair member file [l:30{15}]"HashCleanup.exe" of Microsoft-Windows-TASK-SCHED-HashCleanup-GC, Version = 6.1.7600.16699, 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
 Line 3879: 2013-03-25 18:39:24, Info                  CSI    000003ce [SR] Cannot repair member file [l:22{11}]"wimgapi.dll" of Microsoft-Windows-Wimgapi, Version = 6.1.7600.16385, 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
 Line 3882: 2013-03-25 18:39:24, Info                  CSI    000003d0 [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
 Line 3885: 2013-03-25 18:39:24, Info                  CSI    000003d2 [SR] Cannot repair member file [l:20{10}]"nvstor.sys" of nvraid.inf, Version = 6.1.7601.17577, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3888: 2013-03-25 18:39:24, Info                  CSI    000003d4 [SR] Cannot repair member file [l:20{10}]"nvraid.sys" of nvraid.inf, Version = 6.1.7601.17577, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3892: 2013-03-25 18:39:24, Info                  CSI    000003d6 [SR] Cannot repair member file [l:74{37}]"System.EnterpriseServices.Wrapper.dll" of System.EnterpriseServices, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3895: 2013-03-25 18:39:25, Info                  CSI    000003d8 [SR] Cannot repair member file [l:24{12}]"explorer.exe" of Microsoft-Windows-explorer, Version = 6.1.7601.17567, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3898: 2013-03-25 18:39:25, Info                  CSI    000003da [SR] Cannot repair member file [l:14{7}]"sbe.dll" of Microsoft-Windows-StreamBufferEngine, Version = 6.1.7601.17528, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3901: 2013-03-25 18:39:25, Info                  CSI    000003dc [SR] Cannot repair member file [l:26{13}]"CPFilters.dll" of Microsoft-Windows-CPFilters, Version = 6.1.7601.17528, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3904: 2013-03-25 18:39:25, Info                  CSI    000003de [SR] Cannot repair member file [l:22{11}]"mpg2splt.ax" of Microsoft-Windows-DirectShow-MPEG2, Version = 6.1.7601.17528, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3907: 2013-03-25 18:39:25, Info                  CSI    000003e0 [SR] Cannot repair member file [l:24{12}]"msador15.dll" of Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-ADO15-R, Version = 6.1.7601.17857, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3910: 2013-03-25 18:39:25, Info                  CSI    000003e2 [SR] Cannot repair member file [l:22{11}]"Mystify.scr" of Microsoft-Windows-Mystify, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3913: 2013-03-25 18:39:25, Info                  CSI    000003e4 [SR] Cannot repair member file [l:24{12}]"nshipsec.dll" of Microsoft-Windows-Network-Security-Domain-Clients-Netsh, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3916: 2013-03-25 18:39:25, Info                  CSI    000003e6 [SR] Cannot repair member file [l:22{11}]"Ribbons.scr" of Microsoft-Windows-Ribbons, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

I think we need to check your hard drive first.

Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.

At the Command prompt, type

CHKDSK C: /R

and hit the Enter key.
You will be told that the drive is locked,
and the CHKDSK will run at he next boot - hit the Y key, press Enter, and then reboot.

The CHKDSK will take a few hours depending on the size of the drive, so be patient!

After the CHKDSK has run, Windows should boot normally (possibly after a second auto-reboot) -

Please open Event Viewer
In the left pane, navigate to the Windows Logs
right-click on Applications and select 'Save all events as...' save as Apps.evtx

Compress the file, and attach to your reply.

PhilM99 · Mar 26, 2013

I did as asked, the CHKDSK did run, only thing is it said rather immediately that the hard drive is 'clean'. Then it went to a normal boot.
Attaching the events log as asked. Thanks

NoelDP · Mar 26, 2013

You have a heck of a lot of 'warnings' from products like MSSQL, SQLLISService100, and .NET 4
more seriously, you have a lot of Crypto errors in CAPI2

Please follow the instructions here Event ID 513 and post your results.

PhilM99 · Mar 26, 2013

Followed the instructions (even though it said applies to Server 2008, same base for Win7?)
No changes to permissions were required.
Ran the vssadmin list writers: System Writer was not listed, so perhaps there's a problem there.
(Ensure that Writer Name: 'System Writer' is displayed in the list.)

PhilM99 · Mar 26, 2013

Sorry to proceed without your instructions, but I decided I wanted to know why chkdsk did not run so I ran it again. It's still running (I'm on another computer)..want me to post the events log again when done? (Hundreds of clusters being repaired, hope it boots)

NoelDP · Mar 26, 2013

That sounds like what I would have advised anyhow - carry on

Once the scan is complete, run SFC /SCANNOW again, and post the new CBS.log.

PhilM99 · Mar 26, 2013

This is looking pretty bad. I mean the machine runs fine for everything except this latest update. The chdsk reported dozens, maybe hundreds of clusters it had to fix. So After finishing that I tried the windows update again, same failure.
So I ran the SUR check again. I have attached the CBSlog files as CBS1.rar.
This probably all happened when I was updating the machine a few months ago and the power failed briefly.
I'm thinking of rebuilding it. I originally built it from an OEM copy of Windows 7 I bought at Best Buy (the machine had XP on it, no reasonable upgrade path). Do you think I can somehow repair the files that are messed up using the OEM DVD somehow?
It's a real pain to use the OEM copy to build from, if I recall correctly I had to create a bootable USB stick, not sure I can do it all again. Maybe now that 7 is on this machine, there's an easier way.
Ideas? Thanks for yourhelp Phil
PS In your intro it says
Before starting a new thread please read and follow the instuctions bellow. (Couple of spelling errors, just in case you have a template that needs fixing

)

NoelDP · Mar 27, 2013

The CheckSUR doesn't seen too bad - at least the registry isn't affected.
The SFC results don't appear to have changed, either
I'll work up a fix protocol (two actually) and post it later today.

NoelDP · Mar 27, 2013

...while I'm getting the stuff together, please post your Application Events log.....

Please open Event Viewer
In the left pane, navigate to the Windows Logs
right-click on Applications and select 'Save all events as...' save as Apps.evtx

Compress it and attach to your reply.

NoelDP · Mar 27, 2013

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.

NoelDP · Mar 27, 2013

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

PhilM99 · Mar 27, 2013

Atttached is the apps.rar. BTW I like your forum, is it a commercial product or your own?

NoelDP · Mar 27, 2013

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\SYSTEMRX)"
icacls %windir%\winsxs\filemaps\*.* /grant "NT Service\trustedinstallerF)"
icacls %windir%\winsxs\filemaps\*.* /grant "BUILTIN\UsersRX)"

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

PhilM99 · Mar 27, 2013

The System Writer still does not show up (I have not yet applied the two part fix above).
However, I ran the permissions changes successfuly, and also noted that the Volume Shadow Copy Service was set to manual and thus was not started. Fixed that, booted, still no 'System Writer'.
Going back to the two part fix now.

PhilM99 · Mar 27, 2013

OK, here's part 1, the checksur logs. Moving on to part deux

PhilM99 · Mar 27, 2013

here's the second part

NoelDP · Mar 27, 2013

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

PhilM99 · Mar 27, 2013

I ONLY ran the SFC. I'm confused. How do I run the CheckSUR? I notice that the CBS log was new but the other two logs have not been updated.

NoelDP · Mar 27, 2013

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

Error 9C59 While trying to install IE10 on Win7

New member

My Computer My Computer

At a glance

Three-Toed Sloth

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Three-Toed Sloth

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Three-Toed Sloth

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Three-Toed Sloth

My Computer My Computer

At a glance

Three-Toed Sloth

My Computer My Computer

At a glance

Three-Toed Sloth

My Computer My Computer

At a glance

Three-Toed Sloth

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Three-Toed Sloth

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Three-Toed Sloth

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Three-Toed Sloth

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer