Under the miniscule prism

Error 0x80070490

Windows Update Error 0x80070490

ELEMENT NOT FOUND

 

SYNOPSIS

 

Error 0x80070490 usually appears in Windows Vista Operating Systems. This is caused by a registry key of an update that was either removed or was patched by another update. This registry entry still remains and is being indexed by the Component Based Servicing (CBS) registry key but no longer exists as an installed update. If this error is on XP, this may appear if there was a previous error during installation or removal of an update. The package was removed but a registry entry of the update was not deleted.

In resolving issues of 0x80070490 requires a log file called CHECKSUR.LOG (Check System Update Readiness log) without it we would not be able to find what CBS PACKAGE registry key needs to be removed or deleted. CheckSUR is only available in Windows Vista platforms and not on Windows XP.

A CHECKSUR.LOG would require downloading the System Update Readiness Tool (KB947821). A CBS.LOG will only be used as point of reference in case CheckSUR was not able to determine the issue.

 

TROUBLESHOOTING

 

CREATING LOGS

1.     Creating a CBS log:

a.     Running the System File Checker could resolve your issues altogether. SFC checks and resolves inconsistencies or corruption of the System files it found.

b.    Use SFC /SCANNOW on an elevated Command Prompt if you are using Vista.

 

! WARNING: Do not use SFC /SCANNOW if you are on XP with SP3. Files previously patched by SP3 will need an XPSP3 slipstreamed CD if any System files needs replacing. Overwriting SP3 files using an older version of an XP media other than SP3 will cause more damage to the Operating System. There is a Workaround for this by extracting the i386 folder from the SP3 standalone package and to point SFC where the i386 SP3 files were extracted by modifying a Registry entry.

 

2.     Running CheckSUR:

a.     The Windows Vista Check for System Update Readiness (CheckSUR) tool will try to fix certain Windows Update installation failures. 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 may be caused by various hardware failures or by software issues. In some cases, these inconsistencies can affect the Windows Servicing Store, and they can cause a Windows Vista update to fail. When the update fails, it blocks the user from installing updates and service packs. CheckSUR addresses this issue. When Windows Update detects inconsistencies that are related to system servicing in system files or in the registry, Windows Update offers CheckSUR as an available update package.

b.    To manually install and run CheckSUR, follow these steps:

·         Click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

·         In the User Account Control dialog box, click Continue.

·         Type REG ADD HKLMCOMPONENTS /v StoreCorruptTimeStamp /t REG_SZ /d “0″ /f, and then press ENTER.

·         Type REG DELETE HKLMSOFTWAREMicrosoftWindowsCurrentVersionCheckSUR, and then press ENTER.

·         Download and then install CheckSUR from the Microsoft Download Center KB947821.

·         As soon as the file has been successfully downloaded, double-click the file to install and run CheckSUR.

·         We recommend that you restart your computer after you run CheckSUR to make sure that any changes take effect.

·         Additionally, you must try to reinstall any software updates that previously could not be installed.

·         If CheckSUR detected and fixed the cause of the failures, these updates will now install successfully.

·         If CheckSUR failed proceed to 3. Analysis is at step 4.

 

INTERPRETING LOGS

3.     Launching CBS or CHECKSUR logs using Notepad:

a.     Open a Command Prompt, in Vista run Command Prompt as Administrator.

b.    For CBS.LOG, type in: Notepad %WINDIR%logsCBSCBS.log

c.     For CheckSUR.LOG, type in: Notepad %WINDIR%logsCBSCheckSUR.log

d.    If an MSDT cab file was gathered, this will be the [12_1]CBS.log and the [12_3]CheckSUR.log.

 

4.     Analyzing the CBS and CHECKSUR logs.

a.     In the CBS.log scroll to the bottom and use FIND in an upward direction and “Match Case” to look for the recent Error. This will point out errors for either corrupted services, components or missing files. Take note of the any failure or error. This will help you in troubleshooting the issue later. You should also see a “Failed to resolve status… hr: 0x80070490”, somewhere in the string which means you are looking at the specific KB Package that is causing your issue. Make sure you collect all Errors until the most recent date only. It may not only be one KB Package but a set of packages that may also have the same error string.

 

What to look for?

 

                2009-08-21 12:42:28, Error CBS Failed to resolve Package: Package_for_KBXXXXXX~31bf3856ad364e35~x86~~6.0.22.0. hr: 0x80070490

ü X is a number.

If you need more info on reading CBS logs Microsoft has a Knowledge Base entry for learning how to read CBS.log – http://support.microsoft.com/kb/928228.

 

ü REMEMBER The CheckSUR.log is a precise view of what Package is causing the error. CheckSUR was also designed to be able to resolve specific functionality and compatibility issues of Windows Update. If you don’t have a CheckSUR log it will be advisable for you to download and run the Windows Update System Readiness Tool from http://support.microsoft.com/kb/947821 use the appropriate package for your platform (32bit or 64bit Note: CheckSUR only works for Vista!)

 

RESOLUTION

5.     Now that you have the name of the Package that is causing the error you need to locate this in the Registry:

a.     Open Registry Editor.

b.    Look for this Registry Key

HKLMsoftwareMicrosoftWindowsCurrentVersionComponent Based Servicing

c.     Once in this Registry key, look for the PACKAGE that is causing your issue.

d.    EXPORT first the Registry key and then DELETE it.

e.     Try to Check for Updates again.

 

ü REMEMBER if the cause is “Package_for_KBXXXXXX~31bf3856ad364e35~x86~~6.0.22.0” This is the exact key under Component Based Servicing that you MUST delete.

 

Resources:

 

Optional Component Setup Log Diagnoser – http://technet.microsoft.com/en-us/library/cc732334(WS.10).aspx

Description of the System Update Readiness Tool for Windows Vista – http://support.microsoft.com/kb/947821

Understanding Component-Based Servicing: http://blogs.technet.com/askperf/archive/2008/04/23/understanding-component-based-servicing.aspx

How to Overcome Error 0x80070490: http://blogs.msdn.com/andrekl/archive/2008/09/29/how-to-overcome-error-0x80070490-when-installing-updates-in-windows-vista-server-2008.aspx

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s