Error Code 80073712 Windows update Win 8.1 x64

Anonymous
2014-04-16T19:45:03+00:00

Ok so here are the system specs

After the last update and restart. I am unable to use Windows update.

I have tried the troubleshooting steps but the problem still exists.

SFC returns no problem at all.

Problem occurring for updates KB2936068 and KB2919355

Using their standalone installer isn't working either.

--------- | --------- | --------------- | -------------------

Package Identity

          | State     | Release Type    | Install Time

--------- | --------- | --------------- | -------------------

Microsoft-Windows-CameraCodec-Package~31bf3856ad364e35~amd64~~6.3.9600.16453

          | Installed | Update          | 11-12-2013 01:33:PM

Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-GB~6.3.9

600.16384 | Installed | Language Pack   | 30-09-2013 03:56:AM

Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.3.9600.16384

          | Installed | Foundation      | 22-08-2013 02:46:PM

Package_for_KB2843630~31bf3856ad364e35~amd64~~6.3.3.0

          | Installed | Update          | 15-02-2014 10:59:PM

Package_for_KB2862152~31bf3856ad364e35~amd64~~6.3.1.1

          | Installed | Security Update | 23-11-2013 08:02:PM

Package_for_KB2868626~31bf3856ad364e35~amd64~~6.3.1.2

          | Installed | Security Update | 23-11-2013 08:02:PM

Package_for_KB2876331~31bf3856ad364e35~amd64~~6.3.1.0

          | Installed | Security Update | 23-11-2013 08:02:PM

Package_for_KB2883200~31bf3856ad364e35~amd64~~6.3.1.18

          | Installed | Update          | 30-09-2013 04:25:AM

Package_for_KB2884101~31bf3856ad364e35~amd64~~6.3.1.9

          | Installed | Update          | 27-10-2013 11:10:PM

Package_for_KB2884846~31bf3856ad364e35~amd64~~6.3.1.4

          | Installed | Update          | 27-10-2013 11:10:PM

Package_for_KB2887595~31bf3856ad364e35~amd64~~6.3.2.0

          | Installed | Update          | 23-11-2013 08:02:PM

Package_for_KB2889543~31bf3856ad364e35~amd64~~6.3.1.0

          | Installed | Update          | 30-09-2013 04:25:AM

Package_for_KB2891214~31bf3856ad364e35~amd64~~6.3.1.0

          | Installed | Update          | 28-10-2013 04:32:AM

Package_for_KB2892074~31bf3856ad364e35~amd64~~6.3.1.0

          | Installed | Security Update | 11-12-2013 01:33:PM

Package_for_KB2893294~31bf3856ad364e35~amd64~~6.3.1.1

          | Installed | Security Update | 14-12-2013 01:38:PM

Package_for_KB2894029~31bf3856ad364e35~amd64~~6.3.1.0

          | Installed | Update          | 30-09-2013 04:25:AM

Package_for_KB2894179~31bf3856ad364e35~amd64~~6.3.1.0

          | Installed | Update          | 30-09-2013 04:25:AM

Package_for_KB2894853~31bf3856ad364e35~amd64~~6.3.1.3

          | Installed | Update          | 17-03-2014 07:41:PM

Package_for_KB2898514~31bf3856ad364e35~amd64~~6.3.1.2

          | Installed | Update          | 23-11-2013 08:02:PM

Package_for_KB2898868~31bf3856ad364e35~amd64~~6.3.1.0

          | Installed | Security Update | 15-02-2014 10:59:PM

Package_for_KB2898871~31bf3856ad364e35~amd64~~6.3.1.1

          | Installed | Security Update | 15-02-2014 10:59:PM

Package_for_KB2900986~31bf3856ad364e35~amd64~~6.3.1.2

          | Installed | Security Update | 13-11-2013 09:41:PM

Package_for_KB2901125~31bf3856ad364e35~amd64~~6.3.1.0

          | Installed | Security Update | 15-02-2014 10:59:PM

Package_for_KB2901128~31bf3856ad364e35~amd64~~6.3.1.0

          | Installed | Security Update | 15-02-2014 10:59:PM

Package_for_KB2902892~31bf3856ad364e35~amd64~~6.3.1.0

          | Installed | Update          | 01-11-2013 07:45:PM

Package_for_KB2903939~31bf3856ad364e35~amd64~~6.3.1.2

          | Installed | Update          | 18-12-2013 08:08:PM

Package_for_KB2904266~31bf3856ad364e35~amd64~~6.3.1.1

          | Installed | Update          | 11-12-2013 01:33:PM

Package_for_KB2904440~31bf3856ad364e35~amd64~~6.3.1.1

          | Installed | Update          | 28-01-2014 11:26:PM

Package_for_KB2908816~31bf3856ad364e35~amd64~~6.3.1.1

          | Installed | Update          | 15-02-2014 10:59:PM

Package_for_KB2909210~31bf3856ad364e35~amd64~~6.3.1.0

          | Installed | Security Update | 15-02-2014 10:59:PM

Package_for_KB2909569~31bf3856ad364e35~amd64~~6.3.1.0

          | Installed | Update          | 11-12-2013 01:32:PM

Package_for_KB2909921~31bf3856ad364e35~amd64~~6.3.1.5

          | Installed | Security Update | 15-02-2014 10:59:PM

Package_for_KB2911106~31bf3856ad364e35~amd64~~6.3.1.3

          | Installed | Update          | 24-02-2014 12:03:PM

Package_for_KB2912390~31bf3856ad364e35~amd64~~6.3.1.3

          | Installed | Security Update | 15-02-2014 10:59:PM

Package_for_KB2913152~31bf3856ad364e35~amd64~~6.3.1.0

          | Installed | Update          | 11-12-2013 01:33:PM

Package_for_KB2913270~31bf3856ad364e35~amd64~~6.3.1.1

          | Installed | Update          | 18-01-2014 07:54:PM

Package_for_KB2913760~31bf3856ad364e35~amd64~~6.3.1.0

          | Installed | Update          | 17-03-2014 07:41:PM

Package_for_KB2916036~31bf3856ad364e35~amd64~~6.3.1.2

          | Installed | Security Update | 15-02-2014 10:59:PM

Package_for_KB2917929~31bf3856ad364e35~amd64~~6.3.1.2

          | Installed | Update          | 15-02-2014 10:59:PM

Package_for_KB2917993~31bf3856ad364e35~amd64~~6.3.1.0

          | Installed | Update          | 18-01-2014 07:54:PM

Package_for_KB2919394~31bf3856ad364e35~amd64~~6.3.1.3

          | Installed | Update          | 29-03-2014 08:17:PM

Package_for_KB2919442~31bf3856ad364e35~amd64~~6.3.1.8

          | Installed | Update          | 17-03-2014 07:41:PM

Package_for_KB2919907~31bf3856ad364e35~amd64~~6.3.1.0

          | Installed | Update          | 15-02-2014 10:59:PM

Package_for_KB2922229~31bf3856ad364e35~amd64~~6.3.1.3

          | Installed | Security Update | 10-04-2014 12:42:PM

Package_for_KB2923300~31bf3856ad364e35~amd64~~6.3.1.1

          | Installed | Update          | 15-02-2014 10:59:PM

Package_for_KB2923528~31bf3856ad364e35~amd64~~6.3.1.1

          | Installed | Update          | 15-02-2014 10:59:PM

Package_for_KB2923768~31bf3856ad364e35~amd64~~6.3.1.0

          | Installed | Update          | 15-02-2014 10:59:PM

Package_for_KB2925418~31bf3856ad364e35~amd64~~6.3.1.4

          | Installed | Security Update | 17-03-2014 07:41:PM

Package_for_KB2928680~31bf3856ad364e35~amd64~~6.3.1.2

          | Installed | Update          | 17-03-2014 07:41:PM

Package_for_KB2929961~31bf3856ad364e35~amd64~~6.3.1.2

          | Installed | Security Update | 17-03-2014 07:41:PM

Package_for_KB2930275~31bf3856ad364e35~amd64~~6.3.1.1

          | Installed | Security Update | 17-03-2014 07:41:PM

Package_for_KB2934802~31bf3856ad364e35~amd64~~6.3.1.0

          | Installed | Update          | 24-02-2014 12:03:PM

Package_for_KB2938527~31bf3856ad364e35~amd64~~6.3.1.0

          | Installed | Update          | 17-03-2014 07:41:PM

Package_for_KB2939087~31bf3856ad364e35~amd64~~6.3.1.1

          | Installed | Update          | 10-04-2014 12:42:PM

Package_for_KB2942844~31bf3856ad364e35~amd64~~6.3.1.0

          | Installed | Update          | 10-04-2014 12:42:PM

Package_for_KB976002~31bf3856ad364e35~amd64~~6.3.1.0

          | Installed | Update          | 06-12-2013 12:17:AM

The operation completed successfully.

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-15T08:31:47+00:00

Hi Jaxx,

Microsoft has issued a fix for your error: http://support.microsoft.com/kb/2969339

After you install it, the rest of the updates should download automatically.

Was this answer helpful?

1 person found this answer helpful.
0 comments

95 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2014-05-07T19:45:48+00:00

    2014-05-07 11:01:46, Error                 DISM   DISM Package Manager: PID=5560 TID=4088 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x80240021)

    2014-05-07 13:30:50, Error                 CSI    0000064d@2014/5/7:12:30:50.973 (F) base\wcp\componentstore\deltastore.cpp(2480): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function ComponentStore::CRawStoreLayout::EnsureComponentFullyPresent expression: (null)

    [gle=0x80004005]

    What's the context?  E.g. was that a manual execution of dism /cleanup-image  or something that a failed install might have tried as a recovery procedure?

    Obviously, by the timestamps, the DISM and CBS log entries being examined are unrelated, so again, what was the context?  

    You could use other higher level logs such as  ReportingEvents.log  or  WindowsUpdate.log  or an install log to clarify.   For best results from future tests I would use ProcMon to both correlate and supplement all the diagnostic sources that you have.

    However, if we would believe the CBS.log clues "STATUS_SXS_COMPONENT_STORE_CORRUPT" and "EnsureComponentFullyPresent"  instead of trying something that might be destructive and create a worse problem, e.g. RestoreHealth, how about first trying some of the diagnostic procedures that DISM allows?

    Ref:

    http://technet.microsoft.com/en-us/library/hh825265.aspx

    Use /CheckHealth to check whether the image has been flagged as corrupted by a failed process and whether the corruption can be repaired.

    Use /ScanHealth to scan the image for component store corruption. This operation will take several minutes.

    Use /AnalyzeComponentStore to create a report of the component store. For more information about the report and how to use the information provided in the report, see http://go.microsoft.com/fwlink/?LinkId=293367.

    I suspect those were just listed alphabetically.  FWIW that is the order that I would try them.

    Also, do you have an image backup to fall back to in case your experiments don't work but result in more irreversible corruption?

    HTH

    Robert

    Hi Robert,

      Sorry about the mismatched log entries, CheckHealth and ScanHealth are both happy and claim the store is repairable, but RestoreHealth then fails:

    The restore operation failed. Either the repair source was not found or the comp

    onent store cannot be repaired.

    Error: 0x800f081f

    DISM failed. No operation was performed.

      No idea what I should look for in the Analyse results.

     I think I have a USB stick somewhere around with a backup image,, lets hope I don't have to go there, and MS come up with something that works.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-05-07T22:41:36+00:00

      No idea what I should look for in the Analyse results.

    I was just thinking that it might be another way that corruption would be reported.  If it's clean then I would suspect that the other reports of corruption are bogus.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-05-08T08:32:30+00:00

      No idea what I should look for in the Analyse results.

    I was just thinking that it might be another way that corruption would be reported.  If it's clean then I would suspect that the other reports of corruption are bogus.

    Hi Robert, 

       Nothing particularly revealing:

    Component Store (WinSxS) information:

    Windows Explorer Reported Size of Component Store : 7.15 GB

    Actual Size of Component Store : 6.88 GB

        Shared with Windows : 4.76 GB

        Backups and Disabled Features : 1.88 GB

        Cache and Temporary Data : 245.60 MB

    Date of Last Cleanup : 2014-05-07 08:23:55

    Number of Reclaimable Packages : 12

    Component Store Cleanup Recommended : Yes

    The operation completed successfully.

    Tried /StartComponentCleanup which ran fine, but /RestoreHealth still fails

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-05-08T19:26:26+00:00

    Sadly even those methods are not working.

    Was this answer helpful?

    0 comments