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-05-17T19:32:46+00:00

    CBS log is 103710 lines

    I searched for family of KB2919355 related KB’s – 2932046; 2959977; 2937592; 2938439; 2934018; and all EXCEPT 2919355 have entries similar to this – (2919355 is not in CBS file)

    2014-05-15 18:09:19, Info                 <br>CBS    Session: 30371978_1371178093 initialized   by client WindowsUpdateAgent.
    2014-05-15 18:09:19, Info                 <br>CBS    Appl: detect Parent, Package: Package_for_KB2938439~31bf3856ad364e35~amd646.3.1.0,   Parent:   Microsoft-Windows-Client-Features-Package-AutoMerged-base~31bf3856ad364e35~amd646.3.9600.16384,   Disposition = Detect, VersionComp:<br> EQ, ServiceComp: GE, BuildComp: EQ,   DistributionComp: GE, RevisionComp: GE, Exist: present
    2014-05-15 18:09:19, Info                 <br>CBS    Appl: detectParent: package:   Package_for_KB2938439~31bf3856ad364e35~amd646.3.1.0, parent found:   Microsoft-Windows-Client-Features-Package-AutoMerged-base~31bf3856ad364e35~amd646.3.9600.16384,   state: Installed
    2014-05-15 18:09:19, Info                 <br>CBS    Appl: detect Parent, Package:   Package_for_KB2938439~31bf3856ad364e35~amd64~~6.3.1.0, disposition state from   detectParent: Installed
    2014-05-15 18:09:19, Info         <br>          CBS    Appl: Evaluating package applicability   for package Package_for_KB2938439~31bf3856ad364e35~amd64~~6.3.1.0, applicable   state: Installed
    2014-05-15 18:09:19, Info                 <br>CBS    Appl: detect Parent, Package:   Package_for_KB2938439_RTM~31bf3856ad364e35~amd646.3.1.0, Parent:   Microsoft-Windows-Client-Features-Package-AutoMerged-base~31bf3856ad364e35~amd646.3.9600.16384,   Disposition = Detect, VersionComp:<br> EQ, ServiceComp: GE, BuildComp: EQ,   DistributionComp: GE, RevisionComp: GE, Exist: present
    2014-05-15 18:09:19, Info                 <br>CBS    Appl: detectParent: package:   Package_for_KB2938439_RTM~31bf3856ad364e35~amd646.3.1.0, parent found:   Microsoft-Windows-Client-Features-Package-AutoMerged-base~31bf3856ad364e35~amd646.3.9600.16384,   state: Installed
    2014-05-15 18:09:19, Info                 <br>CBS    Appl: detect Parent, Package:   Package_for_KB2938439_RTM~31bf3856ad364e35~amd64~~6.3.1.0, disposition state   from detectParent: Installed
    2014-05-15 18:09:19, Info                 <br>CBS    Appl: Evaluating package applicability   for package Package_for_KB2938439_RTM~31bf3856ad364e35~amd64~~6.3.1.0,   applicable state: Installed
    2014-05-15 18:09:19, Info                 <br>CBS    Appl: detect Parent, Package:   Package_for_KB2938439_RTM_GM~31bf3856ad364e35~amd646.3.1.0, Parent:   Package_for_KB2919355~31bf3856ad364e35~amd646.3.1.14, Disposition = Staged,   VersionComp: EQ, ServiceComp: GE, BuildComp: GE,<br> DistributionComp: GE,   RevisionComp: GE, Exist: present
    2014-05-15 18:09:19, Info         <br>        CBS      Appl: detectParent: package:   Package_for_KB2938439_RTM_GM~31bf3856ad364e35~amd646.3.1.0, parent found:   Package_for_KB2919355~31bf3856ad364e35~amd646.3.1.14, state: Staged
    2014-05-15 18:09:19, Info                 <br>CBS    Appl: detect Parent, Package:   Package_for_KB2938439_RTM_GM~31bf3856ad364e35~amd64~~6.3.1.0, disposition   state from detectParent: Staged
    2014-05-15 18:09:19, Info                 <br>CBS    Appl: Evaluating package applicability   for package Package_for_KB2938439_RTM_GM~31bf3856ad364e35~amd64~~6.3.1.0,   applicable state: Staged
    2014-05-15 18:09:19, Info                 <br>CBS    EvaluateApplicability, package:   Package_for_KB2938439_RTM_GM~31bf3856ad364e35~amd64~~6.3.1.0, Package   applicability: Staged.
    2014-05-15 18:09:19, Info                 <br>CBS    Appl: detect Parent, Package:   Package_85_for_KB2938439~31bf3856ad364e35~amd646.3.1.0, Parent:   Microsoft-Windows-Common-Foundation-Package~31bf3856ad364e35~amd646.3.9600.16384,   Disposition = Detect, VersionComp: EQ, ServiceComp:<br> GE, BuildComp: EQ,   DistributionComp: GE, RevisionComp: GE, Exist: present
    2014-05-15 18:09:19, Info                 <br>CBS    Appl: detectParent: package:   Package_85_for_KB2938439~31bf3856ad364e35~amd646.3.1.0, parent found:   Microsoft-Windows-Common-Foundation-Package~31bf3856ad364e35~amd646.3.9600.16384,   state: Installed
    2014-05-15 18:09:19, Info                 <br>CBS    Appl: detect Parent, Package:   Package_85_for_KB2938439~31bf3856ad364e35~amd64~~6.3.1.0, disposition state   from detectParent: Installed
    2014-05-15 18:09:19, Info                 <br>CBS    Appl: Evaluating package applicability   for package Package_85_for_KB2938439~31bf3856ad364e35~amd64~~6.3.1.0,   applicable state: Installed
    2014-05-15 18:09:19, Info                 <br>CBS    External EvaluateApplicability, package:   Package_85_for_KB2938439~31bf3856ad364e35~amd64~~6.3.1.0, package applicable   State: Installed, highest update applicable state: Installed, resulting   applicable state:Installed
    2014-05-15 18:09:19, Info            <br>     CBS      External EvaluateApplicability, package:   Package_for_KB2938439_RTM~31bf3856ad364e35~amd64~~6.3.1.0, package applicable   State: Installed, highest update applicable state: Installed, resulting   applicable state:Installed
    2014-05-15 18:09:19, Info                 <br>CBS    External EvaluateApplicability, package:   Package_for_KB2938439~31bf3856ad364e35~amd64~~6.3.1.0, package applicable   State: Installed, highest update applicable state: Installed, resulting   applicable state:Installed

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

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

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2014-05-17T18:11:08+00:00

    Searched for the package “355”. Nothing comes up.

    Why not do that first?  Then you could avoid a Remove-Package which would fail (for whatever reason or confusing code).

    4. DISM – restore health

    dism.exe /online /cleanup-image /restorehealth

    The restore operation failed. Either the repair source was not found or the component store cannot be repaired.

    Error: 0x800f081f

    This is controversial.  Some are using other switches (with potentially irreversible effects) on this command with the contention that using this (supposedly safe?) format of the command may (ironically) corrupt the store.

    http://answers.microsoft.com/message/b7d90452-bcec-49fc-9c7b-cd97a9f57579?threadId=4d4d23a3-695a-4bd4-b340-d2ce9c75919d

    <quote  author="Dogtamer">

    Please note that the post by ThenrikI mentioned earlier in this thread, along with feedback in both the The HotFix Share and Shavlik's Patch Management List as well as my own testing all appear to indicate that running the latter command without the "/resetbase" switch may actually be causing component store corruption if the msu package from a failed instance of KB2919355 isn't first removed by running the command "C:\Windows|System32>DISM.exe /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14- again,

    with elevated privileges; the command argument should be DISM.exe /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35~x86~~6.3.1.14for 32-bit versions of Windows 8.1

    </quote>

    So what happens if you do a  CheckHealth  now?   And if that indicates there is a problem  ScanHealth and AnalyzeComponentStore.

    Hi Robert,

    Thanks for taking the time to look into this. I appreciate it!

    I just run a new CheckHealth. Same result as earlier:

    Deployment Image Servicing and Management tool

    Version: 6.3.9600.16384

    Image Version: 6.3.9600.16384

    The component store is repairable.

    The operation completed successfully.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2014-05-17T13:49:17+00:00

    Searched for the package “355”. Nothing comes up.

    Why not do that first?  Then you could avoid a Remove-Package which would fail (for whatever reason or confusing code).

    4. DISM – restore health

    dism.exe /online /cleanup-image /restorehealth

    The restore operation failed. Either the repair source was not found or the component store cannot be repaired.

    Error: 0x800f081f

    This is controversial.  Some are using other switches (with potentially irreversible effects) on this command with the contention that using this (supposedly safe?) format of the command may (ironically) corrupt the store.

    http://answers.microsoft.com/message/b7d90452-bcec-49fc-9c7b-cd97a9f57579?threadId=4d4d23a3-695a-4bd4-b340-d2ce9c75919d

    <quote  author="Dogtamer">

    Please note that the post by ThenrikI mentioned earlier in this thread, along with feedback in both the The HotFix Share and Shavlik's Patch Management List as well as my own testing all appear to indicate that running the latter command without the "/resetbase" switch may actually be causing component store corruption if the msu package from a failed instance of KB2919355 isn't first removed by running the command "C:\Windows|System32>DISM.exe /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14- again,

    with elevated privileges; the command argument should be DISM.exe /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35~x86~~6.3.1.14for 32-bit versions of Windows 8.1

    </quote>

    So what happens if you do a  CheckHealth  now?   And if that indicates there is a problem  ScanHealth and AnalyzeComponentStore.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments