Error: 0x800F0922 when installing KB 2919355

Anonymous
2014-05-14T19:23:49+00:00

This error may appear for multiple reasons. Some common causes are VPN clients and an unexpected System Reserved Partition size.

Try removing any VPN Clients and attempt the update again.

You might be able to fix this problem by using third-party software to increase the size of the System Reserved partition.

If you have tried both solutions and you still experience Error 0x800F0922 please contact Microsoft Support so that we can further investigate your issue.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

178 answers

Sort by: Most helpful
  1. Anonymous
    2014-06-03T01:02:37+00:00

    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.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2014-06-03T00:49:14+00:00

    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?

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2014-06-02T22:10:43+00:00

    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.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2014-06-02T22:03:03+00:00

    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.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2014-06-02T14:02:08+00:00

    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.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments