Two security updates fail: KB293135 (800736B3) & KB2926765 (8007000D)

CheckSUR fixed a number of problems - but was also unable to fix a few.
Here's the failure list...

Code:

Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7601.18429_none_ca494925289f2f1e.manifest
 winsxs\manifests\wow64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7601.18429_none_d49df3775cfff119.manifest
 winsxs\manifests\amd64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7601.22639_none_cac817ea41c4e800.manifest
 winsxs\manifests\wow64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7601.22639_none_d51cc23c7625a9fb.manifest
 servicing\packages\Package_2_for_KB2926765~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_2_for_KB2926765~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2926765_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2926765_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2926765~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2926765~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_2_for_KB2926765~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_2_for_KB2926765~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2926765_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2926765_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2926765~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2926765~31bf3856ad364e35~amd64~~6.1.1.1.cat

I'll post a fix for them a little later - gotta eat soon!

I've uploaded a file - hcsaa.zip - to my OneDrive at Noel's OneDrive
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 hcsaa 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.

Good - the CheckSUR log is now clear.

Please run SFC /SCANNOW again, and post the new CBS.log file - it may have found new errors, now that the manifest errors have been corrected.

The SFC scan shows the following problems...

Code:

Line 15728: 2014-06-02 06:28:20, Info                  CSI    00000323 [SR] Repairing 5 components
 Line 15729: 2014-06-02 06:28:20, Info                  CSI    00000324 [SR] Beginning Verify and Repair transaction
 Line 15732: 2014-06-02 06:28:20, Info                  CSI    00000326 [SR] Cannot repair member file [l:18{9}]"Chess.dll" of Microsoft-Windows-Shell-PremiumInboxGames-Chess, 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 15735: 2014-06-02 06:28:20, Info                  CSI    00000328 [SR] Cannot repair member file [l:22{11}]"Mahjong.dll" of Microsoft-Windows-Shell-PremiumInboxGames-Shanghai, 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 15738: 2014-06-02 06:28:20, Info                  CSI    0000032a [SR] Cannot repair member file [l:16{8}]"boot.sdi" of Microsoft-Windows-WinRE-RecoveryTools, 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 15741: 2014-06-02 06:28:20, Info                  CSI    0000032c [SR] Cannot repair member file [l:20{10}]"SA4x28.icc" of wiasa002.inf, Version = 6.1.7600.16385, 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

I find it a little strange that there are 5 affected components - but only 4 discovered file problems. Usually, I'd expect it to be the other way around.

Back a little later with a fix protocol.

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

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

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

Great - that's fixed the SFC scan problems.

Now try installing the updates again- after doing a manual Check for Updates.