Error: 0x80070003 when installing KB 2919355

I am well-aware of the problem. I am also aware of the issues of a failure when pointing to a good source which likewise does not work, which is why I posted. I'm as tired as you are of the posts which lead to nowhere which is why I take the time to respond to them. Unfortunately these posts continue day-after-day, week-after-week and who knows how much longer. Unfortunately these same posts continue and have continued for seven weeks without any evidence of a solution.

The best answer... no one knows.  Unfortunately, it's unlikely Microsoft will figure it out either, or if they do, it'll be a year or more from now.

The only successful way of repairing this error is to do a repair install with the 8.1 installation media (run the installer from inside windows, select keeps all files/settings, and install - you'll also need the generic PK for your version of windows which is available through google).  I have a hunch that when the KB2919355 install goes wrong, dism is corrupted.  I don't know this for sure, however even if you use the /source flag and point to either the install.wim (install.esd) or a mounted 8.1 installation with no corruption, you'll still receive an error.  This, at least to me, points to some sort of corruption within the DISM utility itself.  Since DISM is the only program capable of repairing component store corruption, the only way to cure the corruption that is causing this error is a repair install.

EDIT:

Just something I noticed, the dism log would be found in the dism folder.  The cbs log is what SFC writes to, the dism log what dism writes to (unless it also writes to the cbs log).  According to a few other forums I checked out, the result would still be the same, with both logs showing no errors and a repair install still required.  Please see the eightforums link to see the experience reproduced below:

http://www.eightforums.com/tutorials/26512-dism-fixing-component-store-corruption-windows-8-a.html

We can easily imagine that 10,000 computers are damaged.

I think  it would be  about  0.01%  of  all Windows 8.1 installations, and Microsoft will not even make a patch for them.

Look at this page, for example

http://answers.microsoft.com/en-us/windows/forum/windows8_1-winapps/issues-with-apps-not-loadingopening/6da2249b-c218-4f69-8046-8f7ac72138ea?page=3

The file  CNBJ2530.DPB  of prncacla.inf   is corrupted. The date of this post - January 2014

This error is  often repeated in other forums.

The KB2919355  error  leads us to the same packages. Is there the some relationship?

The file CNBJ2530.DPB  is not a compressed one  while others are compressed in this package.  Why?

Do you remember the ClearCompressionFlag.exe ?

Since you posted your reason as as to why Microsoft won't or refuses to deal with this issue, then then perhaps you will address this issue or ask Microsoft why they won't deal with this issue.

I receive an error message when using /Restorehealth 

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

Error: 0x800f081f

DISM failed. No operation was performed.

For more information, review the log file.

***************

After the error message this is what appears in the CBS.log:

Checking System Update Readiness.

Summary:

Operation: Detect and Repair 

Operation result: 0x0

Last Successful Step: Entire operation completes.

Total Detected Corruption: 0

CBS Manifest Corruption: 0

CBS Metadata Corruption: 0

CSI Manifest Corruption: 0

CSI Metadata Corruption: 0

CSI Payload Corruption: 0

Total Repaired Corruption: 0

CBS Manifest Repaired: 0

CSI Manifest Repaired: 0

CSI Payload Repaired: 0

CSI Store Metadata refreshed: True

Rather than providing us with conjecture and opinions and reasons why "the company" will not deal with the issue, many of us would appreciate you taking the time to illuminate me and others as to what this means. DISM reports an error but the CBS.log says there is no corruption. Once again, many of us would appreciate someone ACTUALLY addressing why this is the case rather than than posts which relate to suppositions, conjecture and speculation. Again: What does this mean to real users rather than a response with something like "imagine that 10,000 computers are damaged"?

I will be anxiously awaiting your analysis and answer.

It could be one of the generic drivers included within Windows 8 (at least I think that's how it works, please correct me if I'm wrong, as I know in Win 7 came the feature of generic drivers included in Windows to auto recognize devices, but I'm not sure if these are physically included or downloaded from Windows Update upon attachment).

CNBJ2530.DPB  is the part of a Canon printer driver.   In fact it is a 3-rd party program.

But OEM vendors may implant it by default.