Error: We couldn’t complete the updates, Undoing changes. Don’t turn off your computer.

Robert, that's an issue in itself too. Windows update is set to automatically downloading and installing KB2919355. I am pretty sure that files were downloaded each time. So actually over this period, the auto-update had tried installing this many times. (Other updates were okay). I asked the same question earlier, and downloaded KB2919355 manually install it too. At the end of the installation (after a good 10+mins), it said failed too..... let me know any options that I should try...

By comparing the Update History and the updates needing to be applied, I've found that they are the same. Update History indicates all were successfully installed.

Therefore repeating the process results in an error.

It appears that the auto updater doesn't get the message that they are installed. Maybe that's the problem and is fixable.

I took a look at my partitions and as my laptop originally had just a 120gig SSD, the system reserved partition was less than 2 gigs.  On the hunch that this might be causing the problem, I used the recommended Minitool partition wizard to extend the system reserved partition to about 25 gigs.   I ran KB2919355 again, but the result was exactly the same.  It seemed to install just fine within Windows and then failed after a series of reboots with the same "We couldn't complete the updates.  Undoing Changes" message.

It does not look like the reserve partition size made any difference, my problem is the same as before and this update will not install.

partition size is 334 GB with 192GB free, so space is definitely NOT the issue.

@ Ron

The problem partition appeared to be the System partition.  Supposedly something gets changed there.  It is usually measured in MB.   Use  diskmgmt.msc  to see them and how much Free Space there is.  Use diskpart  list volume  to see more about it.  However, I only know how to access it during a boot...  OK.  FWIW we can use diskpart to actually get to it, assign a letter to it and then do a dir!  Who knew?  And that shows that the last write was done 2014-03-02.  Now what?  Oh.  I suppose I can use DISM /get-packages and try a find...  Even better I can use  Powershell's  equivalent cmdlet and do the same thing...  No.  That doesn't make any sense.  I only got this machine in April.   ; /

Ah.  For my Surface RT 2 it may be a different story.  With it when I delve into its System drive

B:\EFI\Microsoft\Boot>dir/tw/od

I see two relatively recent writes:

2014-02-22  07:17      760,680 bootmgfw.efi

2014-02-22  07:17      758,120 bootmgr.efi

Then going into Powershell I get this:

PS B:> Get-WindowsPackage -Online  |  ft  InstallTime,PackageName -AutoSize | Out-String -Stream | Select-String -Pattern "2014-02-22"

2014-02-22 01:30:00 Package_for_KB291934~31bf3856ad364e35~arm~6.3.1.3

That was a transcription.  I hope there aren't any typos but at least it will give you the right idea.  There are some other directories that I didn't explore.  Just trying to find something that would possibly match an update.   But then it may only be a coincidence because the timestamps are not consistent with the update I found, so who knows?

FWIW in my case it is a 200 MB partition with (according to dir)  178 free.

But I also speculated to someone else making the same claim about their symptom that perhaps it could be referring to Virtual memory?   Which I then tied to Marek's account about being rather meticulous about removing stuff that might have cost memory, e.g. if the programmer was trying to read everything in and use RAM.  (My interpretation of what was done, not something that I read.)  Or WinPE supposedly creates RAM drives, so maybe that was a "disk" that got too full.  Again, who knows?  For us, I think, only a trace can explain what is really going on.

FYI

Robert

I am stuck with KB2961908 failing consistently with error 800F0922 and KB2919355 claiming it installed successfully but getting rolled back during the reboot.  I downloaded the KB2919355 standalone installer, clearcompressionflag.exe ran without any output, running KB2919355.msu resulted in the same rollback.  I noticed that during the restart the other 5 fixes in the KB2919355 package were installed but they were probably rolled back as well.

sfc /scannow cleaned up a ton of errors relating to update files.  A second sfc identified issues with the hash on CNBJ2530.DPB, a printer driver (could not be repaired).  When I tried to install the standalone KB2919355 again, I received an error 80070003 (path not found).  The WindowsUpdate.log shows "WARNING: Copy update to cache failed with exit code = 0x80070003".

Windows Update Troubleshooter reports a DataStore 0x80070057 error that it could not fix and also "Access to the path 'C:\WINDOWS\softwaredistribution' is denied."  I cannot see anything obviously wrong with this folder - permissions are identical to a similar system that successfully installed KB2919355 on May 4th.  

The WindowsUpdate.log contains numerous fatal errors including 0x800f0922, 0x8007045b, 

0x80070002, 0x80242008, 80080008.

Computer Management shows a 400MB Recovery Partition and a 300MB EFI System Partition.

I pass HTTP traffic through a local squid3 server although this had not caused any issues in the past (most Windows Updates are too big to get cached).

At this point, I am not sure if the next step should be the DISM tool, resetting the Windows Update components or restoring my system partition back to my last image backup on April 11 and hoping the problem goes away (:-).  A step-by-step process for narrowing down the issues and appropriate remedial action would really help at this point.