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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2016-02-04T18:49:21+00:00

    80070490

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-02-01T02:06:55+00:00

    Your cmd search located a number of files, each in a folder relating to individual diagnostics. I'm not sure how to interpret anything in the files in these folders though, and can't seem to be able to add files to this board..?

    I ran a Windows Update troubleshooting tool, which returned the error 0x80070490.

    Then followedthese instructions and got these results:

    ![](http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=280fdb61-d0ce-4563-88c1-7b4d673fec64)

    Regarding the BITS troubleshooter, I'm not sure what BITS stands for but I can't find anything that relates to it in the list (running a search in that window returns no results).

    ![](http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=4ed9c0f4-76d9-4998-a748-2a59f0ebe5f6)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-01-29T17:34:47+00:00

    Clicking on it does nothing, searching for that file name returns no results...

    When are you trying?  It may be that your only opportunity to do this will be when you are looking at that dialog.  E.g. closing that dialog may just delete the files it refers to (or perhaps move them to somewhere even more obscure). 

    Otherwise try doing a search for just  CheckSUR*  (e.g. that prefix).   To bypass File Explorer's quirks you could try checking using a cmd window, with current directory set to your SystemDrive root.   E.g. enter:

    cd \

    dir/a/b/s  checksur*

    As for your BITS problem the message sounds bogus.  The dependency for it is a really fundamental service RPCSS.  You would be having more problems than just BITS troubleshooter if there really was a problem with it.  This is an example of why I would want to see more details from the troubleshooter.  However, if you wanted something to try for it, apparently there is a separate troubleshooter for BITS, e.g. as seen in the All Troubleshooters list:

    Control Panel\All Control Panel Items\Troubleshooting\All Categories

    Good luck

    Robert

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-01-29T10:38:51+00:00

    Clicking on it does nothing, searching for that file name returns no results...

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-01-29T04:40:58+00:00

    [Troubleshooting report refers to  CheckSURlog.cab]

    Try opening that .cab file and see if there are any clues in the log files.  Maybe it will have something about the BITS problem too.

    Good luck

    Robert

    Was this answer helpful?

    0 comments