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?
--
Useless IT manager that would die if not for resources like this....
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/archive/2008/09/29/how-to-overcome-error-0x80070490-when-installing-updates-in-windows-vista-server-2008.aspx
Or see the "How to obtain help" section of
http://support.microsoft.com/kb/967723
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Client - since 2002
"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/details.aspx?FamilyId=f6f353c0-d00e-43e7-97ef-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
MowGreen
===============
*-343-* FDNY
Never Forgotten
===============
banthecheck.com
"Security updates should *never* have *non-security content* prechecked"
"PA Bear [MS MVP]" wrote:
> 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
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.
--
"Don't pick a fight with an old man.
If he is too old to fight, he'll just kill you."
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/archive/2008/09/29/how-to-overcome-error-0x80070490-when-installing-updates-in-windows-vista-server-2008.aspx
Heaven forbid that you assume I work for or represent Microsoft! (I don't
nor does anyone else here.)
PS: Bite me.
tong
> .
>
==========================================================
"PA Bear [MS MVP]" wrote:
--
"Don't pick a fight with an old man.
If he is too old to fight, he'll just kill you."
"thepeartree" <thepe...@discussions.microsoft.com> wrote in message
news:6459072D-25EF-4662...@microsoft.com...
> Or see the "How to obtain help" section of
> http://support.microsoft.com/kb/967723
...don't you understand?
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!
>> On Thursday, October 15, 2009 2:09 PM PA Bear [MS MVP] wrote:
>> Courtesy of MVP TauArian:
>>
>> 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 is anything you have not tried -
>>
>> How to overcome error 0x80070490 when installing updates in Windows
>> Vista/Server 2008
>> http://blogs.msdn.com/andrekl/archive/2008/09/29/how-to-overcome-error-0x80070490-when-installing-updates-in-windows-vista-server-2008.aspx
>>
>> Or see the "How to obtain help" section of
>> http://support.microsoft.com/kb/967723
>> --
>> ~Robear Dyer (PA Bear)
>> MS MVP-IE, Mail, Security, Windows Client - since 2002
>>
>>
>> Dragnet wrote:
>>> On Thursday, October 15, 2009 6:09 PM MowGreen wrote:
>>> 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/details.aspx?FamilyId=f6f353c0-d00e-43e7-97ef-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 is it is 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
>>>
>>> MowGreen
>>> ===============
>>> *-343-* FDNY
>>> Never Forgotten
>>> ===============
>>>
>>> banthecheck.com
>>> "Security updates should *never* have *non-security content* prechecked"
>>>
>>>
>>>
>>> PA Bear [MS MVP] wrote:
>>>> On Friday, January 29, 2010 5:14 PM Cybrarian wrote:
>>>> "PA Bear [MS MVP]" wrote:
>>>>
>>>>
>>>> Heaven forbid I should use WINDOWS UPDATE to update Windows OMG what was I
>>>> thinking?
>>>>
>>>> Now I am 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 do not you write the updates correctly so they install correctly?
>>>>> On Friday, January 29, 2010 5:23 PM Michael wrote:
>>>>> Who are you talking to, cybermoron? No one here works for Microsoft.
>>>>> --
>>>>>
>>>>>
>>>>> "Don't pick a fight with an old man.
>>>>> If he is too old to fight, he will just kill you."
>>>>>> On Friday, January 29, 2010 7:13 PM PA Bear [MS MVP] wrote:
>>>>>> Cybrarian wrote:
>>>>>>
>>>>>> 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/archive/2008/09/29/how-to-overcome-error-0x80070490-when-installing-updates-in-windows-vista-server-2008.aspx
>>>>>>
>>>>>> Heaven forbid that you assume I work for or represent Microsoft! (I do not
>>>>>> nor does anyone else here.)
>>>>>>
>>>>>> PS: Bite me.
>>>>>>> On Thursday, February 04, 2010 3:05 AM tong wrote:
>>>>>>> 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.
>>>>>>>
>>>>>>> tong
>>>>>>>
>>>>>>> "PA Bear [MS MVP]" wrote:
>>>>>>>> On Monday, February 15, 2010 8:25 AM thepeartree wrote:
>>>>>>>> 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!
>>>>>>>>
>>>>>>>> ==========================================================
>>>>>>>>
>>>>>>>> "PA Bear [MS MVP]" wrote:
>>>>>>>>> On Monday, February 15, 2010 10:32 AM Michael wrote:
>>>>>>>>> ...and I suggest you go fornicate yourself.
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> "Don't pick a fight with an old man.
>>>>>>>>> If he is too old to fight, he will just kill you."
>>>>>>>>>> On Monday, February 15, 2010 12:21 PM PA Bear [MS MVP] wrote:
>>>>>>>>>> What part of...
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ...do not you understand?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> thepeartree wrote:
>>>>>>>>>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>>>>>>>>> Lucene.Net Indexing Searching Entry Level Tutorial
>>>>>>>>>> http://www.eggheadcafe.com/tutorials/aspnet/c69ef65f-e3c6-409e-ab97-168897c74f83/lucenenet-indexing-searching-entry-level-tutorial.aspx
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!
> On Thursday, October 15, 2009 12:22 PM Dragnet wrote:
>>>>>>>>>>> On Friday, October 08, 2010 3:22 PM Ashley Oviatt wrote:
>>>>>>>>>>> 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!
>>>>>>>>>>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>>>>>>>>>> Silverlight Binary Serialization and Compression with WCF Services
>>>>>>>>>>> http://www.eggheadcafe.com/tutorials/aspnet/96487d4c-d92f-4ca5-85b7-0fef6f42d6c3/silverlight-binary-serialization-and-compression-with-wcf-services.aspx
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!
> On Thursday, October 15, 2009 12:22 PM Dragnet wrote:
>>>>>>>>>>>> On Friday, October 08, 2010 3:24 PM Ashley Oviatt wrote:
>>>>>>>>>>>> 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!
>>>>>>>>>>>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>>>>>>>>>>> SharePoint Create List Add/Edit Form Web Part With Custom Toolbar and Attachments Option
>>>>>>>>>>>> http://www.eggheadcafe.com/tutorials/aspnet/bdae9c53-4661-4144-90f9-5d4a5dfa737c/sharepoint-create-list-addedit-form-web-part-with-custom-toolbar-and-attachments-option.aspx
"Ashley Oviatt" <ash...@vmt-tech.com> wrote in message
news:201010815...@eggheadcafe.com...
>Egghead HoopleHead, responding to a years old post and changing the subject,
>and posting three times.
Pot... kettle... black... for quoting the whole thing. :/
--
Zilbandy