Windows Error 0x80070490: Element Not Found

Error 0x80070490 means "Element not found": a Windows component went looking for a registry entry, package record or data item that should exist and could not find it. You meet it in Windows Update, the Microsoft Store, the Mail app and Windows backup, and each of those leans on the same servicing store. The usual cure is to repair that store with DISM, reset the Store, and re-register the built-in apps.

What is "not found" when Windows says element not found

The code is the Windows result for a failed lookup. An "element" can be a registry key under the servicing tree, an entry in the list of installed packages, or an app's data record. When Windows Update, the Store, or the Mail app asks for something that the system believes is installed and it is not there, the answer is 0x80070490.

That explains why the error crosses apps. The component store (CBS, short for Component-Based Servicing) records which Windows features and updates are installed. Update uses it to decide what to apply, backup reads it, and many inbox apps are installed through packages that it tracks. When one of those records is missing, whichever feature touches it first reports the failure.

Where it tends to appear

Where you see it	How to recognise it	Fix section
Windows Update	"There were some problems installing updates" with the code, retries fail the same way	Servicing store repair
Microsoft Store	Store will not open, or downloads fail with the code	Reset the Store
Mail and Calendar app	Adding or syncing an account fails with the code	Reset or re-register Mail
Windows backup or restore point	Backup fails right at the start, or restore point creation fails	Check the backup-related services
Only one user account on the PC	A new account works normally	Profile test
After a failed update or a cleaner tool	A registry cleaner or interrupted update came first	Servicing store repair, then system restore

Start here: find out what is actually missing

Windows records servicing failures in a text log. Looking at it takes two minutes and often saves an hour. Open File Explorer and go to C:\Windows\Logs\CBS, then open CBS.log in Notepad (it can be large). Use Find to search for "0x80070490" or the word "Error". Lines near the match name the package or key that could not be found. You do not need to understand every line; note the package name and whether the failure happens repeatedly on the same item.

If the log mentions a specific update package, the fix in the next section normally removes the stale record. If it names an app package instead, jump to the Store and app re-registration sections.

Fix 1: Repair the servicing store

Open Command Prompt as administrator (search for cmd, right-click, Run as administrator) and run the commands in this order, letting each one finish:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
DISM /Online /Cleanup-Image /StartComponentCleanup

The first command compares the store with a clean source and repairs what it can. The scan checks protected system files. The third removes superseded component versions, which also helps clear half-finished entries left by interrupted updates. Restart the PC afterwards.

If DISM stops with a source-files error, the related guides on error 0x800f081f and error 0x80073712 explain how to supply a source from a mounted ISO.

Fix 2: Restart and test the update stack services

Several services must be present and able to start for updates and backup to run. Open services.msc and check that the following are not disabled: Windows Update, Background Intelligent Transfer Service, Cryptographic Services, and Volume Shadow Copy. Set them to Manual or Automatic as they were by default, start them, and retry. A service disabled by a "tweak" utility is a surprisingly common source of element-not-found failures.

Fix 3: Reset the Microsoft Store cache

If the Store itself is the symptom, clear its local cache. Press Windows+R, type wsreset.exe and press Enter. A blank command window opens for a short time, then the Store launches on its own. Do not close the window early. This resets cached Store data only; it does not remove apps you installed and does not touch your account.

If wsreset does not help, open Settings, then Apps, then Installed apps (Apps and features on Windows 10), find Microsoft Store, open Advanced options, and use Repair first and then Reset if Repair changes nothing. Reset clears the app's data, so you may need to sign in to the Store again.

Fix 4: Re-register the Store and built-in apps with PowerShell

When the Store package record itself is damaged, re-registering it tells Windows to rebuild its entry from the files already on disk. Right-click Start, open Terminal (Admin) or Windows PowerShell (Admin), and run:

Get-AppxPackage -AllUsers Microsoft.WindowsStore | ForEach-Object { Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml" }

For a broader refresh that covers the Mail app and other inbox apps, this longer variant re-registers every app package for all user profiles on the PC and hides error messages. Create a restore point first (search for "Create a restore point"). Use it only if the single-app command did not work. Some apps may fail to register, which is normal for packages that are in use or not applicable to your edition:

Get-AppxPackage -AllUsers | ForEach-Object { Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml" -ErrorAction SilentlyContinue }

Run it once, wait until the prompt returns, and restart. Treat this as a heavier tool than the single-app version and only use it if the simpler one did not work.

Fix 5: The Mail and Calendar variant

When 0x80070490 shows while adding a Gmail, Outlook.com or other account in the Windows Mail app, the cause is usually a damaged app data record rather than the account itself. Try these steps in sequence:

1. Sign in to the same mailbox in a web browser to confirm the account and password are fine.
2. Open Settings, then Apps, then Installed apps, select Mail and Calendar, then Advanced options, and click Terminate, Repair and then Reset.
3. If it still fails, run the re-registration command from the previous section, restart, and add the account again.
4. Check that Settings, then Privacy and security, then Email shows access allowed for the app.

Microsoft ended support for the Windows Mail and Calendar apps on December 31, 2024, and recommends the new Outlook for Windows or Outlook.com. If you still use the old app, an error there may be a sign it is no longer maintained, so move to the new Outlook before spending long on a repair.

Fix 6: When backup or restore points fail with this code

Backup tools and System Restore depend on Volume Shadow Copy and on a readable servicing store. If a backup job or restore point creation fails with the error, check these in order:

• In services.msc, make sure Volume Shadow Copy and Microsoft Software Shadow Copy Provider are not disabled.
• Run vssadmin list writers in an elevated prompt. Writers shown as failed or waiting for completion often clear after a restart.
• Confirm that System Protection is turned on for the system drive (search for "Create a restore point", select the drive, and open Configure).
• Make sure the backup destination has free space and is connected.

Windows Backup specifics differ between builds and the exact wording on screen changes, so treat the sequence above as community-reported guidance, not an official script. The servicing repair from Fix 1 resolves many of these cases too.

Fix 7: Test with a new user account

If the problem only affects one user's apps, the damage may be in that profile and not in Windows. Create a temporary local administrator account under Settings, then Accounts, then Other users, sign in to it, and try the Store or Mail there. If the apps work, you know the system is healthy and the original profile's app data is the issue. In that case, copying documents to the new profile is often faster and safer than repeated repairs, and it avoids an in-place reinstall.

Fix 8: Roll back with System Restore

If the error began right after a specific event, such as a driver install, a registry cleaner, or an interrupted update, a restore point from before it can undo changes to system registration. Open the Start menu, search for "Create a restore point", choose System Restore, and select the latest point dated before the problem began. Your personal files are not removed by System Restore, but programs installed since that date may be.

What not to do when Windows reports "Element not found"

• Do not use registry cleaners or "one-click fix" downloads. Missing records are the problem; tools that delete more records tend to widen it.
• Do not edit servicing keys in the registry by hand following forum posts for a different Windows build. Entries differ between releases.
• Do not remove the Microsoft Store entirely in the hope that Windows reinstalls it. Re-register it instead.
• Do not rerun the same failed update ten times. If the first two fail identically, repair the store before trying again.
• Do not disable services permanently to "speed up" Windows. Several of them are what backup and Update need.

When to get a professional involved

Element-not-found errors are about records, so data loss is uncommon, but the pattern can hide a deeper fault. Ask for help if:

• DISM and sfc report errors they cannot repair, even after a second attempt.
• The CBS log shows repeated read failures or disk I/O errors.
• The error is joined by freezing, files that will not open, or stop errors.
• The machine holds business or irreplaceable files and your last backup is old.
• A new user account has the same problem, which suggests system-level damage.

Our remote repair service can inspect the CBS log, run the repair sequence and re-register apps in a supervised session, and the Windows support page lists related help. If updates are the main issue, the guide to Windows Update stuck or failing adds more steps, and the page on error 0x80070005 covers the permission-related cousin of this problem.

Keeping the servicing store healthy

• Let updates finish and restart normally instead of forcing a shutdown mid-update.
• Skip registry cleaners and aggressive "debloat" scripts that remove inbox apps.
• Keep services at their default start types unless you know why you are changing one.
• Run a backup regularly and test that restore points are being created.
• Keep free space on the system drive for servicing operations.
• Run DISM /RestoreHealth once after any crash that interrupted an update.

FAQ

What does Windows error 0x80070490 mean?

It means "Element not found". A Windows component looked for a registry entry or package record that should exist and could not find it.

Why does 0x80070490 appear in both Windows Update and the Microsoft Store?

Both rely on the servicing store and package records. Damage to those records can break any feature that reads them, so the same code appears in different apps.

Does wsreset delete my apps?

No. wsreset clears the Store's cache only. Your installed apps and account stay in place.

Is re-registering apps with PowerShell safe?

Generally yes. It rebuilds app registrations from files already on disk. Run the single-app version first and use the all-apps version only if needed.

Why does the Mail app show 0x80070490 when I add an account?

The cause is often damaged app data rather than the mailbox itself. Test the account in a browser, then repair or reset the app and re-register it if needed.

Can this error stop Windows backup?

It can. Backup and restore points depend on Volume Shadow Copy and a readable servicing store. Check the services, run the DISM repair and retry.

How can I tell whether the problem is my profile or Windows?

Create a new local user and test the failing app there. If it works, the issue sits in your original profile's data.

Will I need to reinstall Windows?

Rarely. Servicing repair, Store reset, app re-registration and System Restore fix most cases without a reinstall.