Error: 0x800F0922 when installing KB 2919355

I know the following to solve all KB2919355 issues, and pasted below are the two tutorials.  The first is one that was written to get rid of the component store corruption that 2919355 causes, of which the computer you're working on has.  You will need to do a repair install (tutorial at the bottom of Tutorial 1).  The second tutorial is how to get 2919355 installed after the repair install, however, you should be able to install 2919355 fine after the repair install.  If it still fails, then follow the second tutorial.

Tutorial 1

The following fixes the Component Store Corruption KB2919355 AND Windows Update causes

The following DISM commands must be given in the chronological sequential order of:

First

(Fixes Component Store Corruption; Should 1 or 2 fail with an error, rerun. If either fails a second time, you will need to do a repair install, see tutorial at bottom):

1.dism /online /cleanup-image /startcomponentcleanup

2. dism /online /cleanup-image /restorehealth

3. Restart

4. sfc /scannow

5. Restart

Second:

("Resets" Windows Update; however, if you attempt KB2919355 again through Windows Update, the same corruption will occur again)

1. Create bat and run as ADMIN:

net stop wuauserv

rmdir /s /q C:\Windows\SoftwareDistribution\DataStore

rmdir /s /q C:\Windows\SoftwareDistribution\Download

net start wuauserv

2. Restart

‪#‎ WARNING‬:

this was not a fast process... component cleanup took almost 5 hours. Prior to the above sequential steps, I did an install repair (used iso to "upgrade" Win 8.1 Pro to Win 8.1 Pro) as a last ditch effort (after half a day of researching a fix and finding none) to get rid of the corruption... it didn't solve it btw. The insane amount of time could have been due to the install repair, or it could have been because of whatever ‪#‎WindowsUpdate‬ mucked up the first time around trying to install this update (this will become known after another user affected by the corruption causingKB2919355 completes the steps).

‪#‎ ADVICE‬:

run the commands from a bat for an unattended fix. For whatever reason, if these commands are run, but not in chronological sequence, the corruption will remain.

...Now, back to the update ‪#‎Microsoft‬ mucked up (KB2919355)... it still fails after the above lol Bright side: no more corruption in Component Store =] lol

ADVICE:

Download the updates included in KB2919355 individually and install... or do as old Van Winkle did and find a tree.

***If the above fails to get rid of the Component Store Corruption (steps 1,2, or 4fail), then an install repair (upgrade to your same version of windows) will be required.  Although this repair does not eliminate the corruption, if you're unable to fix the corruption using the method above. then the install repair is replacing something that is needed to fix the corruption but which is not able to pro vide a fix on it's own. Also, download [search] "Microsoft Safety Scanner" from the Microsoft website (I apologize, as I don't remember the thread I found the link on) and run it in full mode either way.***

Tutorial for Repair Install "upgrade"

http://www.eightforums.com/tutorials/26095-repair-install-windows-8-a.html

• Once KB2919355 causes corruption to the extent that /restorehealth no longer operates without errors, there is nothing further than can be done to repair the corruption, except a Repair Install.  DISM /restorehealth was designed to fix component store corruption and is the only application able to do so. Windows Update and KB2919355 causes system corruption to such an extent that using /source and pointing to the installation media or a working windows 8 installtion without corruption does nothing and /restorehealth still fails.
• Once the repair install has completed, run windows update and install the 46 (possibly more depending on configuration) updates. Restart when told to do so.  You may have to restart several times, even though Windows may not direct you to do so.  If you attempt to install additional updates, especially the KB2919355 package update, and receive an error code that is for an error resulting from updates currently being installed (or something to that effect), restart the computer.  It took 3 restarts for Windows to install the 46 updates in 3 stages.  It took an additional 2 (possibly three) restarts to install all updates within KB2919355.DO NOTuse the standalone versions once you do a repair install.  Attempt to do all via Windows Update.  If you're receiving errors other than ones that relate to Windows attempting to install additional updates or installations are in progress, etc. then attempt tutorial 2.
• Upon logging in after the Repair Install andbefore running Windows Update:
  • Run /startcomponentcleanup
  • restart
  • run /restorehealth
  • restart
  • run /scannow
    • If it completes with errors and directs you to the CBS log even though DISM gave no errors, check the CBS log to see if file permissions are the issue and is what is preventing SFC from accessing those files.  If this is the problem, take ownership of the files in question, and give System full permissions.  It appears the corruption can cause files to lose their ownership, preventing SFC from accessing those particular file and will through an error due to it.
  • restart

DO NOT, I REPEAT, DO NOT REFRESH/RESET YOUR PC.

DISCLAIMERMicrosoft will deny this update caused corruption within end user's systems and will blame it on everything else but components of their own OS, most especially Windows Update.  The only problem with this: thousands of users have reported massive corruption not only to the Component Store, but also within the DISM and System File Checker utilities.  Microsoft closed the two longest running threads on the corruption caused by KB2919355, one 116 pages long, the other 103... all the while telling users to run /scanhealth /restorehealth maybe a /startcomponentrepair in their somewhere, but never in the order which they must be run, or how to explain DISM /restorehealth corruption errors when being used with /source and the source was a mounted install.wim, as well as a VM win 8.1 with no corruption within it's component store.**

Tutorial 2

***KB2919355 Fix that WILL allow the install of KB2919355***

As many discoveries have been made, I discovered this accidentally. and quite by coincidence... 

In order for users, who've been plagued by errors and file corruption, to get a successful completion of KB2919355, all that's needed is to run the 8.1 upgrade installer, and when the 8.1 installer goes to the wait screen after entering the generic product key, start Windows Update for the install of KB2919355

EDIT: It appears, from the input of other users, one must FIRST install the 5 standalone updates included within the Windows Update KB2919355 package, you will then need to restart after the fifth and final standalone, then use Windows Update to install KB2919355 (do not use the standalone installer for KB2919355... use Windows Update). The steps listed below may not be needed for a successful KB2919355 issue, as although I had to do this after the first repair install I did, the second did not require it and updated flawlessly.

Steps

1. Run the Windows 8.1 installer from within Windows, as if you're going to do an install repair "upgrade".
2. Enter the generic product key, and upon clicking next, the installer will say wait...
3. Give the installer about 5 minutes, then start Windows Update (it should show the KB2919355 update), and click install.
4. Windows Update will begin downloading the update... if you have a Windows Update cache problem that causes the speed and percentage to remain at zero, don't worry about it and get the update installed first, then you can clear the cache and remove the directories afterwards.
5. The install may fail, don't worry... simply hit install again, making sure the 8.1 installer screen is still on the "wait" screen, as whatever the installer is doing during the "wait" screen is what makes the KB2919355 install possible.
6. KB2919355 should install and Windows Update should request you to restart... simply do so without cancelling the 8.1 installer.  Windows will finalize the update during the shutdown and restart processes.
7. Upon rebooting into Windows, you will have a multitude of additional updates that will need to be installed (around 10, give or take a few), and you can verify the install of KB2919355 by going to "view installed updates"

Do exactly what Tutorial 1 says. I had to do a repair install using an ISO of 8.1 I found elsewhere. This can be from someone who has saved the file when they had the chance when updating from 8.0 to 8.1 via the Windows Store. I have Windows 8.0 preinstalled when I purchased my laptop last year and could not use the update from Microsoft's website to do a repair install, but with this ISO from elsewhere that someone saved prior to updating worked perfectly. 

I suggest using "https://technet.microsoft.com/en-US/subscriptions/securedownloads/hh442904" to verify the sha1 of the iso you download. Check all of them for a match. If there's no match I would look for another.

After the repair install I followed:

• Upon logging in after the Repair Install and before running Windows Update:
  • Run /startcomponentcleanup
  • restart
  • run /restorehealth
  • restart
  • run /scannow
    • If it completes with errors and directs you to the CBS log even though DISM gave no errors, check the CBS log to see if file permissions are the issue and is what is preventing SFC from accessing those files.  If this is the problem, take ownership of the files in question, and give System full permissions.  It appears the corruption can cause files to lose their ownership, preventing SFC from accessing those particular file and will through an error due to it.
  • restart

Then I ran Windows Update, not the stand alone, but the Windows Update program. It had everything installed already when I checked for updates and I verified in the installed log that update KB2919355 is installed. It is weird though, it says it was installed on March...I'm not sure why, but I do have all the KB2919355 features I believe. The Windows store icon is on the bottom task bar and on the home menu where the tiles are I do have the Power and Search buttons in the right corner.

Also I noticed that the high disk usage problem is gone. I cannot confirm this as of now since I just literally got done doing the repair install and updating.

Hopefully this feedback helps everyone and thanks JW0914 for the tutorials and fix!

jW with all due respect, these tutorials involve potentially dubious locations and questionable keys.  It is not an official solution.

these folks impacted deserve a better support experience and a better official solution.

The eula doesn't say use at your own risk.

There have been multiple tutorials posted multiple times with the exact steps needed to solve the corruption and get 2919355 installed.  I've posted tutorials that work in all 6 threads dedicated to the 6 main errors experienced and in many I've posted the tutorials multiple times, and this isn't including the posts by others saying the same thing or offering the same steps to follow.

While this may be the first time many users [the average user] are experiencing anything like this, it only requires common sense to see the same worthless, cookie cutter responses from Microsoft do not solve anything and if followed, many will actually make things much worse (in other words, it doesn't take a genius to look at the posts by Microsoft employees in threads to see they're the same cookie cutter response over and over again, and then realize you should probably disregard all further mention of said responses/steps).  I may know more than the average user, but I'm not an expert... just as many seeking a solution are not.  What I see repeatedly though are people not only being told to a repair install and pretending like that was never even suggested, but are also being told by those of us who have done them that a repair install works, and still people ignore it (as you did in the previous thread for example).

All consumers should know, and if they didn't before, they got a rude awakening with this, that a device with a customizable OS comes with a use at your own risk and if something does screw up, you are the owner of said device and it is your responsibility to have personal responsibility for problems that occur with said devices and it is your responsibility to research solutions for said problems.

Most users are not computer savvy and are looking for a quick solution. Most of them have never experienced anything like this. They have simply had their machines configured to automatically download and install updates All of a sudden this is not happening so they are totally confused. They come here and are met with a number of "solutions", "fixes", "workarounds" and what have you offered by several hundred "experts". They are lost but who can blame them. Ergo, they express their frustration because the "help" is not provided in a manner they understand or consists of a number of posts from different people which purport to help but which can be a completely different approach to the problem.

1. Poster A says the problem is the remanants of anti-virus programs or using registry cleaners; or
2. Poster B says the problem is the fact the system was upgraded from Win XP, Win 7, etc.;
3. Poster C says the problem can be solved by running DISM commands; or
4. Poster D says a reinstall is in order; or
5. Poster E says to contact support which cannot solve the problem, or
6. Poster F says something completely different and refers to something called a repair/install or using Procmon, etc.  

In the meantime the user is totally confused. Why would you expect them not to be?

I'd be seriously surprised if the individual replies back with their case number, which is sad.  I wholly understand the frustration this user and others feel, as it took me several days to get KB2919355 installed, however a few users seem to want to express their frustration, but not make an effort to find a solution to whatever problem they're experiencing.  It's as if the person sees there's a thread on a forum that is about their problem, and instead of taking a few minutes to read the thread, instead choose to simply express their frustration and not seek help... which is quite baffling to me.