Error: 0x800F0922 when installing KB 2919355

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).

If /restorehealth came back clean, then your customer may [I say this gingerly] not have to do a repair install.  This was the only thread, out of the 6 that are dedicated to KB2919355 errors, that I didn't originally post this tutorial on, as from the sound of the posts when I originally read through, it didn't appear to be a system file and component store corruption issue.  

However, when I started seeing posts a few days ago about dism returning errors, I figured I should at least post the two tutorials on this thread in case anyone posting here hadn't come across the other 5. From experience on the other 5 threads, it appears that a repair install always fixes the problem [again, please don't confuse this with Refresh/Reset, and do not follow any instructions by Microsoft to do so, as it creates more problems than it solves and should never be used to troubleshoot an issue].  There have been mixed reviews about users' experiences with Microsoft remote support, and it either goes exceptionally well with Microsoft support fixing the issue, or as the user on the previous page posted, it goes horrendously wrong.  If an experience does go wrong and you're essentially told you're screwed by Microsoft Support, please inform one of the moderators (I'd recommend Ms. Bradley who posted above), giving them all identifying information for the support incident (case number, rep ID, rep name, etc.).

EDIT:

In regards to the Windows 8.1 installation files, upon upgrading from 8 to 8.1, a user would have had to manually select the option to install later and save the installation media to a USB drive or ISO format.  Many users never realized 8.1 is actually an entirely different OS, believing it to be an "update", so many (by no fault of their own) never realized they could create an ISO or realized they would need it at some point.  The only way to get the 8.1 ISO now (as it's not sold) is to either borrow a copy from a friend or co-worker and make a copy or download from a software forum and thoroughly search it for malware before using it. Users will need to make sure they obtain one that is for their version and architecture or they can download an AIO with multiple versions and architectures.  A user will also need to google the generic product key for their version [architecture does't matter], as it will be needed to access the installer.

I didn't get to the repair install, so nothing happened. By the time I found your post I had already worked on this system for several hours covering two days. I still have an open ticket for this customer so if MS support does not get it installed as some other people have stated happened I will run the repair install.

I did check for the 8.1 installation media previously downloaded by the customer but it is no where to be found on his system.

So if needed I will download and run the steps you outlined above.

When I ran all of the other steps (DSIM, sfc) they all came back clean so hopefully the repair install will work if I need to do that if MS support does not succeed.