The 0x80070490 windows update error means “Element not found” — Windows Update went looking for a component it expected to exist and came up empty. It commonly appears when installing apps from the Microsoft Store, running Windows Update, or upgrading Windows, and it almost always traces back to corruption in the component store. The 6 fixes below repair that corruption layer by layer, from quick scans to a full in-place upgrade.
If your update fails earlier — with the service itself refusing to start — our 0x80070422 fix guide is the right starting point instead.
What Causes the 0x80070490 Error?
The 0x80070490 code (HRESULT for “element not found”) fires when the servicing stack — the engine behind Windows Update — references a package, manifest, or registry entry that is missing or damaged. The most common root cause is corruption in the CBS (Component-Based Servicing) store or the WinSxS folder, often left behind by an interrupted update, a power cut during installation, or disk errors.
It also shows up when the local update database is out of sync: the SoftwareDistribution folder’s metadata says a package exists, but the actual files were deleted or never downloaded. Third-party “cleaner” utilities that aggressively purge WinSxS or the update cache are frequent culprits. The error additionally appears in the Microsoft Store and in Mail/Calendar account setup when the underlying app-package registration is broken — same code, same corruption family.
A less obvious trigger is a partially installed language pack or optional feature. When you add a language through Settings > Time & language > Language and the download stalls, the servicing stack records the feature as present while its payload is missing — and the next cumulative update trips over the gap with 0x80070490. Removing the half-installed language pack and re-adding it cleanly often clears the error without any deeper repair.
How to Fix the 0x80070490 Error
Fix 1: Repair the Component Store with DISM
DISM is the primary weapon against this error because it rebuilds exactly the store that is corrupted.
- Open an elevated Terminal or Command Prompt (right-click Start, choose Terminal (Admin)).
- Run the health checks first:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth - Then run the repair: DISM /Online /Cleanup-Image /RestoreHealth
- Let it reach 100% without interrupting it — this typically takes 15–30 minutes.
- Restart your PC and try the update again.
Fix 2: Run SFC After DISM
SFC repairs individual system files using the store DISM just fixed — always run it second.
- In the same elevated prompt, run: sfc /scannow
- Wait for the verification to complete.
- If SFC reports it fixed files, restart and retry the update. If it reports unfixable corruption, repeat Fix 1 — DISM sometimes needs two passes on badly damaged stores.
Fix 3: Reset the Windows Update Components
This clears the out-of-sync metadata that triggers “element not found.”
- Open an elevated Command Prompt.
- Stop the services:
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver - Rename the cache folders:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old - Restart the services:
net start wuauserv
net start cryptSvc
net start bits
net start msiserver - Restart the PC and check for updates.
Fix 4: Run the Windows Update Troubleshooter
The troubleshooter re-registers missing update components automatically.
- Open Settings > System > Troubleshoot > Other troubleshooters (Windows 11) or Settings > Update & Security > Troubleshoot > Additional troubleshooters (Windows 10).
- Click Run next to Windows Update.
- Apply every fix it recommends, restart, and test.
- If the error appeared in the Microsoft Store instead, run the Windows Store Apps troubleshooter from the same page.
Fix 5: Install the Update Manually from the Update Catalog
A manual install bypasses the corrupted metadata path entirely.
- Find the failing KB number in Settings > Windows Update > Update history.
- Search for it on the Microsoft Update Catalog and download the build matching your system (x64 for most PCs).
- Run the downloaded .msu file and follow the prompts.
- Restart if requested, then confirm the update in your update history.
Fix 6: Perform an In-Place Upgrade
When the servicing stack itself is too damaged for DISM, reinstalling Windows over itself rebuilds everything.
- Download the Windows 11 (or Windows 10) Media Creation Tool from Microsoft’s official download page and create installation media, or download the ISO directly.
- Mount the ISO (double-click it) or run setup.exe from the USB — while booted into Windows, not from boot.
- Choose Keep personal files and apps when asked what to keep.
- Let the upgrade complete (30–60 minutes). Your files and programs survive, and the component store is rebuilt from scratch.
- Run Windows Update afterward — it should now proceed normally.
How to Prevent This Error
- Never interrupt Windows Update — sudden shutdowns mid-install are the top cause of store corruption.
- Do not let cleaner tools delete WinSxS contents or the SoftwareDistribution folder.
- Keep 20+ GB free on the system drive so the servicing stack never runs out of staging space.
- Run chkdsk C: /f periodically if your drive is aging; bad sectors corrupt exactly these files.
- Use a UPS or surge protector to survive power cuts during updates.
- Apply updates regularly instead of letting a year’s worth queue up.
FAQs
What does error 0x80070490 mean?
It translates to “Element not found.” The Windows servicing stack expected a package, manifest, or registry entry to exist and it did not — almost always because the component store (CBS/WinSxS) is corrupted.
Why do I get 0x80070490 in the Microsoft Store?
The Store uses the same servicing infrastructure as Windows Update. Broken app-package registrations produce the identical code. The DISM/SFC fixes and the Windows Store Apps troubleshooter resolve the Store variant too.
Will DISM delete my files?
No. DISM /RestoreHealth only repairs Windows system components using clean copies from Windows Update or your installation media. Personal files, apps, and settings are untouched. Microsoft documents the DISM repair flow at learn.microsoft.com.
How long does an in-place upgrade take?
Typically 30–60 minutes on an SSD, longer on a hard drive. It keeps your files and apps, but back up anything irreplaceable first — standard practice before any OS-level operation.
Can 0x80070490 come back after fixing?
It can if the underlying cause persists — most often a failing drive re-corrupting the store, or a cleaner utility scheduled to purge WinSxS. If the error recurs within weeks, check drive health with chkdsk and audit your maintenance tools.
Does 0x80070490 affect Windows 10 the same as Windows 11?
Yes. The servicing stack works identically on both, and every fix in this guide applies to Windows 10 and 11. Only the Settings navigation differs slightly — on Windows 10 the troubleshooter lives under Settings > Update & Security > Troubleshoot > Additional troubleshooters.
Should I delete the SoftwareDistribution folder manually?
Do not delete it outright while the update services are running — that can make things worse. The safe method is Fix 3: stop the services first, then rename the folder so Windows rebuilds it. Renaming instead of deleting also gives you a fallback if something goes wrong.
Conclusion
Error 0x80070490 is the servicing stack telling you a piece it needs has gone missing. DISM plus SFC is the definitive repair for the majority of cases, the component reset handles the metadata side, and the in-place upgrade is the reliable finisher when corruption runs deep. Work the list in order and updates will be installing cleanly again.
