Error: 0x800F0922 when installing KB 2919355

Just to clarify, you are probably inferring that from the email address I use.  I'm not a "systems administrator for a major telecommunications company".

Actually pacbell.net is merely my eons old email address that I pride myself that yes, you can still email me at an email address I used back in the nntp era.  I am not a Sysadmin for a Telecommunications company.

Indeed the reason I am asking for your support case number is so that I can pass it along and ensure that the right hand of Microsoft understands that the left hand of Microsoft is totally dropping the ball.

Hello, RSloan60

     I suspect the frustration caused by your problems with the "8.1.1 update" (KB2919355) may've caused

you to overlook Community Moderator & MVP Susan Bradley's June 1 request for your Microsoft Support case #.  Ms. Bradley, systems administrator for a major telecommunications company, is a world-renowned patch management expert, one of the moderators of PatchManagement.org (among the most-respected peer-to-peer listserv's, or e-mail "lists", about patching, aka updating), the author of a regular column on patching for the "Windows Secrets" newsletter, and a Answers Community/Windows Forum member whose posts have helped many, many folks with a variety of problems, update-related and otherwise.  Her standing is such that when she speaks on an issue, Microsoft has a tendency to listen to what she has to say.  The reason she's asked for your case # is almost certainly because the level of support you've apparently received is not acceptable, and her rapport with the folks in Redmond will allow her to investigate why you were told what you've reported.  I'd respectfully suggest that if you'll post your case # in a reply to her June 1 post on pg. 8 of this thread (simply navigate to that page & click "Reply" under her post), you may find that she'll be able to help you get a better resolution.

Well the customer has another callback scheduled for Tues from MS support. I am going to hold off on suggesting and doing the repair install to see if MS will do it. The customer is not sure if the callback is for another Level 2 tech or Level 3 (if they have Lvl 3) so I will wait and see.

Just wanted to share something I've encountered on my PC...

Yesterday, due to issues not resulting from KB2919355, I ended up simply wiping the drive and applying a WIM I had made about a month ago.  I ran all of my commands from a bat within WinPE (defrag, chkdsk, sfc), however forgot I couldn't run /startcomponentcleanup and /restorehealth in an offline environment (I could have ran them by mounting the WIM prior to applying it, however it's a 331GB WIM and would have taken a ridiculously long time to mount, unmount and commit changes, then applying it) .

After I logged in once the restore was done, I did my normal pre-windows update steps (imported my CIS configuration. updated anti-virus, etc.) and completely forgot to run /startcomponentcleanup and /restorehealth.  So I go about installing updates and finally get to KB2919355, which installed fine.  Upon restarting, one of the smaller updates included in it's package hadn't been able to install, so I clicked install and it returned two different errors (80070005 and another one), telling me another installation was in progress. Restarted multiple times, still a no go.  Granted, I could fix the problem by deleting the Windows Update cache directories, however doing so would delete the list of updates installed under "update history", which is something I'd like to avoid.  Although I'm currently running /startcomponentcleanup, which will be followed by /restorehealth, this demonstrates why the component cleanup and restore health commands are vital prior (not after) to running Windows Update on a restored or install repaired system in order to perform a successful update.

Have you attempted to run /restorehealth, and if so, has it returned errors?  If it has, you will have to do a repair install (NOT a Refresh/Reset, as this is not the same as a repair install, nor are these two options [Refresh/Reset] ever needed).