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 No 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 No comments

245 additional answers

Sort by: Most helpful
  1. Anonymous
    2014-05-23T10:11:40+00:00

    I would like to try the recovery method for Repair Install Upgrade, but have not been able to download Windows 8.1 media. After entering a generic Key, I just get a cannot connect right now message, even though I have a good internet connection.

    If you could direct me to a x64 en-gb ISO that would be great.

    I also get the 'Cannot connect right now' message when doing that. Apparently, generic keys are rejected. by the downloader. Thus, if you have a key for windows 8 only, you either have to download and re-install windows 8 and then update manually to 8.1

    • update 1, or download a windows 8.1 ISO directly from not-so-legal sources. I don't understand the choice Microsoft's made here. I mean, MS wants people to update to the latest version of their OS, right? Silly.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-05-23T05:21:35+00:00

    I would like to try the recovery method for Repair Install Upgrade, but have not been able to download Windows 8.1 media. After entering a generic Key, I just get a cannot connect right now message, even though I have a good internet connection.

    If you could direct me to a x64 en-gb ISO that would be great.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-05-22T00:17:13+00:00

    DISM isn't necessarily "buggy" but system corruption has been introduced as a result of the failed KB2919355 update which may make it appear to be "buggy". Of course, the suggestions proposed here to fix the problem which are the same suggestions which have been proposed since April 8th do not solve the issue except for those who have access to an 8.1 ISO or other similar media, which excludes most of us. Nothing is being done about it other than more posts, more threads with the same non-solutions posted day after day after day and now month after month. Users are chasing their tails unless and until Microsoft solves the problem, which after a month and a half does not appear to be imminent. It is truly amazing to see the same posts which were first posted on April 8th are still being posted on a daily basis. I guess there is someone new here every day so the posts appear to be new to these new posters which precipitates more and more posts with more and more people chasing their tails.

    Was this answer helpful?

    0 comments No comments