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: Oldest
  1. Anonymous
    2014-06-03T04:48:50+00:00

    I apologize that I came across as implying you were irresponsible, as this was not my intent in the slightest and was no where in the realm of what I was trying to convey.

    My point is that anyone who buys a device that allows the customization of it's OS by installing apps/software or by altering settings has a personal responsibility to understand the risks of doing such, whether these risks are minute and unlikely or whether they're serious and probable.  As an end user, we must own our own actions within a device's OS or firmware, and when problems arise from our actions within the OS, regardless if those problems arise out of our direct use of the OS/Firmware or indirectly through a manufacturer's update that we install upon our device, we are responsible for making sure we fix any issues that arise from our actions within the devices OS or firmware.  This does not absolve a manufacturer [such as Microsoft in this instance] of responsibility on their end, but maintains that every user must take personal responsibility for their own actions within an OS/Firmware and should a problem, issue, or error arise out of such actions, it is our responsibility to make an effort to research a solution and not expect anyone else to fix our device for us.  I call this having personal responsibility, however others [possibly yourself] may label this by a different name..

    Preferring Windows 7 over 8.1 is a personal preference and no one is wrong if they should choose to revert back, however if it is done because of issues an end user feels is unresolved within 8.1, it doesn't help the user to fix whatever the core issue is they're having problems with.  While you did choose to reinstall 7, had the same amount of time been used performing a repair install of 8.1, it would have solved the issue and saved time by preventing the reinstall of all software you use.  While I do understand your frustration for reverting back to Windows 7, this doesn't solve the problem you were having, nor will it solve anyone elses.  

    It comes down to wanting to solve the issue or create a bigger problem by wiping the drive, installing 7, going through the OEM driver installs, restarting after each one, installing Internet Security software, restarting, installing the hundreds of windows 7 updates, restarting multiple times, then finally reinstalling any software and restarting after each individual install.  All told, a clean install takes a minimum of one day to do properly, and that's without installing any software.  Which is why I view this as an irrational and illogical response to the KB2919355 issue.  It doesn't solve the problem and creates massive problems and even bigger inconveniences when all that was needed to begin with was a 60 - 90 min repair install. Due to this, I would discourage any and all from taking such a drastic, time wasting route that will not solve the issue, especially when in less time a repair install can be completed and KB2919355 installed successfully.

    Also, Windows Update was never the problem with the KB2919355 update, the update package was.

    Further more, from your response:

    "...they [MS Support]tried and gave me their answer. I don't really care what the answer is - I have a job to do and my tool broke so I made another tool that is less inconvenient." 

    I infer a person that isn't worth the time to help because they refuse to help themselves and have already made their mind up based upon inaccuracies, assumptions, and rhetoric.  If you care to help yourself fix the problem, read back through this thread an you'll find a tutorial to help you, but I see no need to offer any help after this due to " I don't really care what the answer is..."; if you don't care what the answer is, I don't care enough to try helping you find the answer.  Best of luck to you :)

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-06-03T05:33:43+00:00

    JW, this is merely a security update.  A patch.  One that shouldn't demand a complete rebuild.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-06-03T05:38:02+00:00

    It's for this reason that I'm asking Microsoft to release media.  I have a better solution.  Asking Microsoft to do the right thing and fix the problem. 

    Asking consumers to jump through these hoops, compute sha1 values?  I'm sorry this isn't the TechNet forums, this is the answer consumer forums.  If it takes these level to service this operating system then it's not consumer friendly.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2014-06-03T14:11:48+00:00

    It's for this reason that I'm asking Microsoft to release media.  I have a better solution.  Asking Microsoft to do the right thing and fix the problem. 

    Asking consumers to jump through these hoops, compute sha1 values?  I'm sorry this isn't the TechNet forums, this is the answer consumer forums.  If it takes these level to service this operating system then it's not consumer friendly.

    Thank you Susan!  There are too many different UEFI configurations out there to deploy Windows 8.1 without ready access to Media for licensed users.  For the fortunate, ie. those that Microsoft took into account when they developed and tested?  the update, it may work with minimum damage.  For the rest, they wind up with a corrupted partition structure or corrupted operating system files that cannot be easily repaired.  The Windows ecosystem is not the like the Apple IOS ecosystem.  We can't do things the way they do.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2014-06-03T15:25:29+00:00

    That's EXACTLY what I said in my post. Please see below since you obviously didn't bother reading what was actually written...

    "It comes down to wanting to solve the issue orcreate a bigger problem *by wiping the drive, installing 7, going through the OEM driver installs, restarting after each one, installing Internet Security software, restarting, installing the hundreds of windows 7 updates, restarting multiple times, then finally reinstalling any software and restarting after each individual install.  All told, a clean install takes a minimum of one day to do properly, and that's without installing any software.*Which is why I view this as an irrational and illogical response to the KB2919355 issue."

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments