Share via

WindowsUpdate error 0x80073712 - cannot fix

Anonymous
2015-12-02T09:04:19+00:00

When using Windows Update on my Win 7 (32 bit), some months ago I failed to install some updates, error code being 80073712. As new updates have become available, many of them could not be installed either because of that error.

Now, focusing on the problem, I succeeded to fix many of the errors shown by the tool “System Update Readiness tool” using the article How to fix errors found in the CheckSUR.logand its 2nd advice. The problematic update seemed to be KB2987107. The exception to the advice was that when the article advised to place the package under %WinDir%\Temp\CheckSUR\Packages, I had to place it under %WinDir%\CheckSUR\Packages to get it working. After that the System Update Readiness tool fixed many of the errors in CheckSUR.log but still there remained 17 errors.

Then I tried to fix them mainly by using the advice of the article You can't install updates in Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2. I have used its methods up to its method 7, without any success.

The current summary of CheckSUR.log is shown below.  When I look at the error manifests in %WinDir%\winsxs\Manifests, they all seem to contain binary code plus text strings. If I look random other file in %WinDir%\winsxs\Manifests, all I have found are pure text files.

How to proceed?

I suspect that this issue may affect to my efforts to upgrade to Windows 10. At least WindowsUpdate does not list Win 10 upgrade as a possible update.

=================================

Summary:

Seconds executed: 1539

 Found 17 errors

  CSI Manifest All Zeros Total count: 1

  CSI Manifest Failed Catalog Check Total count: 16

Unavailable repair files:

                             winsxs\manifests\x86_14c88482f425722dce21e6898a352582_b03f5f7f11d50a3a_6.1.7601.22970_none_68e556e6ab8a28b1.manifest

                             winsxs\manifests\x86_379720f5e744794c4c9e88e8210e70c0_31bf3856ad364e35_6.1.7601.22948_none_217f5934d7ba9aa9.manifest

                             winsxs\manifests\x86_microsoft-windows-lsa.resources_31bf3856ad364e35_6.1.7601.23040_fi-fi_27fa92b90358269a.manifest

                             winsxs\manifests\x86_microsoft-windows-i..riptedsandboxplugin_31bf3856ad364e35_11.2.9600.17843_none_e1eb89e5c82c665b.manifest

                             winsxs\manifests\x86_microsoft-windows-capi2-wintrust-reg_31bf3856ad364e35_6.1.7601.18526_none_8afadde4f1d5af52.manifest

                             winsxs\manifests\x86_microsoft-windows-i..riptcollectionagent_31bf3856ad364e35_11.2.9600.17843_none_3bd6f449f5994b05.manifest

                             winsxs\manifests\x86_8cb15662793a4fc778c808b6ebf5a406_b03f5f7f11d50a3a_6.1.7601.18763_none_7bc0eb4f3e7f9643.manifest

                             winsxs\manifests\x86_ce35cb884970aa3a52b6075c49114fef_31bf3856ad364e35_6.1.7601.18741_none_5582348fb2b58b90.manifest

                             winsxs\manifests\x86_ca8b5f4deced1208014ccb01a11c2195_b77a5c561934e089_6.1.7601.22970_none_d0ea0dc7cc4b4d78.manifest

                             winsxs\manifests\x86_microsoft-windows-n..xcorecomp.resources_31bf3856ad364e35_6.1.7601.18523_fi-fi_a4649acde5dc8891.manifest

                             winsxs\manifests\x86_microsoft-windows-w..client-ui.resources_31bf3856ad364e35_7.6.7601.18804_fi-fi_9101da69643b78ec.manifest

                             winsxs\manifests\x86_af0f05c36620bfcaf625f971aca3e637_b77a5c561934e089_6.1.7601.18763_none_9c644cf4040a27ce.manifest

                             winsxs\manifests\x86_microsoft-windows-w..client-ui.resources_31bf3856ad364e35_7.6.7601.18804_en-us_f21b78d86efa951d.manifest

                             winsxs\manifests\x86_microsoft-windows-rastls_31bf3856ad364e35_6.1.7601.22792_none_6e9d9dcec7c65cc4.manifest

                             winsxs\manifests\x86_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_11.2.9600.17420_none_3b1c478c3379dbe2.manifest

                             winsxs\manifests\x86_microsoft-windows-i..rityzones.resources_31bf3856ad364e35_11.2.9600.17843_en-us_f4925ddc3e48482e.manifest

                             winsxs\manifests\x86_microsoft-windows-lsa.resources_31bf3856ad364e35_6.1.7601.23040_en-us_891431280e1742cb.manifest

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

16 answers

Sort by: Most helpful
  1. Anonymous
    2016-02-09T11:33:26+00:00

    The problem is still unsolved.

    I found in Internet ISO image for Windows 7 Ultimate Sp1 32-bit. I burnt a DVD using the file and then tried to upgrade with it. It failed because in my system English was not used as the initial installation language.

    In order to try upgrade I would need Windows 7 Ultimate Sp1 32-bit Scandinavian Edition (English, Danish, Finnish, Norwegian, Swedish). I guess such ISO image is not any more available in Internet.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2015-12-10T13:25:48+00:00

    Hi,

    Thank you for the update.

    I suggest you to check if the services responsible for Windows update is running. Refer to these steps:

    1. Press Windows key +R, type “services.msc”
    2. Locate the BITS, Cryptographic, MSI Installer and the Windows Update Services and check if it is running.
    3. If not, right click on the service and click start to start the service.

    Hope this information helps. Please let us know if you need any other assistance with Windows in future. We will be happy to assist you.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2015-12-07T12:36:12+00:00

    I carried out the Metdod 1 operations and also the Method 2 operations (after clean boot and no other applications).

    After that the contents of the Sfcdetails.txt file was still the same as before those operations.

    I made the Sfcdetails.txt file according to instructions in https://support.microsoft.com/en-us/kb/929833 (as I had done before).

    For instance, the first issue in it was:

    2015-12-07 12:21:17, Info                  CSI    00000680 [SR] Cannot verify component files for 8cb15662793a4fc778c808b6ebf5a406, Version = 6.1.7601.18763, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)

    I ran finally also “System Update Readiness tool”. The CheckSUR.log after that was similar as before.

    What should I do next?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-12-05T13:25:52+00:00

    Hi,

    Thank you for posting your query on Microsoft Community.

    As per the description, I understand that you are unable to install Windows updates.

    This might have occurred due to some corruptions in Windows updates.

    Try the Methods.

    Method 1:

    I suggest you to perform clean boot and check, using this Microsoft Article because may be a third party application is causing this issue.

    https://support.microsoft.com/en-us/kb/929135

    NOTE:

    A clean boot is performed to start Windows by using a minimal set of drivers and startup programs. This helps eliminate software conflicts that occur when you install a program or an update or when you run a program in Windows. You may also troubleshoot or determine what conflict is causing the problem by performing a clean boot. You must log on to the computer as an administrator to be able to perform a clean boot. Your computer may temporarily lose some functionality when you perform a clean boot. When you start the computer normally, the functionality returns. However, you may receive the original error message, or experience the original behavior if the problem still exists. If the computer is connected to a network, network policy settings may prevent you from following these steps.

    https://support.microsoft.com/kb/929135

    Once you perform clean boot do refer to the section “How to reset the computer to start normally after clean boot troubleshooting” to boot the computer in normal mode.

    Method 2:

    I would suggest you to perform a SFC Scan and check if it helps.

    Refer to the following link given below.

    https://support.microsoft.com/en-us/kb/929833

    Note: While performing SFC Scan I would recommend you to make sure that there are no applications or programs running on the back ground.

    You may refer:

    http://answers.microsoft.com/en-us/windows/forum/all/windows-7-update-error-0x80073712/56289506-5bce-4302-b989-60b80688882c

    Hope this information helps. Please let us know if you need any other assistance with Windows in future. We will be happy to assist you.

    Was this answer helpful?

    0 comments No comments
  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more