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. 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 . Tap or click Change PC settings , and then Update and recovery . 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.

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!

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!

I too had the unsuccessful update on my brand new Asus M31AD (Windows 8.1 x64) preinstalled. errorcode: 800F0922 what can I do?

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

Robert, although I appreciate the frustration that has been expressed, I find your posts quite useful. I have tried many of the suggestions proposed by you and others. Unfortunately, I am one of those where there is no 'smoking gun' - no error code and no obvious errors reported in the logs. I am also getting error 0x800f0922 trying to install KB2961908 which may or may not be related - I have a ProcMon trace that I need to analyse. I am trying to become proficient in using ProcMon. It has a way to trace events early in the boot process which may help identify why the changes are being rolled back, although I wonder if the number of reboots will result in lost trace information. I have contacted the folks at Defrag Tools (they ran a number of tutorials on ProcMon) about using Update 1 as a real-life problem determination case study but have not heard back. I have a clone of the failing system and plan to try a repair install using a recimg created from a laptop where Update 1 successfully installed. I can also revert the system partition back to April 9th before the trouble happened to see if KB2919355 will install. I suspect the recovery partition on the failing laptop has been corrupted - when I try to create a recovery backup, I do not get the option of including the fully recovery image in the backup. Unfortunately I simply do not have the block of time required to do this testing - I keep hoping Microsoft will pull the rabbit out of the hat. Now that the cut-off for fixes is once again looming, I am composing a strongly worded email to the Director of Public Relations at Microsoft about the poor communications and support . Microsoft needs to get ahead of this issue before it spirals out of control.

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

Anonymous

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.

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.
Tap or click Change PC settings, and then Update and recovery.
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.

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

998 answers

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
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
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
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
Anonymous

2014-06-07T14:06:41+00:00

Robert, although I appreciate the frustration that has been expressed, I find your posts quite useful. I have tried many of the suggestions proposed by you and others. Unfortunately, I am one of those where there is no 'smoking gun' - no error code and no obvious errors reported in the logs. I am also getting error 0x800f0922 trying to install KB2961908 which may or may not be related - I have a ProcMon trace that I need to analyse.

I am trying to become proficient in using ProcMon. It has a way to trace events early in the boot process which may help identify why the changes are being rolled back, although I wonder if the number of reboots will result in lost trace information. I have contacted the folks at Defrag Tools (they ran a number of tutorials on ProcMon) about using Update 1 as a real-life problem determination case study but have not heard back.

I have a clone of the failing system and plan to try a repair install using a recimg created from a laptop where Update 1 successfully installed. I can also revert the system partition back to April 9th before the trouble happened to see if KB2919355 will install. I suspect the recovery partition on the failing laptop has been corrupted - when I try to create a recovery backup, I do not get the option of including the fully recovery image in the backup. Unfortunately I simply do not have the block of time required to do this testing - I keep hoping Microsoft will pull the rabbit out of the hat.

Now that the cut-off for fixes is once again looming, I am composing a strongly worded email to the Director of Public Relations at Microsoft about the poor communications and support . Microsoft needs to get ahead of this issue before it spirals out of control.
Was this answer helpful?

0 comments No comments