Security update failed, error code 80073712

I have been getting help from Arc over on the BSOD section of this forum site for a few weeks now. I figured I'd start a thread here about the update troubles I've been experiencing over the past few days as well. There is one update that won't apply no matter what I try. I've run the amalgamated .bat tool posted on this forum and that didn't solve my issue. I will let my logs and screenshots speak for themselves from here, though.

Thanks in advance for any help!

As stated in the title, error code is 80073712. Also, I can't seem to get my CBS logs to upload. I keep getting an internal server error about the resource not being available. The screenshot attached perfectly fine. I will try to either edit this post to add them or add them as a comment.

Attachment 298869

Still can't get the CBS.zip to upload. I will attach a screenshot of the error page. I'll try it again later.

Attachment 298870

The problem with the upload is probably because the filesize is too large - delete the older CBSPersist file(s) and try again.

The 80073712 error is often cured simply by installing the patch using the standalone update file. -

If you search Google using the format
kbxxxxxxx x64 download site:microsoft.com

the download should be somewhere near the top of the list.

download and save it (just in case we need it later), then double-click on it, and accept the UAC prompt to install the update -

What happens?

I am currently having severe issues with my RAM and/ or motherboard on my desktop. I am posting this from my laptop. Here are the CBS logs for someone to look over while I run memtest on my rig. Thanks in advance for any help!

Attachment 299030

The CheckSUR log shows the following problems...

Code:

Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-scripting_31bf3856ad364e35_6.1.7601.18283_none_a6418c4d17334828.manifest
 winsxs\manifests\wow64_microsoft-windows-scripting_31bf3856ad364e35_6.1.7601.18283_none_b096369f4b940a23.manifest
 winsxs\manifests\amd64_microsoft-windows-scripting_31bf3856ad364e35_6.1.7601.22480_none_a6c82a2030539914.manifest
 winsxs\manifests\wow64_microsoft-windows-scripting_31bf3856ad364e35_6.1.7601.22480_none_b11cd47264b45b0f.manifest
 servicing\packages\Package_2_for_KB2892074~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2892074~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2892074_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2892074_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2892074~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2892074~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2892074~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_2_for_KB2892074~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2892074_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2892074_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2892074~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2892074~31bf3856ad364e35~amd64~~6.1.1.0.cat

I'll post a fix protocol for that later...

The CBS log has errors in it relating to the above problems - but I don't see any evidence of an SFC scan having been run at any time since 23/12

That can wait until after we get the CheckSUR problems sorted though.

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

I will follow your instructions as soon as my desktop is operational again. I've downloaded the rbaaa file from your skydrive and have it on a flash drive. It may be several days or weeks before I can get the new parts ordered and installed on my system (it seems the root of my BSOD woes lies in either my RAM or my motherboard) In the meantime, thanks for your quick responses to this issue. I'm sure we can get this solved as soon as I get the computer on its feet again :P

The standalone installer couldn't install the security update. I extracted/ moved the files as instructed and ran checksur again. It ran into an error. 0x80246002.

Here are the latest CBS logs.

Attachment 299351

The CBS.log file we need has been archived into a CBSPersist file - which isn't present in the folder you uploaded?
Please check for the existence of a CBSPersist20131229xxxxxx.cab file, and upload that if you find it.

Please also run the CheckSUR tool again, and upload the new CheckSUR.log file