Persistent Windows Update error - 80073712

ivorytickler664 · 14 Oct 2014

Hi,

I noticed the other day that my Windows 7 Professional PC had not had any Windows Updates since the end of August, so became curious as to why. On checking Windows Update, it came up with the error code above, and would not install any updates.

I checked the installed updates and there was one relating to Windows Defender KB915597, but I have since been able to download a more recent one from Defender itself after I disabled AVG.

I have perused the web at length to try to resolve this but still no luck, I have tried:-

1. Re-setting the Windows Update components
2. Running Windows6.1-KB947821-v33-x64.msu
3. sfc /scannow
4. chkdsk /f /r
5. Updating Windows from my MESH CD but it kept saying it could not install a newer Windows version
6. I then followed some steps running DSIM.exe from the CMD window

I have done as requested in your posting instructions and enclose my CBS.zip file. I also added my Belarc Advisor html file, and a Word document with screenshots in, in case they helps. I have had to remove the CbsPersist_xxx.cab files to get the zip file below 8Mb in size, but please let me know if you want me to send them separately.

I must advise that I have run some Registry Cleaners on this PC, and whilst investigating this issue, it seems the general consensus is not to use these. So I won't be anymore!

Look forward to hearing from someone, and thank you in advance for your help.

Cheers

Tim

matts6887 · 14 Oct 2014

try the following link and see if it helps ya out any:

Windows Update fails with error code 80073712 - Microsoft Community

NoelDP · 15 Oct 2014

It looks to me as if you've been using some kind of third-party System Cleanup tool, and possibly a registry cleaner. - which ones?

Here's the update errors from the CheckSUR log...

Code:

Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-windowsupdate-adm_31bf3856ad364e35_7.6.7600.256_none_9286cad7bab620de.manifest
 winsxs\manifests\x86_microsoft-windows-t..dpsounddriver-winip_31bf3856ad364e35_7.1.7601.16398_none_f03c847a65ccfe17.manifest
 winsxs\manifests\x86_microsoft-windows-t..ices-msrdpwebaccess_31bf3856ad364e35_7.1.7601.16398_none_7aafdf4834f5859a.manifest
 winsxs\manifests\x86_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_7.1.7601.16398_none_231382b1af0e294c.manifest
 winsxs\manifests\wow64_microsoft-windows-t..minalservicesclient_31bf3856ad364e35_7.1.7601.16398_none_a7750e5ff73bb5fe.manifest
 winsxs\manifests\x86_microsoft-windows-t..cesclient.resources_31bf3856ad364e35_7.1.7601.16398_en-us_67c32fac578450fe.manifest
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
 servicing\packages\Package_4_for_KB2931356~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat
 servicing\packages\Package_4_for_KB2931356~31bf3856ad364e35~amd64~~6.1.1.0.cat

... but you also have a number of missing file problems which will need to be addressed once we have these fixed.

I'll post a fix protocol later.

ivorytickler664 · 15 Oct 2014

Yes you are right Noel

I've done this on my previous XP PC and had minimal problems, but Win 7 64 bit is different, so I will stop using them now. I've used Eusing Registry Cleaner (which seemed the most stable) and Wise Care 365. I also use CCleaner, Malwarebytes and Superantispyware but I assume it is ok to continue using these as they're not registry cleaners?

Matt - I did start looking at that thread but I am running the latest Win Update Agent and I've tried sfc /scannow and chkdsk. Tbh I didn't want to try the other random suggestions the poster made.

Cheers - look forward to getting this fix!

Tim

For what it's worth, I enclose the Word doc with the series of messages I got, that I forgot to attach before

soph200310 · 15 Oct 2014

I'm having the same problem! so annoying!

NoelDP · 15 Oct 2014

...so start your own thread and post your own data! !!

ivorytickler664 · 18 Oct 2014

Noel - I know you're probably dead busy, but have you had a chance to do me a fix protocol yet?

Cheers

Tim

NoelDP · 19 Oct 2014

Sorry about that - you fell off my todo list

Back soon...

NoelDP · 19 Oct 2014

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

ivorytickler664 · 21 Oct 2014

Hi Noel

Thanks for that. Before I run the CheckSUR again though, my folder structure is slightly different, ie I have an MSU folder (see attached)

I have a servicing\Packages folder under it as you can see (and have pasted your Packages files there), but I did not have the Winsxs folder, so I have created it (and the Manifests sub-folder) and pasted the Manifest files therein.

Am I ok to continue with the CheckSUR?

Tim