Solved KB3068708 update fails w/ error 80073712

[sdog]

Greetings,

Windows updates started failing about the time Microsoft started announcing that W10 was coming out and should be reserved (I've not updated to W10, still on 7).

Have run sfc and SURT multiple times. Studying the logs and using this site has allowed me to get all updates working again but one. Can't figure this one out. Anyone have any ideas?

KB3068708 update fails w/ error 80073712

I'd attach the CBS log, but even zipped, it's 253M, well over the 8M limit for this site's uploads.

 

[sdog]

I realize it's probably hard to help me without the logs, but I'm not sure how to reconcile the posting instructions (zip the whole CBS folder) with the maximum upload restrictions (8MB).

I figure I'll take a chance and at least upload the (small) checkSUR log. Hope this isn't too far off the forum rules. I'm also willing to upload any other stuff in bits and pieces or just put the whole thing up on line somewhere for your download if anyone is willing to jump in.

Looks like there are about 45 "missing repair files", (all manifests). I've tried a few of the various techniques from this site to trace what packages these are in, including the registry trace, but have come up empty handed.

Does anyone recognize any of these manifest files and know what packages they might come from?

 

[wben353]

checked my win7 disk E:\sources\install.wim\3\Windows\winsxs\Manifests\ none of the files you are missing are on the disk. NoelDP is the person able to assist you. Might have to wait till Monday, be patient, he helps many people and will get back to you. If you know someone with win7x64 pro they will have the files on their computer. You could get them from there.
How to fix errors found in the checkSUR.log click here. Good luck I'll follow your future posts. I'm sure you will get the issue fixed. The KB that you can't install is optional (telemetry-spyware) I hid that update and several others that track you. Google Microsoft spying in windows 7. I did the fix myself following the instruction on the page I provided the link to.

 

[sdog]

Thanks for the help wben353. And thanks for looking at the original disk.

I had seen that howto for checkSUR errors and even several others but no matter the path I followed, I could not figure out which packages contained those manifests. I used to have another W7 machine, but got in a little bit of hurry upgrading it to W10. If I understand the W10 upgrade correctly, the W7 files are still on there somewhere so the system could be rolled back to W7, but I haven't had a chance to hunt them down yet.

It's good to know that that particular patch is not entirely necessary. I'll wait patiently for Noel, and if I'm unable to resolve this thing after a while, I may simply do what you did and hide it and move on. I'm about done with microsoft and google and amazon and every other software company out there trying to figure out what color underwear I'm wearing. Nobody needs to know!

Although it always drives me nuts to leave things vaguely broken instead of fixing them.

Thanks again!

 

[NoelDP]

Here's the error list...

Summary:
Seconds executed: 469
 Found 45 errors
  CSI Manifest All Zeros Total count: 45

Unavailable repair files:
	winsxs\manifests\amd64_microsoft-windows-c..integrity.resources_31bf3856ad364e35_6.1.7601.23072_en-us_57a109cb7d4a6a08.manifest
	winsxs\manifests\amd64_microsoft-windows-appid_31bf3856ad364e35_6.1.7601.23072_none_b5b89975e2172f61.manifest
	winsxs\manifests\amd64_microsoft-windows-p..ncetoolscommandline_31bf3856ad364e35_6.1.7601.23072_none_bf9003fb2ec501b3.manifest
	winsxs\manifests\amd64_microsoft-windows-advapi32.resources_31bf3856ad364e35_6.1.7601.18869_en-us_767e5e62c7989556.manifest
	winsxs\manifests\amd64_microsoft-windows-msauditevtlog_31bf3856ad364e35_6.1.7601.23072_none_25af0378a85d5817.manifest
	winsxs\manifests\amd64_microsoft-windows-sechost_31bf3856ad364e35_6.1.7601.18869_none_e5b7c30ce3b9dc7e.manifest
	winsxs\manifests\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad.manifest
	winsxs\manifests\amd64_microsoft-windows-systemrestore-main_31bf3856ad364e35_6.1.7601.23072_none_a54c5911e32ee184.manifest
	winsxs\manifests\amd64_microsoft-windows-sechost_31bf3856ad364e35_6.1.7601.23072_none_e62f6607fce61a1a.manifest
	winsxs\manifests\amd64_microsoft-windows-b..os-loader.resources_31bf3856ad364e35_6.1.7601.23072_en-us_d505433013f3b9ce.manifest
	winsxs\manifests\amd64_microsoft-windows-b..t-windows.resources_31bf3856ad364e35_6.1.7601.23072_en-us_7ae981de60192db1.manifest
	winsxs\manifests\amd64_microsoft-windows-p..ncetoolscommandline_31bf3856ad364e35_6.1.7601.18869_none_bf1861001598c417.manifest
	winsxs\manifests\amd64_microsoft-windows-tracedatahelper_31bf3856ad364e35_6.1.7601.23072_none_5acf598d021e2b1e.manifest
	winsxs\manifests\amd64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.23072_none_c6925134073f1524.manifest
	winsxs\manifests\amd64_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.23072_none_bc4adebc218bf1fe.manifest
	winsxs\manifests\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7601.23072_none_b743676c2c1d8f71.manifest
	winsxs\manifests\amd64_microsoft-windows-smss_31bf3856ad364e35_6.1.7601.23072_none_0aa7312749218315.manifest
	winsxs\manifests\amd64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.23072_none_db1f75fd927aa673.manifest
	winsxs\manifests\amd64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.23072_none_9939d441aca4f724.manifest
	winsxs\manifests\amd64_microsoft-windows-advapi32_31bf3856ad364e35_6.1.7601.23072_none_41b4dad4b6719c0b.manifest
	winsxs\manifests\amd64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.23072_none_14eb1fcccc451906.manifest
	winsxs\manifests\amd64_microsoft-windows-security-credssp_31bf3856ad364e35_6.1.7601.23072_none_2224ba99d17fe82c.manifest
	winsxs\manifests\amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.23072_none_45436655e0bd7353.manifest
	winsxs\manifests\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.23072_none_ca9ceacae412f5c3.manifest
	winsxs\manifests\amd64_microsoft-windows-advapi32.resources_31bf3856ad364e35_6.1.7601.23072_en-us_76f6015de0c4d2f2.manifest
	winsxs\manifests\amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.23072_none_8082d4388532ba1c.manifest
	winsxs\manifests\amd64_microsoft-windows-c..ityclient.resources_31bf3856ad364e35_6.1.7601.23072_en-us_c32be014cfc49c8e.manifest
	winsxs\manifests\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.23072_none_fe5f78f236dc8149.manifest
	winsxs\manifests\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_6.1.7601.23072_none_b993435c9c96c3a3.manifest
	winsxs\manifests\amd64_microsoft-windows-b..environment-windows_31bf3856ad364e35_6.1.7601.23072_none_c7a52054bcba8174.manifest
	winsxs\manifests\amd64_microsoft-windows-msauditevtlog_31bf3856ad364e35_6.1.7601.18869_none_2537607d8f311a7b.manifest
	winsxs\manifests\amd64_microsoft-windows-systemrestore-main_31bf3856ad364e35_6.1.7601.18869_none_a4d4b616ca02a3e8.manifest
	winsxs\manifests\amd64_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.18869_none_bbd33bc1085fb462.manifest
	winsxs\manifests\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7601.18869_none_b6cbc47112f151d5.manifest
	winsxs\manifests\amd64_microsoft-windows-smss_31bf3856ad364e35_6.1.7601.18869_none_0a2f8e2c2ff54579.manifest
	winsxs\manifests\amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.18869_none_800b313d6c067c80.manifest
	winsxs\manifests\amd64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.18869_none_daa7d302794e68d7.manifest
	winsxs\manifests\amd64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.18869_none_98c231469378b988.manifest
	winsxs\manifests\amd64_microsoft-windows-advapi32_31bf3856ad364e35_6.1.7601.18869_none_413d37d99d455e6f.manifest
	winsxs\manifests\amd64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.18869_none_14737cd1b318db6a.manifest
	winsxs\manifests\amd64_microsoft-windows-security-credssp_31bf3856ad364e35_6.1.7601.18869_none_21ad179eb853aa90.manifest
	winsxs\manifests\amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.18869_none_44cbc35ac79135b7.manifest
	winsxs\manifests\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.18869_none_ca2547cfcae6b827.manifest
	winsxs\manifests\amd64_microsoft-windows-tracedatahelper_31bf3856ad364e35_6.1.7601.18869_none_5a57b691e8f1ed82.manifest
	winsxs\manifests\amd64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.18869_none_c61aae38ee12d788.manifest

I'll post a fix protocol a little later.

 

[NoelDP]

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

Copy 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.

 

[sdog]

Noel,

THANK YOU!!! You are the best!!!!

First run of SURT showed errors were fixed. Update ran successfully. Second run of SURT (just to be sure) showed no errors.

I wouldn't even want to admit how long I spent trying to hunt down those manifest files. I should have asked for help sooner.

One more question: Is it safe at this point to delete the files in C:\Windows\Temp\CheckSUR ?

 

[NoelDP]

Yep - they anre now safely tucked away where they should be, so the TEMP files can be deleted.

 

[sdog]

Excellent. Thanks Noel!

 

[NoelDP]

You're welcome - good luck!

 

[wben353]

You rock Noel