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 have been working with this update since April. I had numerous chat sessions, and I even was on the phone with level 2 support. Here is the log of things from lat few days: @ Altan Did they ask for any diagnostics? AnalyzeComponentStore perhaps? Something with more detail? C.f. http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/error-code-80073712-windows-update-win-81-x64/5cd2b12d-e118-4f82-bf71-bc8e22b85021?page=9&msgId=756d4c1d-c5d9-4fae-a733-c9ffa40dec4e

I spent hours on the phone with MS help and they accomplished nothing. The only thing of interest is when they did the following: DISM.exe /Online /Cleanup-image /Restorehealth It failed with an error 0x800f081f however, after that the tech never pursued this error.

I spent hours on the phone with MS help and they accomplished nothing. The only thing of interest is when they did the following: DISM.exe /Online /Cleanup-image /Restorehealth It failed with an error 0x800f081f however, after that the tech never pursued this error. This seems to be a side effect of the failed update. There are some threads on the community forums and elsewhere about this issue. The error message may or may not signify a problem and may be a false error message but in any event there has been nothing from Microsoft about the issue. Obviously Microsoft still hasn't figured out what the problem is for many users. The company undoubtedly views post on the forums but still allows the volunteers to post the same solutions which have appeared here since April 8th but which do not work. Since the posters are volunteers who may or may not have a clue as to whether the "solutions" will work at least it allows Microsoft to distance itself from those "solutions" because they are proposed by volunteers and not "solutions" officially proposed by the company. Can you say plausible deniability ?

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

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.

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-19T22:06:49+00:00

I have been working with this update since April. I had numerous chat sessions, and I even was on the phone with level 2 support. Here is the log of things from lat few days:

@ Altan

Did they ask for any diagnostics? AnalyzeComponentStore perhaps? Something with more detail?

C.f.

http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/error-code-80073712-windows-update-win-81-x64/5cd2b12d-e118-4f82-bf71-bc8e22b85021?page=9&msgId=756d4c1d-c5d9-4fae-a733-c9ffa40dec4e
Was this answer helpful?

0 comments No comments
Anonymous

2014-05-19T22:15:21+00:00

I spent hours on the phone with MS help and they accomplished nothing. The only thing of interest is when they did the following:

DISM.exe /Online /Cleanup-image /Restorehealth

It failed with an error 0x800f081f

however, after that the tech never pursued this error.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2014-05-19T23:03:53+00:00

I spent hours on the phone with MS help and they accomplished nothing. The only thing of interest is when they did the following:

DISM.exe /Online /Cleanup-image /Restorehealth

It failed with an error 0x800f081f

however, after that the tech never pursued this error.

This seems to be a side effect of the failed update. There are some threads on the community forums and elsewhere about this issue. The error message may or may not signify a problem and may be a false error message but in any event there has been nothing from Microsoft about the issue.

Obviously Microsoft still hasn't figured out what the problem is for many users. The company undoubtedly views post on the forums but still allows the volunteers to post the same solutions which have appeared here since April 8th but which do not work. Since the posters are volunteers who may or may not have a clue as to whether the "solutions" will work at least it allows Microsoft to distance itself from those "solutions" because they are proposed by volunteers and not "solutions" officially proposed by the company. Can you say plausible deniability?
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
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