My computer has been going through the "We couldn't complete the updates. Undoing changes. Don't turn off your computer" since last night. Tried restarting in SafeMode, but I'm assuming this is no longer an option with 8.1? Please advise how to get past this.
Error: We couldn’t complete the updates, Undoing changes. Don’t turn off your computer.
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.
Windows for home | Previous Windows versions | Windows update
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.
998 answers
Sort by: Most helpful
-
Anonymous
2014-06-29T00:45:05+00:00 -
Anonymous
2014-06-26T16:20:32+00:00 The problem is Asus and all the computer Manufacturers who do not test their computers, software or access. Microsoft maybe aware of weather a manufacturer includes a recovery partitions is mute, it is not their business. These computer companies are responsible to see that their computer runs correctly with Microsoft's Operating system. In my opinion most if not all do a lousy job of this and try and blame anyone but themselves. And by the way, Even though most if not all look for the cheapest way out and let the customer worry about it they do include a recovery Partition or some other recovery option. You might be waiting a long time. this is not microsoft. This forum is made up of individuals like you and me who volunteer their time and effort to help solve users issues or get one of their's solved. As for the change in password policy, this is nothing new to Windows 8.0/8.1.1, it has been the policy for Microsoft Accounts as far back as can remember, and should be as a security issue. Hope this helps and if you need any 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
If this answered your post Please mark it as answered.
-
Anonymous
2014-06-26T15:35:28+00:00 The problem has NOTHING to do with ASUS. I had the exact same issue with a high end ALIENWARE PC. Some manufactures don't even set up their systems with a recovery. I'm sure Microsoft is aware of that.
-
Anonymous
2014-06-26T13:41:16+00:00 I gave up. I formatted C:\ on my brand new ASUS M31AD (with Aus bloatware) took the Windows 8.1 Pro installation (as a MAPS-member I have this available) and started the virgin installation of W8.1 which (suprisingly) took me less than 10 minutes. After installation I first executed all updates (done within 15mins incl. the downloading), installed StarDock Start8 (to get rid of Metro as much as possible), installed Office 2013 and now after roughly 1 hour I am completely back to live with an UP-TO-DATE PC including this tedious update.
Who's to blame? I think partially Microsoft but also Asus who delivers a PC which apparently is not 100% conform MS-specs. The main problem in my case was a too small System Reserved partition which I could not increase with the recommended tools (like EASEUS partition magic).
Anyway: my advise when buying a new laptop/pc: delete the OEM-Windows installation and do a fresh complete Windows installation!
-
Anonymous
2014-06-25T21:43:18+00:00 @NOT_MSFT_LEECHIPTURNER, I made a nuisance of myself at Microsoft Corporate. The challenge is finding a group at Microsoft who has a stake in getting this issue resolved and getting contact details for someone with the clout to get Microsoft Support to pay attention. Fortunately I had a chronology of dates, names, outcomes and enough examples of 'bad information'.
Good luck.