Windows Update error 0x80070490, explained and fixed

0x80070490 is ERROR_NOT_FOUND, “element not found”: the servicing stack went looking for a package or component the update’s manifest references, and it was not there. It shows up during cumulative and feature update installs, often after a previous update was partially removed or its registration damaged.

The fix, in order

  1. Run the Windows Update troubleshooter. Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run. It catches stopped services, cache problems, and registration faults automatically.
  2. Repair the component store and system files. From an admin Command Prompt: DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. Restart afterwards; a repaired store often lets the same update sail through on the next attempt.
  3. Reset the Windows Update components. In an admin Command Prompt, stop the services: net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver. Rename C:\Windows\SoftwareDistribution to SoftwareDistribution.old and C:\Windows\System32\catroot2 to catroot2.old, then restart the four services with net start. This rebuilds the download cache and the update database from scratch.
  4. Manually install the prerequisite or the update itself. Servicing stack updates (SSUs) must be current for cumulative updates to find everything they reference; install the latest SSU for your build from the Microsoft Update Catalog, then the failing cumulative update, also manually.
  5. Check the CBS log for the missing element’s name. The tail of C:\Windows\Logs\CBS\CBS.log after a failed attempt usually names the package that was not found, which tells you exactly what to install or repair.

If it still happens

When DISM cannot restore the store from Windows Update, feed it the installation media as source (DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim /LimitAccess with the mounted ISO’s letter). If the store still references ghosts afterward, an in-place repair install rebuilds package registration completely.

Common questions

What “element” is not found, exactly? A component package the new update expects to build on, often a prior cumulative update’s component or a feature-on-demand package whose registration was lost. The CBS log names it; the fix is restoring that registration, which DISM and manual installs do.

It started after I ‘cleaned up’ old updates. Related? Very possibly. Aggressive cleanup that removes component versions still referenced by the store leaves dangling references like this. DISM’s StartComponentCleanup is the supported cleanup; if a third-party tool went further, DISM RestoreHealth and, failing that, the repair install are the way back.

Related errors

Windows Update error 0x80073712 · Windows Update error 0x800f0900 · Windows Update error 0x800f081f