Results 1 to 9 of 9

Thread: "WindowsUpdate_80070490" "WindowsUpdate_dt000"

  1. #1
    Dragnet Guest

    "WindowsUpdate_80070490" "WindowsUpdate_dt000"

    This an error that is telling me that an update failed to install,
    Specifically (KB967723).

    Upon further investigation; it seems the update is listed as successfully
    installing on Sept 11th but for some reason is now trying to re-install or
    some such.

    System is Windows Server 2008 x64. (Dual Quad core Xeon Dell R610, 48GB RAM)
    I have an identical system where the update is fine.

    Any insights?

  2. #2
    PA Bear [MS MVP] Guest

    Re: "WindowsUpdate_80070490" "WindowsUpdate_dt000"

    0x80070490 - ERROR_NOT_FOUND
    Corrupted System File; Need to perform an in-place upgrade or reinstall of
    the OS.

    The error you are receiving occurs if there is corruption in the Component
    Based Servicing manifest.

    You receive a "0x80070490" error code when you use Windows Update or
    Microsoft Update Web sites to install updates:
    http://support.microsoft.com/kb/958044

    You could peruse this article to see if there's anything you haven't tried -

    How to overcome error 0x80070490 when installing updates in Windows
    Vista/Server 2008
    http://blogs.msdn.com/andrekl/archiv...rver-2008.aspx

    Or see the "How to obtain help" section of
    http://support.microsoft.com/kb/967723

  3. #3
    MowGreen Guest

    Re: "WindowsUpdate_80070490" "WindowsUpdate_dt000"

    Before doing an 'in-place upgrade', described as a 'repair installation'
    in the KB article, suggest that you download, *save*, and then run the
    System Update Readiness Tool [CheckSUR]:
    http://support.microsoft.com/kb/947821

    "What is the System Update Readiness Tool?
    System resources, such as file data, registry data, and even in-memory
    data, can develop inconsistencies during the lifetime of the operating
    system. These inconsistencies might be caused by various hardware
    failures or might be caused by software issues. In some cases, these
    inconsistencies can affect the Windows servicing store, and they can
    cause software updates not to work. The System Update Readiness Tool
    tries to resolve these "

    Link to the x64 release:
    http://www.microsoft.com/downloads/d...f-0feefc7ff064

    Although the 80070490 error is not shown on the error code table IF
    there was an issue with the installation of the latest release of the
    Windows Update Agent then there's it's conceivable that this is the
    cause of the update being detected as needed instead rather than as
    installed.
    If CheckSUR does not resolve the error you can still check the 2 logs it
    created when it ran to see if there was an issue that it could not resolve:
    * %windir%\Logs\CBS\CheckSUR.log
    * %windir%\Logs\CBS\CheckSUR.persist.log

  4. #4
    Cybrarian Guest
    Heaven forbid I should use WINDOWS UPDATE to update Windows OMG what was I
    thinking?

    Now I'm getting this error on both of my 2008 servers... what am I supposed
    to do, come in on a Sunday to reinstall Windows, risking loosing AD?

    Why don't you write the updates correctly so they install correctly?

    Who are you talking to, cybermoron? No one here works for Microsoft.

  5. #5
    PA Bear [MS MVP] Guest

    Re: "WindowsUpdate_80070490" "WindowsUpdate_dt000"

    Heaven forbid you should begin your own, new thread about YOUR problem
    instead of hijacking someone else's thread from Oct-09!

    Heaven forbid you should quote my entire reply! ...which included a
    reference to:

    How to overcome error 0x80070490 when installing updates in Windows
    Vista/Server 2008
    http://blogs.msdn.com/andrekl/archiv...rver-2008.aspx

    Heaven forbid that you assume I work for or represent Microsoft! (I don't
    nor does anyone else here.)

  6. #6
    tong Guest
    I have tried a lot of times, but failed. Finanlly, I manually downloaded the
    KB, and clike on the download files to install, the outcome is successfully
    installed.

    And I suggest you find some references that are in English, so that the
    majority of people likely to read this will be able to understand the
    material you linked to!

    ....and I suggest you go fornicate yourself.

  7. #7
    Ashley Oviatt Guest

    How I Fixed this problem

    I combined a couple of these solutions and made up my own which I think is the easiest way to do it, no regedit needed, (which is a PITA on server 2008)

    Open the CBS log in notepad or wordpad here: %windir%\Logs\CBS\CBS.log

    Go to the bottom of the log file and search up on the word error. It should give you a line that looks something like this:

    2010-10-08 12:50:39, Error CBS Failed to resolve Package: Package_for_KB967723_winpesrv~31bf3856ad364e35~amd64~~6.0.1.7. hr: 0x80070490

    This is the line that gives us the info about which update is failing. It starts with KB######, or in our case KB96772.

    Now that we know which KB update is causing the problem, we can go download it from MS and install it manually. If it won't install manually, you can usually find out why by running it from the command line.

    Now re-run Windows update and it should bypass the failing update, because we did it manually, and the rest should install without problems!

  8. #8
    Jack Knoff Guest

    Re: How I Fixed this problem

    responding to a years old post and changing the subject,
    and posting three times.

  9. #9
    Zilbandy Guest

    Re: How I Fixed this problem

    Pot... kettle... black... for quoting the whole thing. :/

Similar Threads

  1. Replies: 5
    Last Post: 05-04-2011, 08:26 AM
  2. Replies: 6
    Last Post: 18-05-2010, 12:27 AM
  3. Replies: 4
    Last Post: 12-05-2009, 03:26 PM
  4. Replies: 1
    Last Post: 01-05-2009, 02:57 AM
  5. Replies: 1
    Last Post: 06-11-2007, 02:18 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,711,612,947.68836 seconds with 17 queries