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.

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. If I can get caught up, I will try the ProcMon PD/PR procedure described in http://chentiangemalc.wordpress.com/2014/04/03/case-of-the-kb2919355-installation-failure-windows-8-1-update-1/ to see if anything interesting pops up. It is the only other persistent error that I am seeing other than Windows Update Troubleshooter reporting RC_DataStore ErrorCode: 0x80070057, a symptom that Level 2 indicated was not germane to this problem.

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. Some people have had success in resolving KB2919355 install issues using the tips provided in this and other forums but for others the only sure approach is to rebuild the system, something that Microsoft recognizes is not a good option. Level 2 said a startup repair using Win 8.1 media has not been particularly successful. I was also advised that there are reports of issues after KB2919355 installed, including boot problems, printer driver conflicts and problems launching the Windows Store app. The implication was that Microsoft may withdraw KB2919355 until a stable version is developed. At this point I am going to take Microsoft's advice and bypass KB2919355. If I get a chance I will clone the failing harddrive and see if rolling back my system drive to April 9th makes a difference. The laptop that successfully installed KB2919355 had only a driver upgraded between April 9th and May 3th (travelling). The laptop that cannot install KB2919355 had a significant amount of Windows Update in that period.

Could some kind of SSD issue be the problem? I was wondering the same thing...

Could some kind of SSD issue be the problem? Or what about UEFI and GPT? http://msdn.microsoft.com/en-us/library/windows/hardware/dn640535(v=vs.85).aspx

When I run DISM.exe /Online /Cleanup-image /Restorehealth I get error code 0x800f081f. I did come across one interesting item though: I have a 3rd computer, a desktop, that I seldom use but decided to go ahead and install the updates. It also failed with the same errors. Of the 3 computers I have with 8.1, the two that failed the update both have SSD's. Could some kind of SSD issue be the problem?

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-23T15:45:20+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.

If I can get caught up, I will try the ProcMon PD/PR procedure described in http://chentiangemalc.wordpress.com/2014/04/03/case-of-the-kb2919355-installation-failure-windows-8-1-update-1/ to see if anything interesting pops up. It is the only other persistent error that I am seeing other than Windows Update Troubleshooter reporting RC_DataStore ErrorCode: 0x80070057, a symptom that Level 2 indicated was not germane to this problem.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2014-05-23T15:38:00+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.

Some people have had success in resolving KB2919355 install issues using the tips provided in this and other forums but for others the only sure approach is to rebuild the system, something that Microsoft recognizes is not a good option. Level 2 said a startup repair using Win 8.1 media has not been particularly successful. I was also advised that there are reports of issues after KB2919355 installed, including boot problems, printer driver conflicts and problems launching the Windows Store app. The implication was that Microsoft may withdraw KB2919355 until a stable version is developed.

At this point I am going to take Microsoft's advice and bypass KB2919355. If I get a chance I will clone the failing harddrive and see if rolling back my system drive to April 9th makes a difference. The laptop that successfully installed KB2919355 had only a driver upgraded between April 9th and May 3th (travelling). The laptop that cannot install KB2919355 had a significant amount of Windows Update in that period.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2014-05-23T14:09:16+00:00

Could some kind of SSD issue be the problem?

I was wondering the same thing...
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2014-05-23T13:45:40+00:00

Could some kind of SSD issue be the problem?

Or what about UEFI and GPT?

http://msdn.microsoft.com/en-us/library/windows/hardware/dn640535(v=vs.85).aspx
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2014-05-23T09:46:04+00:00

When I run DISM.exe /Online /Cleanup-image /Restorehealth I get error code 0x800f081f.

I did come across one interesting item though:

I have a 3rd computer, a desktop, that I seldom use but decided to go ahead and install the updates. It also failed with the same errors. Of the 3 computers I have with 8.1, the two that failed the update both have SSD's.

Could some kind of SSD issue be the problem?
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments