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

Anonymous
2014-05-14T19:34:39+00:00

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.

  1. 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.
  2. Tap or click Change PC settings, and then Update and recovery.
  3. 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.

0 comments No comments

998 answers

Sort by: Most helpful
  1. Anonymous
    2014-05-19T21:17:49+00:00

    Just for grins, I thought I would try to install 9355 again (just cause I love pain), but it is no longer offered in the update?!?  It's gone.  Is MSFT reworking it, and has pulled it from the store?

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2014-05-19T21:06:45+00:00

    I'm not aware that one can uninstall the 8.1 that came via the store update process.

    <Elephant on the table>

    There is no quick fix here folks.  If you cannot get this update installed as is, you are facing rebuilds or repairs. 

    I need to see if there's a legal way to do an inplace install if you have no 8.1 product key.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2014-05-19T21:00:01+00:00

    If 2919355 is not installed by June, you will receive no future security updates.

    What about backing out of W8.1 to W8.0?

    You're kidding, right?

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2014-05-19T20:55:00+00:00

    If 2919355 is not installed by June, you will receive no future security updates.

    What about backing out of W8.1 to W8.0?

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2014-05-19T20:53:33+00:00

    I have been working with this update since April.  I had numerous chat sessions, and I even was on the phone with level 2 support.  Here is the log of things from lat few days:

    5/18 13:40 – RESTARTING FROM SCRATCH

    At Command Prompt (Admin):

    C:\WINDOWS\system32>dism /online /remove-package /packagename:Package_for_KB2919355~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~amd64~~6.3.1.14

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

    The operation completed successfully.

    C:\WINDOWS\system32>Dism /Online /Cleanup-Image /ScanHealth

    Deployment Image Servicing and Management tool

    Version: 6.3.9600.16384

    Image Version: 6.3.9600.16384

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

    The component store is repairable.

    The operation completed successfully.

    C:\WINDOWS\system32>DISM.exe /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 failed. Either the repair source was not found or the component store cannot be repaired.

    Error: 0x800f081f

    DISM failed. No operation was performed.

    For more information, review the log file.

    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

    A copy of the dism.log file created

    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.

    clearcompressionflag.exe

    OK

    5/19 4:45 AM

    Turning Avast off till reboot

    Ran KB2919355

    Update failed, got the message saying that we could not complete the update, and uninstalling it TWICE.

    This time, the update history was not erased.

    The error is 800F0922.

    I think Mikrosoft owes us all an apology and a quick fix

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments