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-06-12T00:29:53+00:00

    http://support.microsoft.com/kb/2969339

    How interesting - I wonder if this is finally a fix to the issue and they'll stop blaming end users for doing something wrong..

    Look forward to hearing whether this resolves the issue.

    This did fix the issue finally after two months on my Asus Laptop.  I tried all of the alleged solutions in the thousands of post in these forums, all failing.  Here's a somewhat concise sequence all using windows update with no changes to anything on my systems.  Nothing disabled or turned off as that's the way windows update is supposed to  and does work.

    Scanned for updates.

    Selected only KB2969339 (the new fix issued), downloaded and install successfully. No reboot required.

    Scanned for updates again and selected only KB2919355. It was listed at 890MB. 

    Sat at 0MB and 0% for around 20min, but there was a lot of disk activity.  Jumped suddenly to around 46%.  Noticed the file size now was listed around 740MB?  After another 20min it had slowly climbed to 92% and then all of a sudden is was installing.  That went on for another 20min.

    Finished and I got error code 80070002, but there was Restart prompt.

    Restarted and it continued the install process with no failures.  Desktop had the Windows Store icon.

    Back to Windows Update.  Update history showed KB2919355 as failed, but it was listed as installed in installed updates.

    Scanned for updates again and KB2919355 listed again but file size is now around 149MB.  Selected only that one.  Downloaded and install and then reports update not needed already installed or something like that.

    Reboot.

    Rescan updates and select it again.  Downloads and installs successfully.  Reboots to finish.

    Back to windows update to rescan and KB2919355 is there again but now around 126MB.  Download and installs successfully reboot to finish.

    Rescan updates and it's no longer listed.  Update history now shows success.

    Selected the other 20 update listed including the current patch Tuesday one.  All successfully installed.

    All I can figure is that the 890MB update got split up by the update process and was done in sections which kind of accounts for the change in file size initially and then the additional smaller updates afterwards.

    Hope this helps.

    Was surely the worst MS rollout I've seen in all my years since the MS-Dos days.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-06-11T23:40:25+00:00

    Not for me. After installing 2969399 and then 2919355, running (my Windows is Single Language Spanish, so I added the /english switch)

    dism.exe /english /online /cleanup-image /restorehealth

    I get the following:

    Deployment Image Servicing and Management tool

    Version: 6.3.9600.17031

    Image Version: 6.3.9600.17031

    [==========================100.0%==========================]

    Error: 0x800f0906

    The source files could not be downloaded.

    Use the "source" option to specify the location of the files that are required t

    o restore the feature. For more information on specifying a source location, see

     http://go.microsoft.com/fwlink/?LinkId=243077.

    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

    But sfc /scannow says there are no problems in my machine...

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-06-11T19:39:53+00:00

    I know I read somewhere on Microsoft.com in the past day or two about one of the issues with KB2919355 was the age of one of the components within KB2919355 (it was reporting newer or older than the component installed, can't remember which).  Not sure if this would affect DISM and cause it to report corruption, but it'll be interesting to see if Microsoft addresses the why factor.

    Was this answer helpful?

    0 comments