Windows 7 DotNet framework 3.5 SP1 update error 80073712
Hello, Can anyone help with the error that I am receiving when trying to apply an update to one of our Windows 7 (ultimate) client machines. When we try to apply the dotNet framework 3.5 SP1 patch it fails with an error code of 80073712. I have tried downloading both the patch and the entire installation file of 3.5+SP1 and tried to install each file manually (even in safe mode) but I then get an error prompting me to turn windows features on or off (which I tried but this fails with an error also). I have seen forums that mention deleting a pending.xml file and running the Windows Update utility again but this fix appears to be just for Vista. Does anyone have any suggestions? Thanks. DC
January 12th, 2011 10:17am

Try this support article, it also applies to Windows 7: http://support.microsoft.com/kb/931712/en-us And apparently it helped this guy who had the same issue: http://social.answers.microsoft.com/Forums/en-US/vistawu/thread/3b5762eb-a4b0-4953-af77-e93f1ab2668f
Free Windows Admin Tool Kit Click here and download it now
January 12th, 2011 1:36pm

0x80073712 ERROR_SXS_COMPONENT_STORE_CORRUPT The component store is in an inconsistent state See - Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, for Windows 7, and for Windows Server 2008 R2 Download and save the version of the System Update Readiness Tool ( CheckSUR) that matches your system's architecture. If you're unsure of what the architecture is click the link under Method 2: Download the System Update Readiness Tool directly from Microsoft Download Center that states " Click here to view or hide step-by-step instructions with pictures " Once the download is finished suggest you configure the system to Clean boot so as to rule out any 3rd party software interference - How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7 NOTE: When CheckSUR is run the system must be connected to the internet. In the Clean boot state all 3rd party firewalls will be Disabled. Check to see that the native Windows 7 firewall is now On by clicking the Start orb, in the Search programs and files field type in firewall . Under Control Panel click the Check firewall status link. Run CheckSUR and wait until it's finished it's operations. It will create 2 log files located in and named Windows\Logs\CBS\CheckSUR.log Windows\Logs\CBS\CheckSUR.persist.log Go over the logs and see if any content in Winsxs was replaced and if there are still errors showing at the bottom of the logs. You can copy & paste either or both of them into your reply if you wish. They usually show the exact same results. Depending upon how many errors there are, you may have to do an " in-place upgrade ", aka Repair Installation. If no errors are showing after CheckSUR has run, then suggest you try installing the update in question from within the Clean boot state. Whether or not the update installs, undo the Clean boot steps after the updating attempt. If a 3rd party firewall is being used, ensure that it is now On and that the native Win 7 firewall is showing as Off. MowGreen Windows Expert IT Pro - Consumer Security
January 12th, 2011 1:56pm

0x80073712 ERROR_SXS_COMPONENT_STORE_CORRUPT The component store is in an inconsistent state See - Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, for Windows 7, and for Windows Server 2008 R2 Download and save the version of the System Update Readiness Tool ( CheckSUR) that matches your system's architecture. If you're unsure of what the architecture is click the link under Method 2: Download the System Update Readiness Tool directly from Microsoft Download Center that states " Click here to view or hide step-by-step instructions with pictures " Once the download is finished suggest you configure the system to Clean boot so as to rule out any 3rd party software interference - How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7 NOTE: When CheckSUR is run the system must be connected to the internet. In the Clean boot state all 3rd party firewalls will be Disabled. Check to see that the native Windows 7 firewall is now On by clicking the Start orb, in the Search programs and files field type in firewall . Under Control Panel click the Check firewall status link. Run CheckSUR and wait until it's finished it's operations. It will create 2 log files located in and named Windows\Logs\CBS\CheckSUR.log Windows\Logs\CBS\CheckSUR.persist.log Go over the logs and see if any content in Winsxs was replaced and if there are still errors showing at the bottom of the logs. You can copy & paste either or both of them into your reply if you wish. They usually show the exact same results. Depending upon how many errors there are, you may have to do an " in-place upgrade ", aka Repair Installation. If no errors are showing after CheckSUR has run, then suggest you try installing the update in question from within the Clean boot state. Whether or not the update installs, undo the Clean boot steps after the updating attempt. If a 3rd party firewall is being used, ensure that it is now On and that the native Win 7 firewall is showing as Off. MowGreen Windows Expert IT Pro - Consumer Security
Free Windows Admin Tool Kit Click here and download it now
January 12th, 2011 9:51pm

Thanks Kristof, I will try the procedures on that forum and let you know the results.DC
January 14th, 2011 3:38am

Hello, we tried a few fixes, a Windows repair, sfc /scan but neither worked. As we was in a rush to get the machine back online, we just reloaded it and all is now working - thanks for your help.DC
Free Windows Admin Tool Kit Click here and download it now
January 20th, 2011 4:14am

The question that still remains is ... why did the component store end up in an inconsistent state and how can this inconsistency be avoided in the future ? This issue has never occurred on any of my systems as I install all .NET Frameworks by themselves while no other updates are installing. Suggest you try that to see if that mitigates inconsistencies in WinSxS as each update contains packages and some updates have a large number of packages. From my past experiences of assisting Users with .NET updating issues, applying updates for .NET Frameworks is definitely not as reliable as it should be. Keeping the updating process as simple as possible appears to be the most reliable method for updating .NET.MowGreen Windows Expert IT Pro - Consumer Security
January 20th, 2011 3:29pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics