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.

My error code is 0x8007000D - same issue.

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. I also have 8.1 Pro with Media Center. This high end Alienware machine does not have an SSD. I have tried to install this "update" probably around 20 times by now. I'm slowly wearing out my hard drive. I give up! Another flaw of these failures, is that it wipes out my history. I can't restore to when the machine was working well, and I refuse to start over!

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.

I had a chat with Microsoft Level 2 support this morning. Microsoft is very aware of the KB2919355 issue and is working diligently to find the root cause(s) and deliver fixes. At this point, the only recommendation is to hide KB2919355 in Windows Update until such time as a fix is released. That's my approach for now. I can't afford to risk bricking my laptop with all sorts of attempts at getting this thing to install, I don't have any media (or a DVD drive) to do a full install from, and hopefully once Microsoft's corporate customers (or at least those foolish enough to have moved to Win8) start hitting this same problem in August, they'll be forced to do something about it.

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-26T16:13:44+00:00

My error code is 0x8007000D - same issue.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2014-05-26T12:13:03+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.

I also have 8.1 Pro with Media Center. This high end Alienware machine does not have an SSD. I have tried to install this "update" probably around 20 times by now. I'm slowly wearing out my hard drive.

I give up!

Another flaw of these failures, is that it wipes out my history. I can't restore to when the machine was working well, and I refuse to start over!
Was this answer helpful?

0 comments No comments
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-25T09:29:04+00:00

I had a chat with Microsoft Level 2 support this morning. Microsoft is very aware of the KB2919355 issue and is working diligently to find the root cause(s) and deliver fixes. At this point, the only recommendation is to hide KB2919355 in Windows Update until such time as a fix is released.

That's my approach for now. I can't afford to risk bricking my laptop with all sorts of attempts at getting this thing to install, I don't have any media (or a DVD drive) to do a full install from, and hopefully once Microsoft's corporate customers (or at least those foolish enough to have moved to Win8) start hitting this same problem in August, they'll be forced to do something about it.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments