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 hope your experience with level 2 is more fruitful than mine was. The only solution they said that it will work was to restore my laptop from the built in partition to the as shipped condition. Apply all the updates and upgrade - hours and multiple reboots which we already have done because of MS pushing a faulty upgrade. And then, reinstalling all the software and the files that I had to copy to an external drive. Please keep us posted if MS second level has a reasonable suggestion.

Some would say that if the update corrupts the system files then your suggestion will not work: http://www.eightforums.com/performance-maintenance/44172-dism-restorehealth-failes-error-0x800f081f.html If the log messages that are shown there were the only significant ones then the "corruption" involved very old modules. (This is something that has perplexed me with IE updates too. Why are they failing try to find such old modules? And I have speculated that perhaps injudicious "cleanup" may be responsible?) In any case, I think they would not be using the source correctly to repair corruption if they were trying to point it to an updated image (especially if they had used /resetbase to get there. <eg>) I think it would make more sense to point to an older image, which some users might have. and also here: http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/error-0x80070005-when-installing-kb-2919355/a7fddff5-4ab9-4077-baf1-3fb030e73877#LastReply There are also a number of posts on this and other forums which indicate that a repair-install is the only solution to the corrupt files issue and simply pointing /restorehealth to a good source whether sxs or a mounted image will not work. Unfortunately most of us do not have media available in order to test this proposition, but those who do indicate it requires a repair-install rather than a known good source. There has not been a peep out of Microsoft about the issue, but what else is new? It does make for interesting discussions and suppositions for those who enjoy such discussions, but until Microsoft deals with the issue it will remain an interesting discussion and supposition for those who are into such things but not a practical resolution for most users. Until I have actually tested my ideas I would of course have to defer to others' experience. I was just pointing out what the DISM documentation seemed to imply. So, if it doesn't work the way it is described, what's wrong: the document? my interpretation of what is written? or the program being documented? <eg>

That your choice but remember no security Updates starting in June. Hope this helps and if you need further assistance post and we will be glad to Help you. The above opinion is mine and mine alone and doesn't necessarily reflect that of Microsoft, it's employees, or any other member of this forum. "When we try to pick out anything by itself, we find it hitched to everything else in the Universe." -John Muir

Some would say that if the update corrupts the system files then your suggestion will not work: http://www.eightforums.com/performance-maintenance/44172-dism-restorehealth-failes-error-0x800f081f.html and also here: http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/error-0x80070005-when-installing-kb-2919355/a7fddff5-4ab9-4077-baf1-3fb030e73877#LastReply There are also a number of posts on this and other forums which indicate that a repair-install is the only solution to the corrupt files issue and simply pointing /restorehealth to a good source whether sxs or a mounted image will not work. Unfortunately most of us do not have media available in order to test this proposition, but those who do indicate it requires a repair-install rather than a known good source. There has not been a peep out of Microsoft about the issue, but what else is new? It does make for interesting discussions and suppositions for those who enjoy such discussions, but until Microsoft deals with the issue it will remain an interesting discussion and supposition for those who are into such things but not a practical resolution for most users.

@AltanYazici, I had my first 3 hour session with Microsoft Level 1 support. Level 2 will take a shot at my system on Friday (I have real work to do tomorrow). The finger was pointed at my Recovery Partition (400MB total, 130MB free) and/or my EFI System Partition (300MB total, 247MB free). Has anyone seen an official statement on how much free space Update 1 needs on these partitions? The free space is the same as a second laptop (same model, roughly same build) where Win 8.1 Update 1 installed fine. Is it possible that Update 1 is failing not because of space but because other fixes/previous installs of KB2919355 corrupted one or the other partition? I backup the EFI System Partition along with the Windows drive so I could roll both back to April 9th. I have a backup of the Recovery Partition from factory Win8 days but am not sure whether Win8.1 may have modified 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-22T08:56:19+00:00

I hope your experience with level 2 is more fruitful than mine was. The only solution they said that it will work was to restore my laptop from the built in partition to the as shipped condition. Apply all the updates and upgrade - hours and multiple reboots which we already have done because of MS pushing a faulty upgrade. And then, reinstalling all the software and the files that I had to copy to an external drive. Please keep us posted if MS second level has a reasonable suggestion.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2014-05-22T05:34:08+00:00

Some would say that if the update corrupts the system files then your suggestion will not work: http://www.eightforums.com/performance-maintenance/44172-dism-restorehealth-failes-error-0x800f081f.html

If the log messages that are shown there were the only significant ones then the "corruption" involved very old modules. (This is something that has perplexed me with IE updates too. Why are they failing try to find such old modules? And I have speculated that perhaps injudicious "cleanup" may be responsible?) In any case, I think they would not be using the source correctly to repair corruption if they were trying to point it to an updated image (especially if they had used /resetbase to get there. <eg>) I think it would make more sense to point to an older image, which some users might have.

and also here: http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/error-0x80070005-when-installing-kb-2919355/a7fddff5-4ab9-4077-baf1-3fb030e73877#LastReply

There are also a number of posts on this and other forums which indicate that a repair-install is the only solution to the corrupt files issue and simply pointing /restorehealth to a good source whether sxs or a mounted image will not work.

Unfortunately most of us do not have media available in order to test this proposition, but those who do indicate it requires a repair-install rather than a known good source. There has not been a peep out of Microsoft about the issue, but what else is new? It does make for interesting discussions and suppositions for those who enjoy such discussions, but until Microsoft deals with the issue it will remain an interesting discussion and supposition for those who are into such things but not a practical resolution for most users.

Until I have actually tested my ideas I would of course have to defer to others' experience. I was just pointing out what the DISM documentation seemed to imply. So, if it doesn't work the way it is described, what's wrong: the document? my interpretation of what is written? or the program being documented? <eg>
Was this answer helpful?

0 comments No comments
Anonymous

2014-05-22T03:01:13+00:00

That your choice but remember no security Updates starting in June.

Hope this helps and if you need further assistance post and we will be glad to Help you.

The above opinion is mine and mine alone and doesn't necessarily reflect that of Microsoft, it's employees, or any other member of this forum.

"When we try to pick out anything by itself, we find it hitched to everything else in the Universe." -John Muir
Was this answer helpful?

0 comments No comments
Anonymous

2014-05-22T02:17:32+00:00

Some would say that if the update corrupts the system files then your suggestion will not work: http://www.eightforums.com/performance-maintenance/44172-dism-restorehealth-failes-error-0x800f081f.html and also here: http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/error-0x80070005-when-installing-kb-2919355/a7fddff5-4ab9-4077-baf1-3fb030e73877#LastReply

There are also a number of posts on this and other forums which indicate that a repair-install is the only solution to the corrupt files issue and simply pointing /restorehealth to a good source whether sxs or a mounted image will not work. Unfortunately most of us do not have media available in order to test this proposition, but those who do indicate it requires a repair-install rather than a known good source. There has not been a peep out of Microsoft about the issue, but what else is new? It does make for interesting discussions and suppositions for those who enjoy such discussions, but until Microsoft deals with the issue it will remain an interesting discussion and supposition for those who are into such things but not a practical resolution for most users.
Was this answer helpful?

0 comments No comments
Anonymous

2014-05-22T02:16:24+00:00

@AltanYazici, I had my first 3 hour session with Microsoft Level 1 support. Level 2 will take a shot at my system on Friday (I have real work to do tomorrow).

The finger was pointed at my Recovery Partition (400MB total, 130MB free) and/or my EFI System Partition (300MB total, 247MB free). Has anyone seen an official statement on how much free space Update 1 needs on these partitions? The free space is the same as a second laptop (same model, roughly same build) where Win 8.1 Update 1 installed fine.

Is it possible that Update 1 is failing not because of space but because other fixes/previous installs of KB2919355 corrupted one or the other partition? I backup the EFI System Partition along with the Windows drive so I could roll both back to April 9th. I have a backup of the Recovery Partition from factory Win8 days but am not sure whether Win8.1 may have modified it.
Was this answer helpful?

0 comments No comments