What does HRESULT 0x8000000F (RO_E_METADATA_NAME_NOT_FOUND) mean?

 
Could be also:
ConstantTypeOS
STATUS_DEVICE_POWERED_OFFNTSTATUSWindows
Previous Next
E_ILLEGAL_METHOD_CALL RO_E_METADATA_NAME_IS_NAMESPACE

RO_E_METADATA_NAME_NOT_FOUND

Windows Runtime type or namespace was not found in metadata

RO_E_METADATA_NAME_NOT_FOUND is HRESULT 2147483663 (0x8000000F) from winerror.h. The documented description is “Typename or Namespace was not found in metadata file.” The relevant context is the Windows Runtime metadata, object lifetime, asynchronous operation, activation, and apartment model.

Where it is encountered

  • C++/WinRT, WRL, .NET projections, or native WinRT ABI calls.

The immediate focus is WinRT metadata lookup for a fully qualified name that is absent from the loaded WinMD set or package dependency graph.

What to verify

Verify that the spelling, namespace qualification, architecture, package version, and metadata search path match the component being activated or reflected.

Difference from nearby HRESULTs

It means no matching metadata symbol exists; RO_E_METADATA_NAME_IS_NAMESPACE means the supplied name exists but denotes a namespace.

Correct handling and recovery

Correct the type name or deploy the missing metadata dependency. Rebuild generated projections after metadata changes and avoid fallback to a similarly named type.

Practical scenario

A plug-in host requests Contoso.Imaging.Decoder, but the installed package exposes versioned namespace Contoso.Imaging.V2. Deployment and generated bindings are aligned to the same WinMD.

References


Looking for a different code? Search another status or error code.