Windows Update error 80073712 (Solved)

[Ginrikuzuma]

A bit of a copy and paste but...

So I did what anyone else would do I did some searching on why computer wouldn't update and ended up doing a bunch of different things. I'm right now stuck unable to install an old update (Security Update for Windows 7 for x64-based systems (KB286402)) which is from 10/8/2013.

System Specs with the whole dxdiag file can be found here[1] -- http://pastebin.com/MBSVmPC4

Windows 7 64-bit Home Premium

    I tried running the built-in troubleshooter from Windows and it simply gave me the error code and told me some cryptographic services weren't registered. Killing the cryptographic service and trying to renaming catroot2 folder to something else before restarting the service did nothing.

    1) Resetting the Windows Update History did nothing, nor did 2) Resetting and re-registering Windows Update component, nor 3) doing 1 & 2 together.

    I ran SFC /scannow which mentioned corrupted files but was unable to fix them.

    I tried running running something called Dism (Deployment Image Servicing and Management tool) I was told to run: Dism /Online /Cleanup-Image /RestoreHealth That didn't do much due to lacking an argument however running /scanhealth instead of restorehealth also mentioned corrupt files.

Last two said bullets I tried in Safe Mode.

-------that's all the copy paste ----------
Eventually I ended up on reddit and I found that Windows Repair program, doing the optional scan from step 2 pointed to a bunch of packages.

I did noticed they were all AMD files, I transfered most of my stuff from my laptop (which had an AMD card) to my new rig (which has an NVIDIA 970 card) I'm assuming this is my problem but is it safe to delete those files?
I also have hundreds of AMD folders inside winsxs. I been told not to delete folders from those folders in case file become corrupted or compromised but would it matter with those AMD folders can I just delete them or is there a safe method I have to follow to remove these.

Anyways heres the log from the pre-scan.

Tweaking.com - Windows Repair - Pre-Scan
Computer: GINRIKUZUMA-PC (Windows 7 Home Premium 6.1.7601 Service Pack 1) (64-bit)
Started at (5/17/2015 3:55:58 PM)
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Scanning Windows Packages Files.
Started at (5/17/2015 3:55:58 PM)

These Files Are Possibly Corrupt (Bad Digital Signature): (Total: 8)
C:\Windows\servicing\Packages\Package_1_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat
C:\Windows\servicing\Packages\Package_3_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat
C:\Windows\servicing\Packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.cat
C:\Windows\servicing\Packages\Package_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.cat
C:\Windows\servicing\Packages\Package_1_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum
C:\Windows\servicing\Packages\Package_3_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum
C:\Windows\servicing\Packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum
C:\Windows\servicing\Packages\Package_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11.mum

Problems were found with the packages files, these files need to be replaced (These mainly only effect installing Windows Updates.)
The SFC (System File Checker) doesn't scan and replace some of these files, so you may need to replace them manually.
These files do not keep the repairs from working, you may still run the repairs in the program.

If you need help in replacing these files, post on the Forums at Tweaking.com for help.

Files Checked & Verified: 3,795

Done (5/17/2015 3:56:10 PM)
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Scanning Reparse Points.
Started at (5/17/2015 3:56:10 PM)

No problems were found with the Reparse Points.

Files & Folders Searched: 289,202
Reparse Points Found: 44

Done (5/17/2015 3:56:20 PM)
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Checking Environment Variables.
Started at (5/17/2015 3:56:20 PM)

No problems were found with the Environment Variables.

Done (5/17/2015 3:56:20 PM)
--------------------------------------------------------------------------------

Done (5/17/2015 3:56:20 PM)
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Done (5/17/2015 3:56:20 PM)
Scan Complete - Problems Found!

You can use the Repair Reparse Points or Repair Environment Variables tools at the bottom of this Window if needed.

While problems have been found, you can still run the repairs in the program.
But for the best results it is recommended to fix the problems reported in this scan if possible.
If you need help fixing any of the items in the log, just post in the forums at Tweaking.com for help.

[jraju]

Hi, I would recommend windows system readiness tool, a free tool by msoft to fix the pending update problems. I found it fixed most of the problems in updating and fixes it. It is easy to run and safe also. You could try it. I do not know whether this tool supports windows Home premium version. If it is supporting, then you could try it.

[Shane]

I cant find anything for KB286402, can you double check that is the correct KB number for that update?

The error you are getting means

When you try to install updates from Windows Update or Microsoft Update, you may receive error 0x80073712, and the update does not install.

This issue may occur if the Component-Based Servicing (CBS) manifest is corrupted.

You do have some corrupt files in the packages folder that if we replace may fix the problem, the system readiness tool from MS may fix the problem as well.

The update is failing because one of the files from a previous update is corrupt so that update simply errors out and wont install. We replace the files that are corrupt and the update should install.

Here is the system readiness tool if you havent ran it yet
https://www.microsoft.com/en-us/download/details.aspx?id=20858

Shane

[Boggin]

Yes, it should have 7 digits.

The nearest one to that on my Win 7 is KB2864202 dated 9/10/2013 (UK dating dd/mth/yy).

[Ginrikuzuma]

I got busy so I couldn't reply sooner. Here is a screenshot of the KB number in the attachments but yeah I should have typed it correctly.

I thought I ran the Readiness Tool the day before yesterday but I'm seeing nothing, downloading it today again; Will edit this post after I finish with that unless someone posts before I finish.

Edit 1: I just noticed I typed KB286402 I meant KB2864202 my bad anyways I'll update again soon.

Edit 2: So I had the Readiness Tool run it threw in the hotfix but yeah I still can't update.

[Shane]

OK looking up others with a problem with that update (Has to do with USB drivers) some had it fail because their temp folder was on a ram disk, I also found that it is an update to KB2685811, sometimes removing that update will help.

The problem has been fixed. Both KB2864202 and KB2685811 have been succesfully installed. The problem was ASRocks RAM Disk which changes Window's TEMP  location from C drive to RAM disk. Changing the location in Environmental Variables did not work, upon reboot ASRock RAM Disk changed it back.  I stopped the RAM disk and uninstalled the ASRock Software. I also had a problem with AVG 2014 requesting reboot evertime I opened the interface. That problem was also caused by the ASRock RAM Disk. I reinstalled and  that problem is also fixed.

http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/cannont-install-kb2864202/8e4cd4b3-05cc-44c5-b55f-39ef164a3fdb

Since this update wasnt important another user simply right clicked on the update and hid it, after that other updates started showing up again as well.

You can also download the update yourself and then try to install it in safe mode to make sure nothing is getting in the way.
http://download.windowsupdate.com/d/msdownload/update/software/secu/2013/07/windows6.1-kb2864202-x64_92617ad813adf4795cd694d828558271086f4f70.msu

Shane

[Ginrikuzuma]

OK looking up others with a problem with that update (Has to do with USB drivers) some had it fail because their temp folder was on a ram disk, I also found that it is an update to KB2685811, sometimes removing that update will help.

The problem has been fixed. Both KB2864202 and KB2685811 have been succesfully installed. The problem was ASRocks RAM Disk which changes Window's TEMP  location from C drive to RAM disk. Changing the location in Environmental Variables did not work, upon reboot ASRock RAM Disk changed it back.  I stopped the RAM disk and uninstalled the ASRock Software. I also had a problem with AVG 2014 requesting reboot evertime I opened the interface. That problem was also caused by the ASRock RAM Disk. I reinstalled and  that problem is also fixed.

http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/cannont-install-kb2864202/8e4cd4b3-05cc-44c5-b55f-39ef164a3fdb

Since this update wasnt important another user simply right clicked on the update and hid it, after that other updates started showing up again as well.

You can also download the update yourself and then try to install it in safe mode to make sure nothing is getting in the way.
http://download.windowsupdate.com/d/msdownload/update/software/secu/2013/07/windows6.1-kb2864202-x64_92617ad813adf4795cd694d828558271086f4f70.msu

Shane

Downloaded and saved the msu file however I'm not allowed run it in safe mode apparently.
None of my gear is ASRock, my motherboard is Asus but I still decided to make sure and yes my TEMP file is where its suppose to be.

I did hide update KB2864202 and currently KB2685811 shows up as optional (attempting to install that one also gives me the error. 

I'm not sure if that's that or what if so well my only concern left would be those AMD files.

Like I mentioned I transfered most of my files from my laptop (that had an AMD card) to my new rig (that has an NVIDIA card) so I'm not entirely sure they are necessary and thus if I could just delete those files except they are under winsxs.
I read I shouldn't delete folders there due to those being used for OS repairs. --- http://blogs.technet.com/b/joscon/archive/2010/08/06/should-you-delete-files-in-the-winsxs-directory-and-what-s-the-deal-with-vss.aspx

However I would imagine those were meant to be for my laptop since I don't have anything AMD related in my rig, the motherboard is Asus for an intel chip and my graphic card is not amd either.

Sure the corrupt files that were picked up by your scanner are under Windows\servicing\Packages\
but I also have a lot of those amd folders under Windows\winsxs

[Shane]

Asus does have a ramdisk but looks like for only certain boards
http://rog.asus.com/technology/republic-of-gamers-motherboard-innovations/ramdisk/

The amd in the winsxs folder doesnt mean it is an amd system, it is how windows labels a 64bit file. 32 bit is x86 and 64 is amd. Amd was the first to come out with a compatible 64bit cpu that could also run 32 bit, so it got the title I guess lol

Both of these updates have to do with the default usb driver and thats it, and when i searched on that update failing there was a TON of results. Looks like a lot of people have had the problem. If those 2 are the only ones failing and all other updates are install ok then I would say to just hide the two updates. But if other updates are failing as well then a repair install might be needed.

For windows updates it not only the files on the drive that can make it mess up but also the registry under the components section. If it becomes messed up or has missing keys then the update that needed it will fail as well. This is why Windows updates has such a bad reputation, it is VERY easy to break. Also the fact that if the update encounters a single error, no matter how little, it will simply bomb out and not move on.

I need to check, but I do know there is a command line option on installing the updates manually, I need to see if there is an option on that tool to force the update to install even if there is an error.
https://msdn.microsoft.com/en-us/library/aa387102%28VS.85%29.aspx
and
https://support.microsoft.com/en-us/kb/262841

Shane

[Ginrikuzuma]

The amd in the winsxs folder doesnt mean it is an amd system, it is how windows labels a 64bit file. 32 bit is x86 and 64 is amd. Amd was the first to come out with a compatible 64bit cpu that could also run 32 bit, so it got the title I guess lol

Well I learned something new today lol

Thank you very much I guess those are all the problems I'll mark this as solved for now hopefully it was only those two updates (3 actually since a 2nd optional update doesn't install either -- Intel - Other hardware - Intel(R) Management Engine Interface but I'll hide that one as well. )