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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2014-05-25T14:41:30+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.  I will edit my instructions to include end users should install the 5 standalone updates first, then do the final standalone KB2919355 through Windows Update.

    I don't have enough knowledge to help troubleshoot, however, if others helping you can't figure it out, my best advice would be to first try uninstalling the 2919355 update, restart the computer, run /startcomponentcleanup, /restorehealth, and finally /scannow (in that order... if corrections are made with restorehealth, you will receive an error upon running scannow and will need to restart before running it.

    If that proves unsuccessful at cleaning the component store, try a system restore, as Windows should automatically create a restore point prior to installing any update.  If you want a fast solution, I would try this first.  Upon restarting and seeing the restore completed successfully, fun the same 3 repair flags as in the previous paragraph, restart after scannow, install KB2934018, then use Windows Update to Install the final KB2919355 update.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-05-25T14:46:15+00:00

    On another tack I think it would be useful to know how we can start picking this stuff apart.  E.g. I wonder if this is the same for everybody:

    PS C:\windows\servicing\Packages> (dir -Filter "*KB2934018*.mum" -Name).count

    And the strangest thing about this IMO is this:

    PS C:\windows\servicing\Packages> (dir -Filter "*KB2934018*.mum") Sort-Object LastWriteTime ft Name

    which implies that I got them alphabetically?  even though the "highest" one numerically is  Package_365?  WTH?  Hopefully there are no dependencies involved with that numeration.  Perhaps that observation depends on the granularity of the "timestamp" (seconds), so someone whose install spanned a second might see a different result.

    I had to double-check that result with a dir/od in a cmd window:

    C:\Windows\servicing\Packages>dir/od *KB2934018*.mum

    and that one double-checks the first one (135, which I had less doubt about)  <eg>

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-05-25T14:58:07+00:00

    While 8.1 ISOs are readily available on numerous software forum sites, it carries a risk... an even higher one if users have little experience with software forums, and worse, if they don't bother checking the md5/SHA1 hash to make sure it matches the md5 hash listed on MSDN.  It's the quicker of the two options, but if a user doesn't check the md5\SHA1 to make sure it hasn't been tampered with, they carry a serious risk of infecting their computer with malware from the start.  

    The VM option is a safe option... the software forums carry a certain degree of risk, of which can be eliminated by verifying md5\SHA1 hashes, but it is reliant upon the end user doing so.

    Was this answer helpful?

    0 comments