Windows update failure - error code 80073712

Here's the summary from your CheckSUR.log file...

Code:

Summary:
Seconds executed: 889
 Found 146 errors
  CSI Payload File Missing Total count: 146

This tome indicates that something serious interfered at the crucial time of an update install where the files were being relocated after a reboot - especially as SFC appears to find nothing amiss.

I'll post a fix protocol for the above errors later - but I wouldn't hold out too much hope of its being effective.

I've uploaded a file - hplaa.zip - to my OneDrive at Noel'sOneDrive

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:\hplaa

hit the enter key- if you get a 'Not Found' error try

DIR D:\hplaa

or

DIR E:\hplaa

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


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

SFC is clear - apart from these 'false' errors.

Code:

 Line 7385: 2015-07-11 12:12:25, Info                  CSI    00000366 [SR] Repairing 1 components
 Line 7386: 2015-07-11 12:12:25, Info                  CSI    00000367 [SR] Beginning Verify and Repair transaction
 Line 7389: 2015-07-11 12:12:25, Info                  CSI    00000369 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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 7392: 2015-07-11 12:12:25, Info                  CSI    0000036b [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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

Please run CheckSUR again, and post the new CheckSUR.log file.

Still one left to do...

Code:

Checking Component Store
(f) CSI Payload File Missing 0x00000000 win32k.sys amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.23072_none_176002e4ca76ad1b

I'll post the fix protocol for that one soon.

I've uploaded a file - hplab.zip - to my OneDrive at Noel'sOneDrive

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:\hplab

hit the enter key- if you get a 'Not Found' error try

DIR D:\hplab

or

DIR E:\hplab

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


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

:)
Nothing new has popped up - still just these 'errors' from KB3022345...

Code:

     CSI    00000366 [SR] Repairing 1 components
 Line 14768: 2015-07-11 16:39:48, Info                  CSI    00000367 [SR] Beginning Verify and Repair transaction
 Line 14771: 2015-07-11 16:39:48, Info                  CSI    00000369 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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 14774: 2015-07-11 16:39:48, Info                  CSI    0000036b [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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 14777: 2015-07-11 16:39:48, Info

Just to check, please run CheckSUR once more and post the log - it should be clear.

Then do a Check for Updates, and see what happens.