Main Forum > General Computer Support
Windows Update error 80073712 (Solved)
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.
--- Quote ---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.
--- End quote ---
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:
--- Quote from: Shane on May 20, 2015, 12:54:28 pm ---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.
--- Quote ---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.
--- End quote ---
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
--- End quote ---
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:
--- Quote from: Shane on May 20, 2015, 03:50:36 pm ---
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
--- End quote ---
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. )
Navigation
[0] Message Index
[*] Previous page
Go to full version