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

Please post here with your error code, so that the Community can try to help guide you appropriately.

Two related KB articles fails to install:

Security Update for Windows 8.1 for x64-based Systems (KB2961908) without KB2919355

Installation date: ‎21.‎05.‎2014 13:19

Installation status: Failed

Error details: Code 800F0922

after reaching 99%

and KB2919355 itself with Code 800F0922 after reaching 99%.

I have tried to follow steps by Vivian Samartha but next command failed with error code0x800f081f.:

DISM.exe /Online /Cleanup-image /Restorehealth

 Could I create a system image on this laptop and then use it to recover the one that is being stubborn?

Are they networked?  Looking at that  /source:  parameter  it implies that you just need to point it at something usable.   So, if it was pointing at the other's WinSxS, and it was the same version that you were trying to get wouldn't that be "usable"?   <eg>   Then in that case you probably could even use the /LimitAccess option and save yourself having to connect to WU.   ; )

Ref:

http://technet.microsoft.com/en-us/library/hh825265.aspx

<quotes>

Use the /Source argument to specify the location of the files that are required to restore the feature. The source of the files can by the Windows folder in a mounted image, for example c:\test\mount\Windows. You can also use a Windows side-by-side folder as the source of the files, for example z:\sources\SxS.

If you specify multiple /Source arguments, the files are gathered from the first location where they are found and the rest of the locations are ignored. If you do not specify a /Source for a feature that has been removed, the default location in the registry is used or, for online images, Windows Update (WU) is used.

Use /Source with /RestoreHealth to specify the location of known good versions of files that can be used for the repair, such as a path to the Windows directory of a mounted image.

If you specify multiple /Source arguments, the files are gathered from the first location where they are found and the rest of the locations are ignored. If you do not specify a /Source for a feature that has been removed, the default location in the registry is used or Windows Update (WU) is used for online images.

</quotes>

The first quote was about the /Enable-Feature command's use of that operand but I would suspect that rather than having significantly different functionality the documentation is different to avoid being redundant.

Good luck

Robert

I'm giving up on updating with KB2919355 and getting functioning results.

I will run win8.1 without kb2919355 installed...

@AltanYazici, I had my first 3 hour session with Microsoft Level 1 support.  Level 2 will take a shot at my system on Friday (I have real work to do tomorrow).

The finger was pointed at my Recovery Partition (400MB total, 130MB free) and/or my EFI System Partition (300MB total, 247MB free).  Has anyone seen an official statement on how much free space Update 1 needs on these partitions?  The free space is the same as a second laptop (same model, roughly same build) where Win 8.1 Update 1 installed fine.

Is it possible that Update 1 is failing not because of space but because other fixes/previous installs of KB2919355 corrupted one or the other partition?  I backup the EFI System Partition along with the Windows drive so I could roll both back to April 9th.  I have a backup of the Recovery Partition from factory Win8 days but am not sure whether Win8.1 may have modified it.

Some would say that if the update corrupts the system files then your suggestion will not work: http://www.eightforums.com/performance-maintenance/44172-dism-restorehealth-failes-error-0x800f081f.html and also here: http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/error-0x80070005-when-installing-kb-2919355/a7fddff5-4ab9-4077-baf1-3fb030e73877#LastReply

There are also  a number of posts on this and other forums which indicate that a repair-install is the only solution to the corrupt files issue and simply pointing /restorehealth to a good source whether sxs or a mounted image will not work. Unfortunately most of us do not have media available in order to test this proposition, but those who do indicate it requires a repair-install rather than a known good source. There has not been a peep out of Microsoft about the issue, but what else is new? It does make for interesting discussions and suppositions for those who enjoy such discussions, but until Microsoft deals with the issue it will remain an interesting discussion and supposition for those who are into such things but not a practical resolution for most users.