Windows Update Problems, 80073712 and 80070436

the SFC scan is clear - but I think that's beacause SFC didn't detect the errors in the first place.

From what you've written, it looks as if you omitted the spaces before the switches in the command..
You wrote
c:\windows\winsxs\y\i\s\v\h

The proper command is
XCOPY D:\vtcaa D:\windows\winsxs(space)/y(space)/i(space)/s(space)/v(space)/h

Good - SFC is happy, and the CheckSUR result is less confusing

Code:

Checking Component Store
(f) CSI Payload File Missing 0x00000000 XpsGdiConverter.dll x86_microsoft-windows-c..ent-xpsgdiconverter_31bf3856ad364e35_6.1.7601.17566_none_14bfd06d49b99ef7 
(f) CSI Payload File Missing 0x00000000 jscript.dll x86_microsoft-windows-scripting-jscript_31bf3856ad364e35_8.0.7601.17817_none_9fa4a049cc65ac0f 
(f) CSI Payload File Missing 0x00000000 XpsGdiConverter.dll x86_microsoft-windows-c..ent-xpsgdiconverter_31bf3856ad364e35_6.1.7600.20908_none_13a5f234657e5b04 
(f) CSI Payload File Missing 0x00000000 jscript.dll x86_microsoft-windows-scripting-jscript_31bf3856ad364e35_8.0.7600.21192_none_9dec3578e8a276dd 
(f) CSI Payload File Missing 0x00000000 XpsGdiConverter.dll x86_microsoft-windows-c..ent-xpsgdiconverter_31bf3856ad364e35_6.1.7601.21667_none_154a6d8262d65818 
(f) CSI Payload File Missing 0x00000000 XpsPrint.dll x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_6.1.7600.20875_none_ac0ded9c8bb45d36 
(f) CSI Payload File Missing 0x00000000 XpsPrint.dll x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_6.1.7601.17537_none_ad97ee1b6f9aec42 
(f) CSI Payload File Missing 0x00000000 XpsPrint.dll x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_6.1.7601.21636_none_ae208a9c88b972b5 
(f) CSI Payload File Missing 0x00000000 XpsGdiConverter.dll x86_microsoft-windows-c..ent-xpsgdiconverter_31bf3856ad364e35_6.1.7600.16766_none_12d973674c93330b 
(f) CSI Payload File Missing 0x00000000 jscript.dll x86_microsoft-windows-scripting-jscript_31bf3856ad364e35_8.0.7601.21969_none_9ffa2e0ce5aa0a3c 
(f) CSI Payload File Missing 0x00000000 XpsPrint.dll x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_6.1.7600.20830_none_ac342bda8b986ebf 
(f) CSI Payload File Missing 0x00000000 jscript.dll x86_microsoft-windows-scripting-jscript_31bf3856ad364e35_8.0.7600.17000_none_9dc1e765cf3da8ec

I'll post what I hope is a fix protocol for that this evening.

One more try - if this fails then we'll have to look in the registry for problems.

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



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



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

Interesting - the SFC shows that it found this error..

Code:

 Line 24819: 2014-10-24 02:48:38, Info                  CSI    00000046 [SR] Beginning Verify and Repair transaction
 Line 24822: 2014-10-24 02:48:40, Info                  CSI    00000048 [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.1.7600.20538, 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 24825: 2014-10-24 02:48:41, Info                  CSI    0000004a [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.1.7600.20538, 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 24826: 2014-10-24 02:48:41, Info                  CSI    0000004b [SR] This component was referenced by [l:146{73}]"Package_2_for_KB975778~31bf3856ad364e35~x86~~6.1.1.0.975778-2_neutral_LDR"
 Line 24831: 2014-10-24 02:48:41, Info                  CSI    0000004e [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\windows\System32"\[l:22{11}]"autochk.exe"; source file in store is also corrupted
 Line 24850: 2014-10-24 02:48:43, Info                  CSI    00000051 [SR] Verify complete

... but the summary at the end shows only this...

Code:

2014-10-24 03:03:47, Info                  CSI    000001d2 [SR] Repairing 1 components
2014-10-24 03:03:47, Info                  CSI    000001d3 [SR] Beginning Verify and Repair transaction
2014-10-24 03:03:47, Info                  CSI    000001d4 Repair results created:
POQ 89 starts:
 
POQ 89 ends.
2014-10-24 03:03:47, Info                  CSI    000001d5 [SR] Repair complete

CheckSUR is clear.

I'll post a fix for the errant file above later.

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



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



XCOPY <drive>:\vtcac <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!
If you right-click on the update in the listing, you can select 'Hide update' - this will prevent it bothering you until it is itself updated again.

The SFC scan is clear, so you should be good to go.