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.

@ Susan See this ? Someone figured out how to use DISM's /source: switch! Now if we could just get a way of knowing what to download and unpack for which module version we would really be getting some place! Note that it really doesn't help that now all .manifest files are compressed and hence unsearchable! But why doesn't WU fill in the holes if something is missing and /LimitAccess is not specified? Isn't that how it is implied that it works? FYI Robert

I strongly recommend that you start a new thread. No one will find you on the 49th page of a forum post. Generally speaking when this issue occurs there is system corruption and you need to do a sfc /scannow or DISM http://www.eightforums.com/tutorials/26512-dism-fixing-component-store-corruption-windows-8-a.html

The "latest" failed update error code is KB2975719 after the "Can't Complete Updates: Undoing Changes" screen. Please help. I am tired of having to deal with this every time I turn on my computer. This is an embarrasment.

Various attempts at updates (e.g., KB 2975719 / KB 2919355 / KB 2989647) since 9/13/14 [some were auto-updates / some manual] failed with no ERROR number /code. 2 messages appeared, in each case. Initially, 'Working on updates ##% complete. Don't turn off your computer.' Followed by 'We couldn't complete the updates. Undoing changes. Don't turn off your computer.' On some instances, 2 cycles of these messages appeared, with a RE-START in the middle, before the CPU rebooted.

Please see my earlier comment about that code . I will even do the suggested translation for you: <translation> 0x800f0922-activation error Possible causes of-activation keys do not correspond to the distribution; update to Windows 8 made on unactivated platform (Windows 7, Vista, XP); license validity period has expired with a limited lifetime; it exceeded the number of activations for multiple keys; system updates were installed on the non-activated Windows, there are third-party software, distorting or destroying files activation. In most cases, reinstalling the system and correct activation eliminates the error. </translation> Unfortunately the KB article which documents these codes has still not been updated to reflect this information. OTOH this looks to me like a "grasping at straws" grab bag reason code (better than "something's wrong" but not much), so as always I would be using ProcMon to try to find out what is really going on. FYI Robert Aldwinckle

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-10-13T05:13:54+00:00

@ Susan

See this? Someone figured out how to use DISM's /source: switch! Now if we could just get a way of knowing what to download and unpack for which module version we would really be getting some place! Note that it really doesn't help that now all .manifest files are compressed and hence unsearchable! But why doesn't WU fill in the holes if something is missing and /LimitAccess is not specified? Isn't that how it is implied that it works?

FYI

Robert
Was this answer helpful?

0 comments No comments
Anonymous

2014-10-13T04:43:19+00:00

I strongly recommend that you start a new thread. No one will find you on the 49th page of a forum post.

Generally speaking when this issue occurs there is system corruption and you need to do a sfc /scannow or DISM

http://www.eightforums.com/tutorials/26512-dism-fixing-component-store-corruption-windows-8-a.html
Was this answer helpful?

0 comments No comments
Anonymous

2014-10-12T20:05:50+00:00

The "latest" failed update error code is KB2975719 after the "Can't Complete Updates: Undoing Changes" screen.

Please help. I am tired of having to deal with this every time I turn on my computer. This is an embarrasment.
Was this answer helpful?

0 comments No comments
Anonymous

2014-10-09T18:11:22+00:00

Various attempts at updates (e.g., KB 2975719 / KB 2919355 / KB 2989647) since 9/13/14 [some were

auto-updates / some manual] failed with no ERROR number /code. 2 messages appeared, in each

case. Initially, 'Working on updates ##% complete. Don't turn off your computer.' Followed by

'We couldn't complete the updates. Undoing changes. Don't turn off your computer.'

On some instances, 2 cycles of these messages appeared, with a RE-START in the middle, before

the CPU rebooted.
Was this answer helpful?

0 comments No comments
Anonymous

2014-10-08T17:56:20+00:00

Please see my earlier comment about that code. I will even do the suggested translation for you:

<translation>

0x800f0922-activation error

Possible causes of-activation keys do not correspond to the distribution; update to Windows 8 made on unactivated platform (Windows 7, Vista, XP); license validity period has expired with a limited lifetime; it exceeded the number of activations for multiple keys; system updates were installed on the non-activated Windows, there are third-party software, distorting or destroying files activation.

In most cases, reinstalling the system and correct activation eliminates the error.

</translation>

Unfortunately the KB article which documents these codes has still not been updated to reflect this information. OTOH this looks to me like a "grasping at straws" grab bag reason code (better than "something's wrong" but not much), so as always I would be using ProcMon to try to find out what is really going on.

FYI

Robert Aldwinckle
Was this answer helpful?

0 comments No comments