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.

PS - just to be up to date I tried updating just now and things have moved on!!!!! **New error code =** 800706B5

I don't understand what the problem is?? Windows 8.1 (without mandatory update) is just fine. Just turn your automatic updates off until next year. By then it will be fixed, and you haven't wasted any time, money, or grief. Just keep your Malwarebytes and Spybot up-to-date. You really have no other choice because none of the "solutions" work, and Microsoft isn't aware that they have re-created Vista. So, avoid MS Updates and be happy. This is what I'm doing. As a bog standard user who bothered to find out this forum and look for solutions/help I have tried a few suggestions, I was even on MS online remote support people for near 2hrs before they just disconnected without a word, no notice, nothing depsite starting numerous scans and switching off firewalls, and uninstalling programs. Obviously I gave low feedback and then worked to fix back everything he had halfway done. Anyway, as a bog standard user I don't really know what DSIM, OEM, partition, etc, etc means (I should google the initials at least) but to be honest, knowing what the initials mean would not be a massive help as, I say, I am a bog standard laptop user and wouldn't feel comfortable breaking things down to build them back up. The only problem with wait and see is that my laptop is now working about 40% slower than it used to before all this kerfuffle which can be extremely annoying as I only bought this laptop at the beginning of this year to replace a very old VERY slow one. In following this thread and other suggestions I am just going round and round in ever decreasing circles with things getting ever more technically advanced and so I feel my only option now is to wait and see.

It is great that Microsoft now employs physocoligy(sic) experts to spin things! People who add "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." to their postings are probably employed by Microsoft and I take their postings with a grain of salt. This issue was caused by Microsoft pushing a faulty update. Now they blame everyone but themselves. OEMs were a target, in the postings you will see a surface pro owner having the same issue. We do not want to be WIndows support people. Yet, the suggestions from postings from MS people includes use of tools such as DISM that we do not fully understand, we copy/paste the commands and hope for the best. By the way, I checked Windows update now. It found KB2969339, KB890830, and an Intel video driver. They all installed without a problem. I did not see any IE related updates. I don't care about IE anyway. I don't use it, and probably I will never use it. So, what is my status? Am I out of the abandoned users?

Reinstall, Find repair media from someplace on the web, rebuild The servicing stack is so corrupted nothing is working. I am seeing no other solution, no magic fix. Frankly, the only update I was expecting / hoping for this Update Tuesday was a fresh build of the 2919355 update, whereas my Windows Update list is still showing the duff MkII version from 14 May. However, contrary to other reports about today's updates not being available if 2919355 is not installed, I am still seeing a bunch of fresh updates today . So maybe we are not being sold down the river just yet. With my Surface Pro, Microsoft is my 'OEM' (sic), but they have yet to offer a fix to the problem, only that I could waste two days plus of my time to re-install W8.0 and the subsequent updates and risk getting back to exactly the same mess at the end of the process. Do they really think anyone is going to do that? We reasonably expect a fix to the failed update.

NO ERROR CODE, and my update history is blank. Sounds like an automatic refresh was done? What did it leave you with? To try to find out try this command in an elevated cmd window (AKA Administrator Command Prompt). It's a fake DISM command but it should show you both the version of DISM that you have, which apparently has been a problem for a few people, and the version of the image that you are now using. dism /online /version

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-11T10:48:20+00:00

PS - just to be up to date I tried updating just now and things have moved on!!!!!

**New error code =**800706B5
Was this answer helpful?

0 comments No comments
Anonymous

2014-06-11T10:25:39+00:00

I don't understand what the problem is?? Windows 8.1 (without mandatory update) is just fine. Just turn your automatic updates off until next year. By then it will be fixed, and you haven't wasted any time, money, or grief. Just keep your Malwarebytes and Spybot up-to-date. You really have no other choice because none of the "solutions" work, and Microsoft isn't aware that they have re-created Vista. So, avoid MS Updates and be happy.

This is what I'm doing.

As a bog standard user who bothered to find out this forum and look for solutions/help I have tried a few suggestions, I was even on MS online remote support people for near 2hrs before they just disconnected without a word, no notice, nothing depsite starting numerous scans and switching off firewalls, and uninstalling programs. Obviously I gave low feedback and then worked to fix back everything he had halfway done.

Anyway, as a bog standard user I don't really know what DSIM, OEM, partition, etc, etc means (I should google the initials at least) but to be honest, knowing what the initials mean would not be a massive help as, I say, I am a bog standard laptop user and wouldn't feel comfortable breaking things down to build them back up.

The only problem with wait and see is that my laptop is now working about 40% slower than it used to before all this kerfuffle which can be extremely annoying as I only bought this laptop at the beginning of this year to replace a very old VERY slow one.

In following this thread and other suggestions I am just going round and round in ever decreasing circles with things getting ever more technically advanced and so I feel my only option now is to wait and see.
Was this answer helpful?

0 comments No comments
Anonymous

2014-06-11T08:34:35+00:00

It is great that Microsoft now employs physocoligy(sic) experts to spin things!

People who add "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." to their postings are probably employed by Microsoft and I take their postings with a grain of salt.

This issue was caused by Microsoft pushing a faulty update. Now they blame everyone but themselves. OEMs were a target, in the postings you will see a surface pro owner having the same issue. We do not want to be WIndows support people. Yet, the suggestions from postings from MS people includes use of tools such as DISM that we do not fully understand, we copy/paste the commands and hope for the best.

By the way, I checked Windows update now. It found KB2969339, KB890830, and an Intel video driver. They all installed without a problem. I did not see any IE related updates. I don't care about IE anyway. I don't use it, and probably I will never use it.

So, what is my status? Am I out of the abandoned users?
Was this answer helpful?

0 comments No comments
Anonymous

2014-06-11T05:25:47+00:00

Reinstall, Find repair media from someplace on the web, rebuild

The servicing stack is so corrupted nothing is working.

I am seeing no other solution, no magic fix.

Frankly, the only update I was expecting / hoping for this Update Tuesday was a fresh build of the 2919355 update, whereas my Windows Update list is still showing the duff MkII version from 14 May.

However, contrary to other reports about today's updates not being available if 2919355 is not installed, I am still seeing a bunch of fresh updates today. So maybe we are not being sold down the river just yet.

With my Surface Pro, Microsoft is my 'OEM' (sic), but they have yet to offer a fix to the problem, only that I could waste two days plus of my time to re-install W8.0 and the subsequent updates and risk getting back to exactly the same mess at the end of the process. Do they really think anyone is going to do that?

We reasonably expect a fix to the failed update.
Was this answer helpful?

0 comments No comments
Anonymous

2014-06-11T03:30:24+00:00

NO ERROR CODE, and my update history is blank.

Sounds like an automatic refresh was done? What did it leave you with?

To try to find out try this command in an elevated cmd window (AKA Administrator Command Prompt). It's a fake DISM command but it should show you both the version of DISM that you have, which apparently has been a problem for a few people, and the version of the image that you are now using.

dism /online /version
Was this answer helpful?

0 comments No comments