Error: 0x800F0922 when installing KB 2919355

Just a heads up, I know nothing about VPNs or what options within Windows need to be set up to use them, so please keep this in mind with regards to advice I post.  This is the main reason I didn't originally post in this thread.

I'd be curious if a repair install would fix the issues users with VPNs are experiencing and would try it as it leaves everything in tact and at worst, if it doesn't fix the issue, the only thing lost is about an hour from start to finish.  It would take an additional 45 - 60 minutes to run the two dism commands and one sfc command, and then run windows update for the 46 then KB2919355.  

EDIT:

I just remembered you mentioned when MS ran /restorehealth it failed with errors...if /restorehealth is run a second time and returns errors, a repair install is the only way to fix this (technically you could spend hours going through the log and the component store to root out the corrupted component store files, however it's quicker and easier to just do a repair install which replaces all system files within the Windows folder.

You're having problems because you missed a step ;) You'll need to google "generic product key [your version of windows]".  You cannot use activation keys for the installer, you must use the generic keys Microsoft released.

My assumption here is that with the licensing structure change that came with the rollout of windows 8, microsoft was attempting to lock down their proprietary software and prevent users from being able to install Windows without first entering a valid product key in an effort to combat KMS Activators, which Microsoft has never been able to do with any degree of success.  However, a problem was discovered within the Windows 8 installer... upon a user installing windows 8 and activating it with their activation key, said activation key would no longer work in the installer and would return an error that it's not a valid product key.  Whether this is the actual reason or not, I'm not sure, however Microsoft did make generic keys readily available for Windows 8 after it's release.  Then when 8.1 was released, they released generic keys for it (as you cannot use product or activation keys for windows 8 to install 8.1 as 8.1 is an entirely separate OS, not an "update" as it's usually referred to as).  You can however use a Windows 8 activation key to activate 8.1, as Windows 8.1 is free and (at least to my knowledge) does not have it's own line of activation keys.

For some reason /restorehealth finally started coming back clean but then when MS support started working on it errors started popping up again. I missed some of the work they did so I'm not sure what they did that may have caused it. I will be contacting the customer this morning to see what ended up happening yesterday.

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

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.