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 Windows 8.1 updates KB3000850 and KB3013769 keep appearing on my update list but will not download. I have tried going to the site to download them but they still do not download. Other updates have downloaded although I did switch off automatic updates to getsome of them

Did you lose any programs doing this? I'd love to know. My husband's computer has had issues for MANY months. What phone # did you call? Thank you!!!

Done that but with no result... How soon after the event did you try? CBS.log gets wrapped quickly so you may have to look also at the archived versions.

@ Robert Aldwinckle on forums , at the risk of adding even more posts to this thread, is there an opportunity to develop a script that steps through the standard recovery steps for these kinds of Windows Update issues? For those cases where the typical steps do not resolve the issue, would it be possible to write a script that extracts the useful bits of information from the various logs? I do not have the skills to write the scripts themselves but would be willing to help test them- I still have a bunch of the logs from my bout with KB2919355-itis.

still have a bunch of the logs from my bout with KB2919355-itis. One with 0x80246013? All we are trying to do first is get the text for that code as a supplementary clue. MS can't get DISM right (which I think makes sense in many ways as a strategy) so I can't imagine them being able to create a tool to make their unusable diagnostics more usable and it doesn't make any sense economically anyway to spend development resources on such a project. Fix the product and fix the repair tool before spending effort on making diagnostics which were not designed for self-support more useful for self-support. I still say that, if you want to do self-support, using ProcMon to find and supplement whatever diagnostics you are given is the most effective way to puzzle out what you have been given. It would be nice if we had access to at least the support documentation but I can think of several reasons why even that it is not available. BTW in W10 some tools we rely on such as WindowsUpdate.log are going away, so it might even be a waste of effort documenting how to make use of it, let alone try to code something that would try to make use of it. If anything it would be better to make expert systems for it. I wouldn't be surprised if MS Support already have such things but they have access to the source and support documentation which would make development of them feasible and relatively efficient. FYI Robert

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

2015-05-11T14:45:49+00:00

The Windows 8.1 updates KB3000850 and KB3013769 keep appearing on my update list but will not download. I have tried going to the site to download them but they still do not download. Other updates have downloaded although I did switch off automatic updates to getsome of them
Was this answer helpful?

0 comments No comments
Anonymous

2015-05-11T19:36:39+00:00

Did you lose any programs doing this? I'd love to know. My husband's computer has had issues for MANY months. What phone # did you call? Thank you!!!
Was this answer helpful?

0 comments No comments
Anonymous

2015-05-11T20:59:38+00:00

Done that but with no result...

How soon after the event did you try? CBS.log gets wrapped quickly so you may have to look also at the archived versions.
Was this answer helpful?

0 comments No comments
Anonymous

2015-05-11T21:38:37+00:00

@Robert Aldwinckle on forums, at the risk of adding even more posts to this thread, is there an opportunity to develop a script that steps through the standard recovery steps for these kinds of Windows Update issues? For those cases where the typical steps do not resolve the issue, would it be possible to write a script that extracts the useful bits of information from the various logs? I do not have the skills to write the scripts themselves but would be willing to help test them- I still have a bunch of the logs from my bout with KB2919355-itis.
Was this answer helpful?

0 comments No comments
Anonymous

2015-05-12T02:55:41+00:00

still have a bunch of the logs from my bout with KB2919355-itis.

One with 0x80246013? All we are trying to do first is get the text for that code as a supplementary clue.

MS can't get DISM right (which I think makes sense in many ways as a strategy) so I can't imagine them being able to create a tool to make their unusable diagnostics more usable and it doesn't make any sense economically anyway to spend development resources on such a project. Fix the product and fix the repair tool before spending effort on making diagnostics which were not designed for self-support more useful for self-support.

I still say that, if you want to do self-support, using ProcMon to find and supplement whatever diagnostics you are given is the most effective way to puzzle out what you have been given. It would be nice if we had access to at least the support documentation but I can think of several reasons why even that it is not available.

BTW in W10 some tools we rely on such as WindowsUpdate.log are going away, so it might even be a waste of effort documenting how to make use of it, let alone try to code something that would try to make use of it. If anything it would be better to make expert systems for it. I wouldn't be surprised if MS Support already have such things but they have access to the source and support documentation which would make development of them feasible and relatively efficient.

FYI

Robert
Was this answer helpful?

0 comments No comments