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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-05-25T21:57:14+00:00

    ***KB2919355 Fix that WILL allow the install of KB2919355***

    As many discoveries have been made, I discovered this accidentally. and quite by coincidence... 

    In order for users, who've been plagued by errors and file corruption, to get a successful completion of KB2919355, all that's needed is to run the 8.1 upgrade installer, and when the 8.1 installer goes to the wait screen after entering the generic product key, start Windows Update for the install of KB2919355

    EDIT: It appears, from the input of other users, one must FIRST install the 5 standalone updates included within the Windows Update KB2919355 package, you will then need to restart after the fifth and final standalone, then use Windows Update to install KB2919355 (do not use the standalone installer for KB2919355... use Windows Update).

    Steps

    1. Run the Windows 8.1 installer from within Windows, as if you're going to do an install repair "upgrade".
    2. Enter the generic product key, and upon clicking next, the installer will say wait...
    3. Give the installer about 5 minutes, then start Windows Update (it should show the KB2919355 update), and click install.
    4. Windows Update will begin downloading the update... if you have a Windows Update cache problem that causes the speed and percentage to remain at zero, don't worry about it and get the update installed first, then you can clear the cache and remove the directories afterwards.
    5. The install may fail, don't worry... simply hit install again, making sure the 8.1 installer screen is still on the "wait" screen, as whatever the installer is doing during the "wait" screen is what makes the KB2919355 install possible.
    6. KB2919355 should install and Windows Update should request you to restart... simply do so without cancelling the 8.1 installer.  Windows will finalize the update during the shutdown and restart processes.
    7. Upon rebooting into Windows, you will have a multitude of additional updates that will need to be installed (around 10, give or take a few), and you can verify the install of KB2919355 by going to "view installed updates"

    A few users will need to comment back once they'e performed this in order to see if this automatically fixes the multitude of issues users are facing, and if it doesn't complete successfully, then I can back track what step I took over the past several days in order to figure out what caused this to work for me, but not others if problems occur.

    I'll try this on my recently repair-installed 8.1, when the missus finishes her work.

    Do you think it's needed to use a generic key or can I use the legit key that came with the install media MS sent?

    Also should I run WU up to the point where it's offering 2919355, then do this  procedure? I disabled auto update after my repair install, so have no updates installed, 2919355 is not offered ATM, tho I see that 442 pre-req is.

    Edit: just saw your edit. I'll try this and report back.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-05-25T20:48:04+00:00

    I finally opened a ticket with MS support. They spent over 4 hours and fixed my machine. My faith has been restored in MS.

    It was actually very painless, you just need a morning or afternoon to hang around the house. They hung up the phone and did the work, then called me back.

    I'm happy>>>>

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-05-25T18:29:33+00:00

    KB2934018 is a 129MB update, and if it's not showing as installed under "Installed Updates" "Update History" then it wasn't installed.

    You're missing my point.  I suspect it was installed, resulting in however many modules it contains being updated.  Subsequently all it would take is for one of those modules being changed (e.g. regressed or deleted or otherwise made inaccessible) to make WU decide that that update needed to be reapplied.  In fact, for all I know that subsequent download might be tailored to what was discovered that way.  Then, instead of getting the same 135 packages again, only some of them would be needed.  But if the same conditions existed which made the update appear incomplete still existed when it goes to be reapplied it would then appear in total as a failed install.  In any case, a start at checking for this hypothesis would be as I mentioned in the WindowsUpdate.log.

    Was this answer helpful?

    0 comments