Error: We couldn’t complete the updates, Undoing changes. Don’t turn off your computer.

Anonymous
2014-05-14T19:34:39+00:00

This error may appear anytime a Windows Update fails. To investigate possible solutions, we need to start with the specific error code.

We can do this by viewing your update history.

  1. Swipe in from the right edge of the screen (or, if you're using a mouse, pointing to the lower-right corner of the screen and moving the mouse pointer up), and tap or click Settings.
  2. Tap or click Change PC settings, and then Update and recovery.
  3. Tap or click View your update history.

View failed update error code.

Please post here with your error code, so that the Community can try to help guide you appropriately.

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

998 answers

Sort by: Most helpful
  1. Anonymous
    2014-06-10T16:23:47+00:00

    There is no update history, doesn't record that there was an update attempted. I've manually tried the updates with suggested settings around a dozen times not including that times that it tries to update from the automatic software update settings in windows 8.1. the update always stops at 75% and after reboot it then it starts the recovery which it tries 2 more times each time rebooting before my logon screen comes back. One thing it always does is I loose my Internet explorer from my desktop icons and start screen, I have to go back and reset the microsoft default programs to get it back.

    I have a new Gateway with factory installed W8.1 Pro media center. This is my work PC and I need to fix the issue, ...is there a fix?  This thread is full of people with the same issue but I have yet to find a post that provides a solution.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-06-10T12:56:40+00:00

    After trying almost every suggestion at least once, I have decided not to try any DISM this, DISM that, procmon analysis. If Microsoft does not find a solution to the mess it created, I will perform a factory reset on my 6 month old Lonovo ultrabook, then aBay it. In the mean time I can be seen at an Apple store picking a MacBook Air!

    Man I hear you!

    I just tried UBUNTU 14.04 in one machine. Everything just worked! Now I'm down to 1 machine with the update problem. I'll give MICROSOFT just a little more time, before I nuke the drive, and put UBUNTU into it also.

    KB2919355 is a destructive update from ****. 2 machines took it, 1 machine damaged from multiple attempts, then took it, and one more machine still in limbo.

    No more DISM bull for me either!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-06-10T11:59:49+00:00

    After trying almost every suggestion at least once, I have decided not to try any DISM this, DISM that, procmon analysis.  If Microsoft does not find a solution to the mess it created, I will perform a factory reset on my 6 month old Lonovo ultrabook, then aBay it.  In the mean time I can be seen at an Apple store picking a MacBook Air!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-06-10T09:52:43+00:00

    I too had the unsuccessful update on my brand new Asus M31AD (Windows 8.1 x64) preinstalled. 

    errorcode: 800F0922

    what can I do?

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2014-06-07T15:38:39+00:00

    getting error 0x800f0922 trying to install KB2961908 which may or may not be related - I have a ProcMon trace that I need to analyse.

      

    Google could be the tool of choice for that one:

    C.f.

    Description of the update rollup of revoked noncompliant UEFI modules: May 13, 2014

    http://support.microsoft.com/kb/2961908/en-us

    Microsoft security advisory: Update to revoke noncompliant UEFI boot loader modules

    http://support.microsoft.com/kb/2871690/en-us

    (Google search for

        0x800f0922 update site:microsoft.com

    )

    <quotes>

    You receive a 0x800f0922 error when you try to install this security update

    Cause

    This error occurs because the installer for security update 2871690 incorrectly expects BitLocker to be installed.

    </quotes>

    They sound similar, with the later one now producing a previously undocumented error code, which without any more details I would have to guess was something of the nature of:  "Oops. Something's wrong."

    In fact, though, as I have mentioned before, the pattern of the code is documented

    http://support.microsoft.com/kb/938205/en-us

    <quote>

    0xf0900 CBS_E_XML_PARSER_FAILURE unexpected internal XML parser error.

    0xf0901 CBS_E_MANIFEST_VALIDATION_MULTIPLE_UPDATE_COMPONENT_ON_SAME_FAMILY_NOT_ALLOWED In a given package

    </quote>

    So a good guess IMO for a way to get more context about it would be to look in the CBS.log at the time that the update which reported the code was run.   If you had ProcMon running at the time, then that much better because then, to repeat my suggested procedure, you could infer the WriteFile which was responsible for the output of that CBS.log record and therefore have any other preceding ProcMon events as more context for that error event.  In particular, to support the hypothesis that your 0x800F0922  was related to the later (now diagnosed) one, I imagine that you would probably see a File access for a Bitlocker support file whose Result would be FILE NOT FOUND.   (For example.)   Etc.

    HTH

    Robert


    Was this answer helpful?

    0 comments No comments