The short version
- 01Confirm that 0x80070490 occurred during Windows Update driver installation.
- 02Record the failed package, driver and Windows version.
- 03Ask an administrator to match the failure to Microsoft's driver-metadata case.
- 04Have the administrator inspect the affected DriverOperations entry and its Identity value.
- 05Use the actual missing value for that driver in a prepared, backed-up registry repair.
- 06Retry the same package after the targeted correction and retain the result.
Raw message
0x80070490 — ERROR_NOT_FOUND
Likely causes
- In Microsoft's documented Update case, required driver metadata is missing in the registry.
Match the driver-installation case first
Microsoft's common Update table maps this case to ERROR_NOT_FOUND during driver installation. It identifies missing driver details, such as architecture, in the registry. Our recommendation is to retain the driver and package before applying this explanation to another application's 0x80070490.
Let Identity identify the missing metadata
The documented procedure inspects the affected ComponentBasedServicing DriverOperations entry and its Identity value. Our recommendation is to have an administrator match the actual sequence and missing detail; Microsoft's sample amd64 value is an example, not an instruction for every system.
Use a prepared repair for the affected entry
Microsoft's remedy adds the missing value from the driver identity and retries the update. Our recommendation is to back up before a registry edit and give the exact case to an administrator. This reference does not establish universal component-store corruption from the code alone.
Sources and review notes
Checked on . Official Microsoft table read October 6, 2026. Matching context, registry preparation and administrator handoff are editorial guidance. Scoped to the documented Update driver case. Glitchary is independent of Microsoft.