Error: 0x80070003 when installing KB 2919355

At this time this is my understanding:

KB2919355 has been revised to fix the main cause of failure, the corruption issue.  That's that clearcompression flag patch you see in the revised KB2919355.

Any of the other threads started to deal with the other known issues (see http://www.infoworld.com/t/microsoft-windows/microsoft-posts-tips-overcoming-windows-81-update-kb-2919355-errors-242603 for the links to posts in this forum) I do not see any action from said software company to fix these automatically.  I have been given no information that any automatic fix is coming.  As is stated in all of those links, if you are still impacted, you are informed to contact support directly.

That's the current "resolution" at this time.

On a similar note, may I share a support story?  Yesterday I had a problem updating my mini jambox speaker.  I called support.  Talked to a nice person who I told him all the steps I had done.  He said "yes, you've tried everything, let's get you with an escalation case".  I received a call back, from a equally nice person, who walked me through a factory reset.  The update to the Jambox then took this time.  I had to reset the device, but I lost no data.  Obviously a jambox speaker is not the same as a Windows 8.1 but I think the problem is exactly what you said at the end "the dynamics have changed and people have become accustomed to this sort of incompetence and it is what they expect from most businesses nowadays. "

I was shocked by my good experience of support with the Jambox device.  I shouldn't be shocked.  I should expect this from all my vendors.

No, I think you bring up extremely valid points and excellent questions.  

The system wide file corruption caused corruption to such a degree not just to the component store, but dism itself to the point that using the /source flag and pointing to either 8.1 installation media or a working 8.1 install did nothing to solve the dism generated errors and inability to fix component store corruption.  

The first repair install I did, I ran /startcomponentcleanup after Windows rebooted and the component cleanup took just shy of 5 hours... unheard of.

Ok thanks.

Does anyone have any information from the Great Software Company as to whether, when or if said company has a solution to this update failing to install on many computers? In addition, does anyone have any idea as to whether, when or if the aforesaid company intends to deal with the corruption or possibly false error messages (take your pick) which affect DISM /Restorehealth?

After next Tuesday (which will be the two month anniversary of this mess) will we still be receiving the same answers (which for the most part do not work) to the failed update and no answers to the issues related to the corruption or whatever else is causing DISM to be non-functional? 

The silence is the most troubling aspect of all of this. It is as if the company has decided to stuff cotton in its figurative ears and allows the "answers", "solutions" and "fixes" to be continued to be posted by the same people who have been posting the same thing since April 8th to no avail. This is surreal.  

Perhaps that is too much to ask on a forum dedicated to Microsoft products, and in particular to the category of issues related to updates to Windows 8.1. If so, I apologize for wasting everyone's time with this post as perhaps my expectations are well-beyond what the average user expects from a company which for the most part derives its income from selling operating systems. Again maybe the dynamics have changed and people have become accustomed to this sort of incompetence and it is what they expect from most businesses nowadays.

Thanks for taking the time to verify everything :)  I was wrong and will be editing my posts with the correct information. 

EDIT:

The one thing I did find a bit perplexing is during this repair install, 2919355 installed fine, no failures, no need to run the 8.1 installer to get it to install, it was flawless.  I remember reading a post on one of the tens of forums I tried to find a solution on that one individual had lost power, causing a dirty shutdown.  Following this, he was unable to install 2919355.  I know there were a few times I had to manually turn off my laptop after it had frozen for a half hour, however, it was never during the install of KB2919355.  This is the only difference that I can recall between last time and this time... do you know why this would cause an issue installing any update?

So here's the 11 updates post KB2919355:

2955164  May update rollup, non security,  needs 2919355 installed.  Not needed if you don't have 2919355 installed.

The below four updates are security updates that one receives when you don't have 2919355 installed. Once you do, they are offered again to now secure your system with post 2919355 fixes: 

KB2953522  MS14-029 IE (you get the prior one without KB2919355)

2920189  UEFI update  - again you get this before it’s applied

2926765  MS14-027 – Windows shell – again you get before 2919355 is applied

2962140  Juniper networks (get it pre 2919355)

These four security updates get offered to a system that does not have KB2919355 installed as well.  They are slightly different kb numbers reflecting that it’s a different update, but they are patching the same thing as the pre2919355 code.

Rest of the list are not security updates – thus do not leave machine in vulnerable condition.

2954879  update for .net native – not a security update

2939153  antimalware platform update needed post 2919355

2950153  WUSA freezes when you install an update – only needed post 2919355

2956575 Store and update client improvements – needed post 2919355

2958262  Compat update for Windows 8.1 – needed post 2919355

2965065  Latest version of bootmgr – again needed post 2919355

All of the seven non security updates – are only needed post 2919355.  The four security updates you receive them if you can't get 2919355 installed.

They aren’t holding anything back.  These are not needed on a pre2919355 platform.  Once you get KB2919355 installed then you get offered up what you need.