Windows Update error Code 80073712

[souldout]

Hi Guys,

I've recently been having this update error code which i cant find out how to fix.
i have already run the sfc /scannow that has said nothing that has been disturbed, and also installed system update readiness tool for x64 "Windows6.1-KB947821-v34-x64.msu" was the file not sure if there are other versions, but after doing those it hasnt helped so i thought someone would know how to fix this.

i have attached my logs if they are required.

thanks in advance

 

[NoelDP]

You have these problems showing in the CheckSUR scan...

Summary:
Seconds executed: 340
 Found 127 errors
  CSI Manifest Failed Catalog Check Total count: 1
  CSI Payload File Missing Total count: 116
  CBS MUM Corrupt Total count: 10

Unavailable repair files:
	winsxs\manifests\x86_microsoft-windows-ie-ieproxy_31bf3856ad364e35_11.2.9600.17914_none_1630a909a76a65d6.manifest
	servicing\packages\Package_104_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_105_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_106_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_107_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_108_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_51_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_52_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_54_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_79_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
	servicing\packages\Package_for_KB3072630_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
	servicing\packages\Package_104_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.cat
	servicing\packages\Package_105_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.cat
	servicing\packages\Package_106_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.cat
	servicing\packages\Package_107_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.cat
	servicing\packages\Package_108_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.cat
	servicing\packages\Package_51_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.cat
	servicing\packages\Package_52_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.cat
	servicing\packages\Package_54_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.cat
	servicing\packages\Package_79_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.cat
	servicing\packages\Package_for_KB3072630_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat

I'll post a fix protocol later.

 

[NoelDP]

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

 

[souldout]

Thanks NoelDP, I'm giving this a try now and will update you shortly

Update...

New log files attached

 

[NoelDP]

I missed one

Unavailable repair files:
	servicing\packages\Package_for_KB3072630_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
	servicing\packages\Package_for_KB3072630_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat

I'll post another fix protocol later for that.

I'm not happy about the number of missing payload files that have popped up, though

Summary:
Seconds executed: 392
 Found 128 errors
 Fixed 10 errors
  CSI Manifest Failed Catalog Check Total count: 1
  Fixed: CSI Manifest Failed Catalog Check.  Total count: 1
  CSI Payload File Missing Total count: 117
  CBS MUM Corrupt Total count: 10
  Fixed: CBS MUM Corrupt.  Total count: 9
  Fixed: CBS Paired File.  Total count: 9

 

[souldout]

Oh i see, what causes all these missing payload files?
i noticed i had heaps...

thanks for your help so far though i greatly appreciate it

 

[NoelDP]

It's probably because this update barfed early in the install phase, and all the temporary files were deleted before they were placed in the proper place - this didn't show until the accompanying control control files (mum/cat/manifest) were in place.

With luck it won't cause too many problems. - back later.

 

[NoelDP]

I've uploaded a file - sdtab.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 sdtab in the same place.
Open this folder - there should be one folders inside it ( Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

 

[NoelDP]

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

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

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

 

[souldout]

Hey Noel,

did you want me to do post # 8 then #9?
or just do #9? i see you have posted up 2 files.

thanks!

 

[NoelDP]

You need to do both - it may be better to do #9 before #8, as that'll confirm the substitutions made better.

 

[souldout]

Hi Noel,

I've done step 9 finally and have attached the CBS log to this reply, ill continue to do step 8 now.
i made a copy and compressed it as it had a fit when i attached it without compressing.

thanks!

 

[souldout]

Hi again,

Step 8, now completed with both logs uploaded.

thanks!!!