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.

... according the Surface site, there weren't any updates released in June ... Well, there was definitely a fresh build of KB2919355 available to my Surface Pro as of 17 June 2014, and I have now made two separate attempts at installing it. (You can guess where this is headed.) Before I started, I removed all USB devices, and also the SD card which I use to store photos and MP3s (as the C: drive on my Surface Pro (1) is only 128GB) after first removing it from the relevant libraries and also as the usual source for my desktop images. The first attempt had downloaded up to about 6%, and next moment I looked it was installing. It then went all the way through; two restarts later it failed configuring Windows Updates at 100% and then painstakingly rolled the whole thing back for the umpteenth time. At this stage, I decided I had to give the DISM commands another try, having read some posts suggesting that people have had more luck with them recently. These commands seemed to take longer than on previous occasions and, as per the trace below, you will see that the last command completed with the encouraging message, 'The component store corruption was repaired.'. So I then made my second attempt, and this time it downloaded to at least 92% before saying it was installing. (I have no idea if this difference is significant, or if I should even have expected it to reach 100% first.) It then went all the way through, I even had an idea that the progres bar made it further across this time; but, two restarts later, it again failed configuring Windows Updates at 100% and then painstakingly rolled the whole thing back for the umpteen+1th time. My next step is to re-open my support case with MS which was suspended while I was travelling and to push for access to an 8.1 Pro ISO from which I can attempt the in-place repair. I have seen nothing yet which explains why I should have to pay to access to this (when I already have this system legally installed on my system) and I am ready to make more of a fuss this time after wasting another half day on this debacle. --------------- DISM trace follows ------------------- C:\WINDOWS\system32>DISM /online /remove-package /packagename:Package_for_KB2919 355~31bf3856ad364e35~amd64~~6.3.1.14 Deployment Image Servicing and Management tool Version: 6.3.9600.16384 Image Version: 6.3.9600.16384 Processing 1 of 1 - Removing package Package_for_KB2919355~31bf3856ad364e35~amd6 4~~6.3.1.14 [==========================100.0%==========================] The operation completed successfully. C:\WINDOWS\system32>DISM /online /cleanup-image /startcomponentcleanup Deployment Image Servicing and Management tool Version: 6.3.9600.16384 Image Version: 6.3.9600.16384 [==========================100.0%==========================] The operation completed successfully. C:\WINDOWS\system32>DISM /online /cleanup-Image /restorehealth Deployment Image Servicing and Management tool Version: 6.3.9600.16384 Image Version: 6.3.9600.16384 [==========================100.0%==========================] The restore operation completed successfully. The component store corruption was repaired. The operation completed successfully.

Harry, With regard to your last point regarding CCleaner, please see this article: http://chris.pirillo.com/are-registry-cleaners-safe-to-use/

mr. stem, See this site on how to contact Microsoft: http://www.microsoft.com/surface/en-us/support/contact-us/ I just tried it myself using these options after selecting Surface Pro and the waiting time was only 7 mins.

Thanks Xircal. In fact I just emailed the original engineer to re-open my support case and he replied to me in just 11 minutes to say that a colleague in the right time-zone would be in touch (most likely tomorrow). (I was on the other side of the planet when this all started up and initially worked with someone based in APAC.)

One more update to the group: KB2919355 is finally installed, though not because the patch was ever fixed, nor because the June 17th build was any better than the May 14th. An MS Level 2 Engineer called me back yesterday after I told him that there was no way I was going to start over with a full wipe from my original media. After going through yet another round of DISM attempts prior to another manual update with KB2919355 (which ended with the familiar rollback and undoing of changes) he finally suggested an "in-place repair" of Windows 8.1. I was assured that the in-place repair would not wipe out my user settings nor installed software, the catch is that it requires a Win 8.1 media disc (or .iso). I happened to have one of these from a different install, which sped up the process quite a bit. I'm happy to report that after everything, the "in-place repair," which is basically a non-destructive reinstall, finally did the trick. I have KB2919355 installed and everything is now up-to-date. I wish the patch could have been fixed so that a proper update could have been done on my existing installation, but as we have all found out, that is not currently the case. The in-place repair turned out to be the next best solution for me, although this is not possible if you do not have a Windows 8.1 media disc or access to the .iso.

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-19T15:51:58+00:00

... according the Surface site, there weren't any updates released in June ...

Well, there was definitely a fresh build of KB2919355 available to my Surface Pro as of 17 June 2014, and I have now made two separate attempts at installing it. (You can guess where this is headed.)

Before I started, I removed all USB devices, and also the SD card which I use to store photos and MP3s (as the C: drive on my Surface Pro (1) is only 128GB) after first removing it from the relevant libraries and also as the usual source for my desktop images.

The first attempt had downloaded up to about 6%, and next moment I looked it was installing. It then went all the way through; two restarts later it failed configuring Windows Updates at 100% and then painstakingly rolled the whole thing back for the umpteenth time.

At this stage, I decided I had to give the DISM commands another try, having read some posts suggesting that people have had more luck with them recently. These commands seemed to take longer than on previous occasions and, as per the trace below, you will see that the last command completed with the encouraging message, 'The component store corruption was repaired.'.

So I then made my second attempt, and this time it downloaded to at least 92% before saying it was installing. (I have no idea if this difference is significant, or if I should even have expected it to reach 100% first.) It then went all the way through, I even had an idea that the progres bar made it further across this time; but, two restarts later, it again failed configuring Windows Updates at 100% and then painstakingly rolled the whole thing back for the umpteen+1th time.

My next step is to re-open my support case with MS which was suspended while I was travelling and to push for access to an 8.1 Pro ISO from which I can attempt the in-place repair. I have seen nothing yet which explains why I should have to pay to access to this (when I already have this system legally installed on my system) and I am ready to make more of a fuss this time after wasting another half day on this debacle.

--------------- DISM trace follows -------------------

C:\WINDOWS\system32>DISM /online /remove-package /packagename:Package_for_KB2919

355~31bf3856ad364e35~amd64~~6.3.1.14

Deployment Image Servicing and Management tool

Version: 6.3.9600.16384

Image Version: 6.3.9600.16384

Processing 1 of 1 - Removing package Package_for_KB2919355~31bf3856ad364e35~amd6

4~~6.3.1.14

[==========================100.0%==========================]

The operation completed successfully.

C:\WINDOWS\system32>DISM /online /cleanup-image /startcomponentcleanup

Deployment Image Servicing and Management tool

Version: 6.3.9600.16384

Image Version: 6.3.9600.16384

[==========================100.0%==========================]

The operation completed successfully.

C:\WINDOWS\system32>DISM /online /cleanup-Image /restorehealth

Deployment Image Servicing and Management tool

Version: 6.3.9600.16384

Image Version: 6.3.9600.16384

[==========================100.0%==========================]

The restore operation completed successfully. The component store corruption was

repaired.

The operation completed successfully.
Was this answer helpful?

0 comments No comments
Anonymous

2014-06-19T16:12:46+00:00

Harry,

With regard to your last point regarding CCleaner, please see this article: http://chris.pirillo.com/are-registry-cleaners-safe-to-use/
Was this answer helpful?

0 comments No comments
Anonymous

2014-06-19T16:26:09+00:00

mr. stem,

See this site on how to contact Microsoft: http://www.microsoft.com/surface/en-us/support/contact-us/

I just tried it myself using these options after selecting Surface Pro and the waiting time was only 7 mins.
Was this answer helpful?

0 comments No comments
Anonymous

2014-06-19T17:32:27+00:00

Thanks Xircal. In fact I just emailed the original engineer to re-open my support case and he replied to me in just 11 minutes to say that a colleague in the right time-zone would be in touch (most likely tomorrow). (I was on the other side of the planet when this all started up and initially worked with someone based in APAC.)
Was this answer helpful?

0 comments No comments
Anonymous

2014-06-19T18:04:40+00:00

One more update to the group: KB2919355 is finally installed, though not because the patch was ever fixed, nor because the June 17th build was any better than the May 14th.

An MS Level 2 Engineer called me back yesterday after I told him that there was no way I was going to start over with a full wipe from my original media. After going through yet another round of DISM attempts prior to another manual update with KB2919355 (which ended with the familiar rollback and undoing of changes) he finally suggested an "in-place repair" of Windows 8.1. I was assured that the in-place repair would not wipe out my user settings nor installed software, the catch is that it requires a Win 8.1 media disc (or .iso). I happened to have one of these from a different install, which sped up the process quite a bit.

I'm happy to report that after everything, the "in-place repair," which is basically a non-destructive reinstall, finally did the trick. I have KB2919355 installed and everything is now up-to-date. I wish the patch could have been fixed so that a proper update could have been done on my existing installation, but as we have all found out, that is not currently the case. The in-place repair turned out to be the next best solution for me, although this is not possible if you do not have a Windows 8.1 media disc or access to the .iso.
Was this answer helpful?

0 comments No comments