Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | 0x80070490 (ERROR_NOT_FOUND) | Event Viewer, CBS log | -> DISM or WindowsUpdateClient |
| Affected build range | Windows 10/11 | Microsoft Docs | |
| Registry key involved | HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages | Registry Editor | -> missing or corrupt entries |
| Relevant service/endpoint URL | https://www.catalog.update.microsoft.com/ | Microsoft Update Catalog | -> download SSU |
| Log line signature | 0x80070490 Not found | DISM log, CBS log | |
Log Files to Check
C:\Windows\Logs\CBS\CBS.logC:\Windows\Logs\DISM\dism.log
What This Error Actually Means
The error code 0x80070490, also known as ERROR_NOT_FOUND, is a generic failure that occurs when the Windows operating system or its components cannot find a specific registry entry, service, or file. This error can be raised by various Windows services and APIs, including Component-Based Servicing (CBS), DISM (Deployment Image Servicing and Management), and Windows Update. The core issue behind this error is often related to missing or corrupted entries in the Windows component store (WinSxS) or registry hives that are critical for system updates and maintenance operations.
Affected Versions and Scope
This error affects all versions of Windows 10 and Windows 11, impacting both client and server editions. It is particularly prevalent in environments where frequent updates are applied through Windows Update or via Group Policy Objects (GPOs). The error does not affect older Windows builds such as Windows 7 or 8.x unless they have been upgraded to a newer version of Windows that falls under the affected range.
Where To Look First: Logs and Event IDs
When encountering this issue, the first step is to locate relevant logs where the error message is recorded. The primary log files are:
-
C:\Windows\Logs\CBS\CBS.log: This file contains detailed records of Component-Based Servicing operations. Search for lines containing '0x80070490' and 'Not found'.
-
C:\Windows\Logs\DISM\dism.log: DISM logs are essential when dealing with feature installation or servicing failures. Look for entries mentioning the error code along with specific component identities that were not found.
- Windows Update log: Use PowerShell to convert ETL files into human-readable format by running
Get-WindowsUpdateLog. This command will generate a file named Desktop\WindowsUpdate.log which should be searched for '0x80070490'.
- Event Viewer > System: Filter events from DISM or Microsoft-Windows-WindowsUpdateClient sources. Pay attention to Event ID 76, as it often includes the result code 0x80070490.
Root Causes
The error can stem from several root causes:
- Missing or Corrupted Component Store Entries
This occurs when a previous update attempt was interrupted, leaving behind orphaned entries in the component store. To identify this issue, check for the presence of a pending.xml file at C:\Windows\WinSxS\Pending.xml. If found, it indicates that an operation is stalled and blocking further updates.
- Registry Hive Corruption or Incomplete Entries
The registry hive located at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages may contain corrupt entries for the update being installed. Use PowerShell to inspect this key and look for any missing or incomplete package entries that correspond to the failing KB number.
- Incomplete Servicing Stack Update (SSU)
Certain cumulative updates require a specific SSU to be installed beforehand. If an essential SSU is missing, it can prevent subsequent updates from proceeding correctly. Verify the installed SSU against the latest available in the Microsoft Update Catalog for your OS build.
Fix Procedure
To resolve this issue, follow these steps:
1. Run DISM component store health check:
Invoke-Expression 'DISM /Online /Cleanup-Image /ScanHealth'. If it reports that the component store is repairable, proceed with:
Invoke-Expression 'DISM /Online /Cleanup-Image /RestoreHealth'.
2. Execute System File Checker to repair any corrupt files:
sfc /scannow
3. Check for a pending.xml stall:
Use PowerShell to test the presence of this file: Test-Path 'C:\Windows\WinSxS\Pending.xml'. If present, it indicates an ongoing operation that needs resolution.
4. Inspect component store package registry entries:
Run Get-ChildItem 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages' | Where-Object {$_.Name -match ''}. Look for any missing or incomplete entries related to the failing KB.
5. Ensure that the required SSU is installed:
Download and install the latest SSU from Microsoft Update Catalog using: wusa.exe /quiet /norestart.
6. Remove pending.xml if necessary (caution advised):
Backup the file first, then remove it with PowerShell commands:
Rename-Item 'C:\Windows\WinSxS\Pending.xml' 'Pending.xml.bak'
Follow up by running: DISM /Cleanup-Image /RevertPendingActions. This step should only be taken if the system has been stuck in a pending state for multiple reboots.
7. Reset Windows Update:
Stop services and clear download cache with PowerShell commands:
Stop-Service wuauserv; Stop-Service bits; Remove-Item 'C:\Windows\SoftwareDistribution\Download' -Recurse -Force; Start-Service wuauserv; Start-Service bits.
Warning: Removing pending.xml can cause system instability if not performed correctly. Ensure you have a backup before proceeding.
Tip: Use Get-WindowsUpdateLog to quickly check for new 0x80070490 entries after applying fixes, which helps in verifying the resolution without manually searching logs.
Error Code Variants
| Error Code | Description |
| 0x80070651 (ERROR_INVALID_DATA) | This error indicates that the data passed to a function is invalid or corrupted. |
| 0x80070424 (ERROR_BAD_NETPATH) | Suggests an issue with network paths, often related to connectivity problems rather than missing components. |
Verification
After applying the fixes, retry the failed Windows Update operation. Confirm that it completes successfully by checking the DISM log for a line stating 'The operation completed successfully.' Additionally, run
Get-WindowsUpdateLog to ensure no new 0x80070490 entries appear in the logs.
Prevention
To prevent recurrence of this issue:
- Ensure that all updates are installed fully and without interruptions.
- Regularly check for missing or outdated Servicing Stack Updates (SSUs) before applying cumulative updates.
- Implement policies to monitor and manage pending.xml files, ensuring they do not accumulate indefinitely.
By following these guidelines and maintaining a robust update management process, you can significantly reduce the likelihood of encountering error 0x80070490 in your Windows environment.