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.

If I had the 8.1 media I would probably just start over, as *355 continues to fail on two of my computers. But like most, the original 8.0 and 8.1 upgrade were done by download, so I don't even have that option. As both of the computers I have that will not install the patch are running off of SSD's, I am suspecting that is at least part of the issue. At first I thought it might have been an error when the SSD was cloned to replace the hard drive, but on the 2nd machine the entire install of 8.0 and 8.1 was all done with the existing blank SSD already in place.

Although Microsoft Level 2 downplayed issues with the Recovery Partition or EFI System Partition as a root cause, I am seeing persistent KB2961908 install failures with error 0x800f0922. It appears that this fixes is related to noncompliant UEFI modules and update dbupdate.bin and dbxupdate.bin in C:\Windows\System32\SecureBootUpdates. Same here, it takes forever to install (or at least not install) something like a 29kB update, and it fails every time. Like -355, I've hidden the update until Microsoft can figure out what's wrong with their product.

Give Linux Mint a try. It is based on Ubuntu. I have installed on a few old XP laptops including an Acer Netbook. They are working much better than they ever did!

Other than Apple, what is the most viable OS competition to Windows? Linux? Based on my experiences with this update, I am ready and eager to switch to something that actually works. Thoughts?

@NH905, that is the most reasonable answer from level 2. Why cannot Microsoft publicly acknowledge this and put an end to users' agony and wasted time probably in the tens of thousands of hours. Till next month;)

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-05-25T17:56:10+00:00

If I had the 8.1 media I would probably just start over, as *355 continues to fail on two of my computers. But like most, the original 8.0 and 8.1 upgrade were done by download, so I don't even have that option.

As both of the computers I have that will not install the patch are running off of SSD's, I am suspecting that is at least part of the issue. At first I thought it might have been an error when the SSD was cloned to replace the hard drive, but on the 2nd machine the entire install of 8.0 and 8.1 was all done with the existing blank SSD already in place.
Was this answer helpful?

0 comments No comments
Anonymous

2014-05-25T09:32:11+00:00

Although Microsoft Level 2 downplayed issues with the Recovery Partition or EFI System Partition as a root cause, I am seeing persistent KB2961908 install failures with error 0x800f0922. It appears that this fixes is related to noncompliant UEFI modules and update dbupdate.bin and dbxupdate.bin in C:\Windows\System32\SecureBootUpdates.

Same here, it takes forever to install (or at least not install) something like a 29kB update, and it fails every time. Like -355, I've hidden the update until Microsoft can figure out what's wrong with their product.
Was this answer helpful?

0 comments No comments
Anonymous

2014-05-23T17:23:38+00:00

Give Linux Mint a try. It is based on Ubuntu. I have installed on a few old XP laptops including an Acer Netbook. They are working much better than they ever did!
Was this answer helpful?

0 comments No comments
Anonymous

2014-05-23T17:17:57+00:00

Other than Apple, what is the most viable OS competition to Windows? Linux? Based on my experiences with this update, I am ready and eager to switch to something that actually works. Thoughts?
Was this answer helpful?

0 comments No comments
Anonymous

2014-05-23T17:09:58+00:00

@NH905, that is the most reasonable answer from level 2. Why cannot Microsoft publicly acknowledge this and put an end to users' agony and wasted time probably in the tens of thousands of hours.

Till next month;)
Was this answer helpful?

0 comments No comments