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: Newest
  1. Anonymous
    2014-05-16T19:11:12+00:00

    You should not. It should be a free call.

    Shoulda woulda coulda.

    ¯\_(⊙︿⊙)_/¯ Microsoft.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-05-16T19:07:41+00:00

    Removing and reinstalling my VPN client or adjusting the partition size may work fine on a single workstation, but it will definitely not work across the board in a large environment.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-05-16T18:49:51+00:00

    I too have been getting the error code 800F0922 when trying to install update KB2919355 on my ASUS computer with Windows 8.1. I have tried both using the update server and manually downloading the update and installing it. My most recent attempt was today, May 16 2014 (2:30 pm EDT). I get the same error code each time. 

    I do not have a third party VPN client installed, though I noticed that apparently Windows 8.1 can establish a VPN connection through the Network and Internet section of the control panel.

    I checked the various partitions from free space - there are 4 partitions:

    • EFI System Partition - 100MB - 100% free
    • Recovery Partition - 900MB - 100% free
    • Recovery Partition - 29.01GB - 100% free
    • C: - 444.65 GB - 77% free

    The installation process under Windows completes with no errors. The machine then restarts and displays screen stating "Working on updates XX% complete Don't turn off your computer". It gets up to about 30-35% and then restarts again. The next screen that comes up is "Getting WIndows ready Don't turn off your computer" which shortly changes to the previous "Working on updates..." screen and starts at about 35%. It then proceeds to 99% complete. Then up comes the infamous screen "We couldn't complete the updates Undoing changes Don't turn off your computer"

    I've been trying to get this update installed off and on for the past month with no success. Can you provide some help!

    John

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2014-05-16T18:46:12+00:00

    I continue to get error 0x800F0922 while attempting to install KB2919355.

    I don't use a VPN Client and I have tried all the solutions listed in the 116+ pages of the previous thread over the past several weeks, with the exception of increasing the size of the “System Reserved Partition”.  Using the diskmgmt.msc reveals that my laptop (Lenovo T430 running Win 8.1 Pro x64) does not have a “System Reserved Partition”, per se. The closest I get are one “EFI System Partition” and 3 “Recovery Partitions” – all of which are 100% unused.  Is this the problem?  Do I need to create a “System Reserved Partition”?  And if so, how does one go about doing that?

    Similar to the situation mentioned by others, the KB2919355 update goes to 99% before rolling back.  All other MS updates received before and after this ugly brute have been installed without issue – including the update from Windows 8 to 8.1.  However, from the standpoint of time logged in attempting to resolve this failed install, Win 8.1 is the most expensive OS ever encountered by this sorry individual; and at this juncture, any and all (new) suggestions are welcomed.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2014-05-16T17:03:17+00:00

    You should not. It should be a free call.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments