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

998 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2015-03-03T22:57:30+00:00

    I read through that thread but do not know how to "go into the CBS.log and find the repair attempt and summary." What steps do I follow?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-03-03T22:49:36+00:00

    The ...RestoreHealth command gets this result:

    Error: 0x800f081f

    That's looking much better than I thought.   So now you should go into the CBS.log and find the repair attempt and summary

    Here's an example

    http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/windows-81-store-error-0x80070002-comprehensive/2b0ed3e1-1835-4517-97dd-0a7abb6ef74c?page=3

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-03-03T22:39:30+00:00

    and the Scannow results:

    C:\WINDOWS\system32>sfc /scannow

    Beginning system scan.  This process will take some time.

    Beginning verification phase of system scan.

    Verification 77% complete.

    Windows Resource Protection found corrupt files but was unable to fix some

    of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For

    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not

    supported in offline servicing scenarios.

    C:\WINDOWS\system32>

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-03-03T22:09:49+00:00

    The ...RestoreHealth command gets this result:

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

    Deployment Image Servicing and Management tool

    Version: 6.3.9600.17031

    Image Version: 6.3.9600.17031

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

    Error: 0x800f081f

    The source files could not be found.

    Use the "Source" option to specify the location of the files that are required t

    o restore the feature. For more information on specifying a source location, see

     http://go.microsoft.com/fwlink/?LinkId=243077.

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

    C:\WINDOWS\system32>

    Was this answer helpful?

    0 comments
  5. Anonymous
    2015-03-03T21:55:12+00:00

    Here are the results of running those two commands:

    Microsoft Windows [Version 6.3.9600]

    (c) 2013 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>

    C:\WINDOWS\system32>fsutil  hardlink  list  "C:\Windows\System32\dism.exe"

    \Windows\WinSxS\amd64_microsoft-windows-d..ervicing-management_31bf3856ad364e35_

    6.3.9600.17031_none_4f9af566e17dbc2c\Dism.exe

    \Windows\System32\Dism.exe

    C:\WINDOWS\system32>fsutil  hardlink  list  "C:\Windows\SysWOW64\dism.exe"

    \Windows\WinSxS\x86_microsoft-windows-d..ervicing-management_31bf3856ad364e35_6.

    3.9600.17031_none_f37c59e329204af6\Dism.exe

    \Windows\SysWOW64\Dism.exe

    C:\WINDOWS\system32>

    Was this answer helpful?

    0 comments