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.

I'm not getting any error code. That's part of what makes this so frustrating!

Good luck. This issue has plagued users since the update was first made available on April 8th. The "team" has not had much success but let us hope they do in your situation.

Just got off the phone with another supervisor at Microsoft support. He was telling me I just need to download the 8.1 ISO. Once I explained to him that I had a OEM 8.0 key he told me he would elevate my case for review, not really sure what that means. Anyway he did say that Microsoft has a team working on the issue. Greg

DISM.exe /Online /Cleanup-image /Restorehealth It failed with an error 0x800f081f I have seen an implication that both it and ScanHealth may do the equivalent of CheckSUR. If that's the case, there may be extra logs in %windir%\Logs\CBS\ Also, I just found out that Powershell seems to have equivalent functionality (probably just a UI wrapper for it) which may be easier to use. At least it seemed easier to use the LogLevel and LogPath operands. <eg> http://technet.microsoft.com/library/2e9658bf-c013-4fd1-a981-b9242ba61d35(v=wps.630).aspx Yes Powershell has equivalent commands which perform the same function. I was able to install the KB2919355 update (after performing a manual fix of component store corruption) notwithstanding the fact that /RestoreHealth failed after the failed attempt to install the update and still fails with the 0x800f081f error via the command line AFTER the update. A review of the CBS.log indicates NO corruption notwithstanding the report from DISM which indicates there is a problem. This is indicative of the fact the update itself is corrupting the DISM command and perhaps resulting in a false error message. There is a thread about this on the community forums and elsewhere about the issue with no answer. A system restore to a point BEFORE the failed update results in no problems with /RestoreHealth which has been reported on this forum and others. This update apparently corrupts or at least results in a false error message. This particular issue appears to have been lost in the noise about the failed update itself.

DISM.exe /Online /Cleanup-image /Restorehealth It failed with an error 0x800f081f I have seen an implication that both it and ScanHealth may do the equivalent of CheckSUR. If that's the case, there may be extra logs in %windir%\Logs\CBS\ Also, I just found out that Powershell seems to have equivalent functionality (probably just a UI wrapper for it) which may be easier to use. At least it seemed easier to use the LogLevel and LogPath operands. <eg> http://technet.microsoft.com/library/2e9658bf-c013-4fd1-a981-b9242ba61d35(v=wps.630).aspx

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-20T01:06:55+00:00

I'm not getting any error code. That's part of what makes this so frustrating!
Was this answer helpful?

0 comments No comments
Anonymous

2014-05-20T01:02:35+00:00

Good luck. This issue has plagued users since the update was first made available on April 8th. The "team" has not had much success but let us hope they do in your situation.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2014-05-20T00:59:09+00:00

Just got off the phone with another supervisor at Microsoft support. He was telling me I just need to download the 8.1 ISO. Once I explained to him that I had a OEM 8.0 key he told me he would elevate my case for review, not really sure what that means.

Anyway he did say that Microsoft has a team working on the issue.

Greg
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2014-05-19T23:56:56+00:00

DISM.exe /Online /Cleanup-image /Restorehealth

It failed with an error 0x800f081f

I have seen an implication that both it and ScanHealth may do the equivalent of CheckSUR. If that's the case, there may be extra logs in %windir%\Logs\CBS\

Also, I just found out that Powershell seems to have equivalent functionality (probably just a UI wrapper for it) which may be easier to use. At least it seemed easier to use the LogLevel and LogPath operands. <eg>

http://technet.microsoft.com/library/2e9658bf-c013-4fd1-a981-b9242ba61d35(v=wps.630).aspx

Yes Powershell has equivalent commands which perform the same function. I was able to install the KB2919355 update (after performing a manual fix of component store corruption) notwithstanding the fact that /RestoreHealth failed after the failed attempt to install the update and still fails with the 0x800f081f error via the command line AFTER the update. A review of the CBS.log indicates NO corruption notwithstanding the report from DISM which indicates there is a problem. This is indicative of the fact the update itself is corrupting the DISM command and perhaps resulting in a false error message. There is a thread about this on the community forums and elsewhere about the issue with no answer.

A system restore to a point BEFORE the failed update results in no problems with /RestoreHealth which has been reported on this forum and others. This update apparently corrupts or at least results in a false error message. This particular issue appears to have been lost in the noise about the failed update itself.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2014-05-19T23:45:43+00:00

DISM.exe /Online /Cleanup-image /Restorehealth

It failed with an error 0x800f081f

I have seen an implication that both it and ScanHealth may do the equivalent of CheckSUR. If that's the case, there may be extra logs in %windir%\Logs\CBS\

Also, I just found out that Powershell seems to have equivalent functionality (probably just a UI wrapper for it) which may be easier to use. At least it seemed easier to use the LogLevel and LogPath operands. <eg>

http://technet.microsoft.com/library/2e9658bf-c013-4fd1-a981-b9242ba61d35(v=wps.630).aspx
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments