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.

The 8.1 update KB2919355 failed without an error code. Just the statement "We couldn't complete the updates, Undoing changes. Don't turn off your computer." I went through all of the admin Command line commands before I tried to install the update, but it didn't help. I am experiencing the same error. i am stuck please help. Thanks in advance.

I can not find "update and recovery". My error came when the update was allmost done insalling and the code were: OxC1900101-0x40017. Anybody knows what that means?

My error code is 0x800F0806. We have two identical computers bought recently (still under warranty). Came loaded with 8.0, I updated both to 8.1. Both are 64-bit. I set both of them up identically. Partitions on both are the same; I left them as they came. One has installed KB2919355 with no issues, the other continues to fail. Loads everything, installs to 100%, then gives error... we couldn't complete the updates..." rolls back. View update history reveals error code 0x800F0806. I have tried all fixes presented, including DISM. Indicated that the corrupt file was fixed, so I was encouraged to try updating after a reboot, only to have the same 40 minutes wait while the file is being installed and then rolled back. Someone mentioned I should find a moderator that could give me a MS case number, but I don't see how to do this. Please help!

Also, this was in the DISM log: Did you restart your DISM.log before trying that command? Otherwise, my guess would be that you are just showing us old corruption. In particular, notice that there is no timestamp to help judge when those records were written. An alternative to renaming or restarting your DISM.log would be redirecting the output of a specific DISM command to a specific file using its /LogPath: operand. Alternatively, I would be interested in seeing if my Powershell count idea works on that log and if there is anything actually readable after the initial corruption. See... a thread that I can't find ATM ... It was a really simple idea. Just use Powershell to find out how many records it saw and then go down into cmd for more (because I don't know an elegant Powershell method of doing the next step) E.g. in Adminstrator Powershell navigate to the DISM log directory and do those things: cd $env:windir\Logs\DISM (get-content dism.log).count cmd more <dism.log +nnn00 (E.g. where the first step returned +nnnxx and you just want to see the last xx) HTH Robert Aldwinckle

joseph, While I don't necessarily disagree with your point of view, this forum exists because ordinary users like myself are prepared to volunteer their services to try and help others. There are alternatives such as direct support from Microsoft, but it's not free: Microsoft Answer Desk Support Services Where it concerns an OEM machine, that it to say, a computer supplied with the operating system preinstalled, the manufacturer is responsible for providing support. Some are better than others and it's pot luck as to whether you get a good deal or not. Microsoft does come under pressure through posts on this forum because many media sites like the following one which doesn't pull any punches often refers to it in their reports: http://www.infoworld.com/t/microsoft-windows/microsoft-tends-enterprise-windows-users-kicks-consumers-the-curb-240801?page=0,1 This kind of pressure forced Microsoft to backtrack on it's orginal threat to cutoff users by April 8 if they hadn't installed KB2919355 by then and the deadline was subsequently extended to May 13. Where we go from here though is anybody's guess.

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-06-17T19:39:20+00:00

The 8.1 update KB2919355 failed without an error code. Just the statement "We couldn't complete the updates, Undoing changes. Don't turn off your computer." I went through all of the admin Command line commands before I tried to install the update, but it didn't help.

I am experiencing the same error. i am stuck please help. Thanks in advance.
Was this answer helpful?

0 comments No comments
Anonymous

2014-06-17T18:06:28+00:00

I can not find "update and recovery". My error came when the update was allmost done insalling and the code were: OxC1900101-0x40017. Anybody knows what that means?
Was this answer helpful?

0 comments No comments
Anonymous

2014-06-16T20:49:49+00:00

My error code is 0x800F0806. We have two identical computers bought recently (still under warranty). Came loaded with 8.0, I updated both to 8.1. Both are 64-bit. I set both of them up identically. Partitions on both are the same; I left them as they came. One has installed KB2919355 with no issues, the other continues to fail. Loads everything, installs to 100%, then gives error... we couldn't complete the updates..." rolls back. View update history reveals error code 0x800F0806.

I have tried all fixes presented, including DISM. Indicated that the corrupt file was fixed, so I was encouraged to try updating after a reboot, only to have the same 40 minutes wait while the file is being installed and then rolled back.

Someone mentioned I should find a moderator that could give me a MS case number, but I don't see how to do this.

Please help!
Was this answer helpful?

0 comments No comments
Anonymous

2014-06-15T20:54:50+00:00

Also, this was in the DISM log:

Did you restart your DISM.log before trying that command?   Otherwise, my guess would be that you are just showing us old corruption. In particular, notice that there is no timestamp to help judge when those records were written.

An alternative to renaming or restarting your DISM.log would be redirecting the output of a specific DISM command to a specific file using its /LogPath: operand.

Alternatively, I would be interested in seeing if my Powershell count idea works on that log and if there is anything actually readable after the initial corruption.   See... a thread that I can't find ATM... It was a really simple idea.   Just use Powershell to find out how many records it saw and then go down into cmd for more (because I don't know an elegant Powershell method of doing the next step)

E.g. in Adminstrator Powershell navigate to the DISM log directory and do those things:

cd $env:windir\Logs\DISM

(get-content dism.log).count

cmd

more <dism.log +nnn00

(E.g. where the first step returned +nnnxx and you just want to see the last xx)

HTH

Robert Aldwinckle
Was this answer helpful?

0 comments No comments
Anonymous

2014-06-15T18:25:43+00:00

joseph,

While I don't necessarily disagree with your point of view, this forum exists because ordinary users like myself are prepared to volunteer their services to try and help others.

There are alternatives such as direct support from Microsoft, but it's not free: Microsoft Answer Desk Support Services

Where it concerns an OEM machine, that it to say, a computer supplied with the operating system preinstalled, the manufacturer is responsible for providing support. Some are better than others and it's pot luck as to whether you get a good deal or not.

Microsoft does come under pressure through posts on this forum because many media sites like the following one which doesn't pull any punches often refers to it in their reports: http://www.infoworld.com/t/microsoft-windows/microsoft-tends-enterprise-windows-users-kicks-consumers-the-curb-240801?page=0,1

This kind of pressure forced Microsoft to backtrack on it's orginal threat to cutoff users by April 8 if they hadn't installed KB2919355 by then and the deadline was subsequently extended to May 13.

Where we go from here though is anybody's guess.
Was this answer helpful?

0 comments No comments