Error: 0x80073712 when installing KB 2919355

Anonymous
2014-05-14T19:25:04+00:00

This error might mean that a file needed by Windows Update is damaged or missing. Here are a few steps that have solved the error for other community members:

  1. Swipe in from the right edge of the screen, and then tap Search.

(If you're using a mouse, point to the lower-right corner of the screen, move the mouse pointer up, and then click Search.)

  1. Enter command prompt in the search box.
  2. In the list of results, swipe down on or right-click Command Prompt, and then tap or click Run as administrator.
  3. In the Administrator: Command Prompt window, enter the following commands. Press the Enter key after each command.

If you're running a 64-bit version of Windows 8.1, type:

dism /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14

If you're running a 32-bit version of Windows 8.1, type:

dism /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35~x86~~6.3.1.14

If you're running Windows RT 8.1, type:

dism /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35~arm~~6.3.1.14

  1. Type the following command, and then press Enter:

dism.exe /online /cleanup-image /restorehealth 2. Type the following command, and then press Enter:

dism /online /cleanup-image /startcomponentcleanup

  1. Install the Windows 8.1 Update from the download center.

 Windows 8.1 Update (32-bit version)

 Windows 8.1 Update (64-bit version)

If you have followed these steps and you still receive error 0x80073712, log files may need to be collected and reviewed. Please contact Microsoft Support so that we can further investigate your issue.

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
Answer accepted by question author
Anonymous
2014-06-11T01:22:45+00:00

RH6M6,

I saw the kb2969339 update come through this morning a good 6 hours before the normal patch Tuesday updates were to be released and thought it was strange. Applied it to the final computer tonight and ran Windows Update. KB2919355 went right through and installed and the rest of the updates are now being installed. Hope this solution works for others.  Thanks.

Jim

Was this answer helpful?

3 people found this answer helpful.
0 comments

245 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2014-05-26T15:39:01+00:00

    I'm not getting confused... and while Microsoft may say that's how they should be installed, they're not able to be installed in the order without problems occurring.  This is not my opinion, but the experiences of myself and 4 other users who've commented thus far, 2 of which I believe have commented on this thread.

    A repair install WILL NOT *fix the problem, although it will fix the corruption caused by KB2919355.*Again, PLEASE REVIEW THE POSTS IN THIS THREAD BEFORE GIVING OUT FURTHER ADVICE.  <ToU/CoC violation removed>

    ***EDIT: My purpose here isn't to be rude, but to prevent the wrong information from corrupting an almost flawless fix for the havoc caused by KB2919355***

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-05-26T15:27:41+00:00

    I think we're getting confused.

    2919442  That was an update released in March and should be installed before this process begins.

    when installing from the download center: 

    Then the clearcompression flag patch goes on.

    Then KB2919355, KB2932046, KB2959977, KB2937592, KB2938439, and KB2934018.

    There may be at this time a small post patch also labeled 2919355 but by this time if you got all the rest listed above installed already, the rest of the updates will go on okay as well.

    If you can't get KB2919355, KB2932046, KB2959977, KB2937592, KB2938439, and KB2934018 installed from the download site, the WU implementation won't work either.

    Bottom line the folks that are left need a repair install.

    I'm not convinced the install of the update 'caused' the corruption.  This update just showcases that many are in this corrupted state.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-05-26T15:17:41+00:00

    Every user thus far I've communicated with, who've not installed the 5 standalones before installing the actual 2919355 update, have been unable to install whichever standalone they missed after successfully installing 2919355.

    As far as the Microsoft link you referred to, everyone, including moderators, should know by now to not trust anything Microsoft has to say about the KB2919355 update.  Thousands of users are now the victim of massive system file corruption due to this update.  Microsoft was alerted to these problems at the beginning of April, and have thus far done nothing to solve the issue, instead posting worthless troubleshooting step that won't work, then telling users they need to reset/refresh, which should NEVER be done to troubleshoot an issue, period. On top of this, even though Microsoft said they would not start withholding patches from those not updated with KB2919355 until the first week of June, they've already began, as 11 patches will not become available until KB2919355 is installed (theactual update, which is around 640MB in size).

    Thus far, it appears I am the only Windows user to have stumbled upon a fix for all KB2919355 install issues.  I would encourage you to please read my tutorial, and please do not tell users to install any of the 5 included updates after 2919355, as more than one will fail to install.

    Was this answer helpful?

    0 comments