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-17T21:05:09+00:00

    If its at all helpful to anyone, the warnings coming out of dism.log during detect only are:

    2014-05-17 10:13:46, Warning               DISM   DISM Provider Store...Failed to Load the provider: C:\Users...\AppData\Local\Temp...\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2014-05-17 10:13:46, Warning               DISM   DISM Provider Store: ...Failed to get the IDismObject Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80004002)

    2014-05-17 10:13:46, Warning               DISM   DISM Provider Store:...Failed to Load the provider: C:\Users...\AppData\Local\Temp...\Wow64provider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x80004002)

    2014-05-17 10:13:46, Warning               DISM   DISM Provider Store:....Failed to Load the provider: C:\Users...\AppData\Local\Temp...\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    Then during detect and repair i get

    2014-05-17 10:15:27, Error                 DISM   DISM Package Manager:...Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)

    2014-05-17 10:15:27, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F081F

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2014-05-17T23:21:07+00:00

    I've done all these recommended steps multiple times over. DISM says it's repairable, then it says it can't actually repair it when I try...

    And at this point, my CBS.log is full of CHINESE CHARACTERS.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2014-05-17T23:41:42+00:00

    none of the KB’s shows up in CP – Programs & Features – Installed Updates

    So, nothing comparable in both CBS.log either?   See why I like ProcMon?

    Does it get into  WinSxS?

    PS C:\windows\WinSxS> dir -Filter "amd64*_31bf3856ad364e35_6.3.9600.*" -Name | Measure-Object

    Count    : 8583

    Note that the tildes get converted to an underscore and the KB number disappears and the platform is a prefix.

    This exercise has me kicking myself for not obtaining MCSE certification when I was in my 60’s.

    I think this is ludicrous.  Makes IBM Systems Programming look like a bookkeeping.   <eg>

    Was this answer helpful?

    0 comments