Error Code 80073712 Windows update Win 8.1 x64

Downloaded the latest 2919355.msu and attempted by hand, still fails with 0x80073712, tried running the diagnostic tool, but that couldn't fix anything up.

Like many, it appears, I've wasted a good part of the day Googling, and trying things to no avail. Machine came with Windows 8 installed, has been kept up to date, and has only ever run Microsoft Security Essentials. 

'Refreshing' my PC isn't a terribly attractive idea, getting apps reinstalled is a non trivial exercise.

            wasted a good part of the day Googling, and trying things to no avail.

       

Try some diagnosis?  I would still like to see what this 0x80073712 really means.  If we knew what it meant there would be a better chance of devising an effective workaround.  (SOP for end users of closed source software.)

            wasted a good part of the day Googling, and trying things to no avail.

       

Try some diagnosis?  I would still like to see what this 0x80073712 really means.  If we knew what it meant there would be a better chance of devising an effective workaround.  (SOP for end users of closed source software.)

Would love to contribute anything I can, any log files I can search through?

DSIM offers up this:

2014-05-07 11:01:46, Error                 DISM   DISM Package Manager: PID=5560 TID=4088 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80240021)

2014-05-07 11:01:46, Error                 DISM   DISM Package Manager: PID=5560 TID=4088 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x80240021)

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 11:01:46, Error                 DISM   DISM Package Manager: PID=5560 TID=4088 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80240021)

2014-05-07 11:01:46, Info                  DISM   DISM Package Manager: PID=5560 TID=4088 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

2014-05-07 11:01:46, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80240021 

CBS offers up:

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]

2014-05-07 13:30:50, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.

2014-05-07 13:30:51, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20140507115150.log to WER report.

2014-05-07 13:30:51, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20140507101955.log to WER report.

2014-05-07 13:30:51, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20140507083946.log to WER report.

2014-05-07 13:30:51, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20140507081757.log to WER report.

2014-05-07 13:30:51, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20140507072206.cab to WER report.

2014-05-07 13:30:51, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2014-05-07 13:30:51, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2014-05-07 13:30:51, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2014-05-07 13:30:57, Error                 CSI    0000064e (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #4584798# from CFileInstaller::DoComponentOperation(...)[gle=0xd015001a]

2014-05-07 13:30:57, Error                 CSI    0000064f (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #4584776# from CFileInstaller::ProcessComponentChange(...)[gle=0xd015001a]

2014-05-07 13:30:57, Error                 CSI    00000650 (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #4584775# from PrimitiveInstaller::CCoordinator::ProcessChange(Change 6.3.9600.16460 -> 6.3.9600.17031 for intelpep.inf, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral)[gle=0xd015001a]

2014-05-07 13:30:57, Info                  CSI    000000ae SMI Primitive Installer [done]

2014-05-07 13:30:57, Error                 CSI    00000651 (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #2318289# from CCSDirectTransaction::PerformChangeAnalysis(...)[gle=0xd015001a]

2014-05-07 13:30:57, Error                 CSI    00000652 (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #2318288# from CCSDirectTransaction::PrepareForCommit(...)[gle=0xd015001a]

2014-05-07 13:30:57, Error                 CSI    00000653 (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #2318287# from CCSDirectTransaction::ExamineTransaction(...)[gle=0xd015001a]

2014-05-07 13:30:57, Error                 CSI    00000654 (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #2318286# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(...)[gle=0xd015001a]

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