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: Newest
  1. 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 No comments
  2. 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 No comments
  3. Anonymous
    2014-06-11T19:33:27+00:00

    Yep, that is correct.

    Was this answer helpful?

    0 comments No comments