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-25T15:23:20+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.

    The problem with the muck up Microsoft has caused with KB2919355 isn't the inability to update to it (although it appears I've found the solution) or having problems installing updates within the KB2919355 update package on Windows Update... it's the massive System File Corruption caused by a failed KB2919355 install, packaged or standalone.  It's one thing for malware to corrupt system files, another thing entirely for an update from the software designer to cause massive system file corruption to such an extent it renders the only tool designed to repair component store corruption unable to repair the corruption.

    Was this answer helpful?

    0 comments
  2. 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

  3. Anonymous
    2014-05-25T15:11:02+00:00

    I could be wrong, however my experience thus far has been that the 5 updates included within the Windows Update*****KB2919355 Package* are a prerequisite to the actual KB2919355 install.

    Sounds like everything was installed but then something happened either before or after the second KB2919355 which made WU think that KB2934018 was now needed again.  WindowsUpdate.log  may provide some clues for testing that hypothesis but I doubt if there will be enough detail that way to know for sure what is wrong and what was being fixed.  That would be another example of where I would want to be using ProcMon to both correlate and supplement all diagnostics associated with these events.

    Was this answer helpful?

    0 comments