Recommended Free Tools
Error 0x00000490 is the Windows Win32 code ERROR_NOT_FOUND, displayed as “Element not found.” It is a generic missing-element message, not a diagnosis of one failed part. The correct fix depends on what Windows was doing when it appeared—installing a driver, running Windows Update, adding a printer, installing an application, or configuring another component. Record that context first, then follow the matching procedure below.
What error 0x00000490 means
Windows uses 0x00000490 when an operation asks for an element that cannot be found. The missing element might be a driver value, a device entry, a printer connection, a service, or an installation component. The hexadecimal number alone cannot identify which one is absent.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Microsoft Windows 11 (USB) | $128.99 | Buy on Amazon |
| 2 |
|
Tech-Shop-pro Compatible with install Key Included USB For Windows 11 Home OEM Version 64 bit.... | $48.00 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
You may see the code in a short dialog, an update history entry, a printer setup failure, Device Manager, or an installer log. A closely related code, 0x80070490, is the same underlying ERROR_NOT_FOUND condition with an HRESULT-style prefix. Treat both as symptoms and use the operation that failed to choose a remedy.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The code does not by itself indicate malware, a damaged hard drive, or a dead printer. Do not buy a replacement component or edit random registry keys until you know which Windows component reported the error.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
Capture the failure context before changing anything
Write down the exact action that produced the message. This prevents a printer-specific repair from being applied to Windows Update, and prevents a risky registry change from being made for an unrelated application.
- The complete dialog text and whether it shows 0x00000490 or 0x80070490.
- What you clicked immediately before the error: Windows Update, a driver installer, Add device, a printer wizard, an application setup program, or another task.
- Your Windows edition and build. Press
Windows key + R, enterwinver, and press Enter. - The device or printer model, connection type, and whether the problem began after an update, uninstall, or software installation.
- Any KB number, driver name, setup log entry, or Event Viewer error shown near the failure.
Windows 10 reached end of support on October 14, 2025. The troubleshooting steps below still apply to an installed Windows 10 system, but security and feature updates are no longer generally provided, so plan a supported upgrade where your hardware permits it.
Use Device Manager to identify the missing device element
Device Manager is the fastest way to connect a generic code with a physical device or driver.
- Right-click Start and select Device Manager, or press
Windows key + R, typedevmgmt.msc, and press Enter. - Expand categories related to the failure, such as Printers, Print queues, Display adapters, Network adapters, Universal Serial Bus controllers, or Other devices.
- Look for a yellow warning icon, an unknown device, or a device that disappeared after the failed installation.
- Right-click the device and choose Properties. Read the message on the General tab, then inspect Driver, Details, and Events.
- Record the device name, provider, driver date and version, hardware IDs, and the most recent event. Those details identify the component that Windows could not find.
If Device Manager shows no relevant device, the problem may be a printer queue, Windows servicing metadata, or an application component rather than a directly detected hardware failure. Continue with the section that matches the original operation.
When Windows Update or a driver update fails
Microsoft documents 0x80070490 as a driver-installation update problem that can occur when architecture information is missing from the DriverOperations registry area. This is a targeted procedure for that scenario, not a general cure for every appearance of 0x00000490.
First try the low-risk update checks
- Restart Windows and retry the update once. A restart can release a pending servicing operation.
- Open Settings > Windows Update and select Check for updates. Install any servicing update that is offered before retrying the device or driver update.
- Open Settings > Windows Update > Update history and note the failed update’s name and KB number.
- In Device Manager, open the affected device’s Properties > Driver tab. Record the current version before changing it. If Windows offers Roll Back Driver and the problem began immediately after an update, rolling back can restore the previous working driver.
- Disconnect nonessential USB devices, restart, and retry. A competing device or stale enumeration can make Windows select the wrong installation target.
Check the DriverOperations registry entry
Back up the registry or create a restore point before editing it. Registry changes affect the whole installation; an incorrect value can prevent a driver operation from completing.
- Press
Windows key + R, typeregedit, and press Enter. Approve the User Account Control prompt. - Navigate to
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionComponentBasedServicingDriverOperations. - Open the sequence subkey identified by the failed operation, represented in Microsoft’s procedure as
02(SequenceID). Do not assume the literal sequence number is always 2; use the sequence associated with the failure. - Review the
Identityvalue. It identifies the driver architecture and helps determine which value is missing. - If the operation specifically reports a missing architecture value, create the missing entry as a
REG_SZstring. For example, Microsoft’s procedure uses anArchvalue containingamd64when that is the architecture shown byIdentity. - Close Registry Editor, restart Windows, and retry the same update. If the update succeeds, do not alter unrelated DriverOperations entries.
Use amd64 only when the failed operation identifies that architecture. A 32-bit installation or an ARM device requires the architecture indicated by its own identity data. If you cannot identify the failing sequence or missing value, stop rather than guessing; use the update error details, Device Manager events, or Microsoft’s support guidance for the specific driver.
Repair a driver without the registry
- In Device Manager, choose Update driver > Search automatically for drivers.
- If the device is unusable after an update, choose Properties > Driver > Roll Back Driver when available.
- For a clean reinstall, right-click the device, select Uninstall device, choose the option to remove the driver package only when you have a known replacement source, restart, and let Windows redetect it.
- Prefer Windows Update for a supported driver. If it does not provide one, use the exact device manufacturer’s support page or the driver supplied with the computer. Match the model, Windows edition, system architecture, and release.
When adding, finding, or using a printer produces the error
A printer setup failure is usually resolved by checking the connection, restarting the print service, refreshing the driver, and then removing and re-adding the printer. Follow these steps in order so that you do not leave duplicate queues behind.
Rank #2
- Video Link to instructions and Free support VIA Amazon
- Great Support fast responce
- 15 plus years of experiance
- Key is included
1. Check power and the connection
- Make sure the printer is powered on, has no paper, cover, or ink error, and shows a ready state on its own display.
- For USB, reconnect the cable directly to the computer rather than through an unpowered hub. Try another USB port and inspect the cable for damage.
- For Wi-Fi, connect the computer and printer to the same network. A guest network, VPN, or isolated wireless network can prevent discovery.
- For Bluetooth, confirm Bluetooth is enabled, the printer is discoverable, and it is not already paired with another computer.
- Print a configuration or status page from the printer’s own controls when available. This separates a printer-network problem from a Windows queue problem.
2. Restart Print Spooler
- Press
Windows key + R, enterservices.msc, and press Enter. - Find Print Spooler, right-click it, and choose Restart. If it is stopped, choose Start.
- Open its properties and confirm the startup type is not set to Disabled.
- Retry the printer operation. If the service stops again, note the time and inspect Event Viewer before repeatedly reinstalling the printer.
3. Update or reinstall the printer driver
Windows Update is Microsoft’s preferred driver source. Open Settings > Windows Update > Advanced options > Optional updates and install a printer driver if one is offered. Device Manager is another option: expand Print queues or Printers, right-click the printer, and select Update driver.
If neither source has a suitable driver, download the driver for the exact printer model and your Windows edition from the printer manufacturer’s official support site. Avoid a driver intended for a similar model or an older architecture. On Windows running on ARM, Microsoft recommends Settings > Bluetooth & devices > Printers & scanners > Add device instead of a manufacturer’s installer unless the manufacturer provides different ARM-specific instructions.
4. Run the printer troubleshooter
Open the Get Help app from Start, search for printer problems, and run its automated printer troubleshooter. Follow the prompts while the printer is powered on and connected. The troubleshooter can identify an unavailable queue, spooler problem, or discovery issue, but it cannot correct a damaged cable or a printer that is offline at the hardware level.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →5. Select the correct default printer
- Open Settings > Bluetooth & devices > Printers & scanners.
- Select the intended printer and choose Set as default. If Windows manages the default automatically, turn off that behavior when you need one fixed printer.
- Retry the application or setup operation. A successful test page confirms that the selected queue, rather than an old offline queue, is receiving the job.
6. Remove and add the printer again
- In Settings > Bluetooth & devices > Printers & scanners, select the failing printer and choose Remove.
- Restart Windows. This releases handles held by the old queue and reloads Print Spooler.
- Return to Printers & scanners, select Add device, and wait for discovery.
- If automatic discovery fails, choose the option to add the printer manually and enter its network address or select the correct USB port, using the printer’s configuration page for the address.
- Print a test page before restoring application-specific print settings.
7. Clear a stuck print queue
Use this only when jobs remain in the queue or Print Spooler repeatedly reports a pending job.
- Open
services.msc, right-click Print Spooler, and choose Stop. - In File Explorer, go to
C:WindowsSystem32spoolPRINTERS. Approve administrator access if requested. - Delete the files inside that folder, not the folder itself.
- Return to
services.mscand choose Start for Print Spooler. - Remove and re-add the printer if the same job reappears or the queue remains unusable.
When the code appears during another installation or setup
For a .NET component, recovery environment, application, feature, or hardware setup that is not a printer or driver update, treat 0x00000490 as a missing-element symptom. The remedy belongs to the component named by the installer.
Inspect the installer and system evidence
- Read the complete setup log and identify the file, package, feature, service, or registry value that the installer says it cannot find.
- Open Event Viewer by pressing
Windows key + R, enteringeventvwr.msc, and checking Windows Logs > Application and System at the failure time. - Check Device Manager if the setup involves hardware. A warning icon, hardware ID, or failed event usually identifies the required driver.
- Retry from the original, complete installer package. A partial download or an installer launched from a temporary location can omit a required component.
- Use the setup program’s repair or uninstall option only when its documentation identifies that action. Do not delete random program folders or registry keys to make an installer proceed.
If the log names a Windows feature, use Settings > System > Optional features or the relevant Windows component management instructions. If it names a third-party application, obtain the installer and recovery steps from that application’s publisher. A printer queue fix and the DriverOperations registry procedure are not interchangeable with application-installation repairs.
How to choose the safest next step
| Situation | Best first action | Risk and evidence |
|---|---|---|
| Restart, connection, or queue problem | Restart Windows or Print Spooler; check the cable or network | Low risk; verify with a test page or retry |
| Printer driver mismatch | Use Windows Update, then the exact model driver | Moderate; record the current version and model |
| Unknown device in Device Manager | Read Properties, hardware IDs, Driver, and Events | Evidence-led; do not install a similar model’s driver |
| Windows Update driver error 0x80070490 | Inspect the DriverOperations sequence and Identity value | Higher risk; back up the registry and edit only the identified missing value |
| Application or feature setup | Read the setup log and Event Viewer entry | Component-specific; generic printer or registry steps may be wrong |
When a cable or replacement part is actually appropriate
There is no universal physical product for 0x00000490. A model-specific USB cable, power supply, network adapter, or replacement printer part is justified only after the printer’s own status page, another computer, or a known-good cable confirms a physical fault. The hexadecimal code alone cannot identify a cable, cartridge, adapter, or printer model. Buying a generic cable or recovery gadget before confirming the hardware diagnosis is likely to leave the Windows error unresolved.
Quick Recap
Verification checklist
- The original operation now completes without 0x00000490 or 0x80070490.
- Device Manager no longer shows the relevant warning icon, and its Events tab records a successful start.
- A printer appears once under Printers & scanners, is set as the intended default when needed, and prints a test page.
- Windows Update history no longer reports the same driver failure after a restart.
- An application or feature installer completes from a complete, model- or version-matched package.
- You documented any registry change, driver version, or queue removal so it can be reversed if a later update exposes a different problem.
As an optional shortcut after trying the manual steps, Outbyte PC Repair can scan Windows system elements and settings for abnormalities associated with failed installations or invalid entries. It complements antivirus software rather than replacing it, results vary, and no tool repairs every crash. It supports Windows 11, 10, 8 and 7 and offers a free trial by category for at least two days before a subscription.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
