| Previous | Next |
| RO_E_METADATA_NAME_IS_NAMESPACE | RO_E_INVALID_METADATA_FILE |
RO_E_METADATA_INVALID_TYPE_FORMAT
WinRT metadata type name has invalid syntax
RO_E_METADATA_INVALID_TYPE_FORMAT is HRESULT 2147483665 (0x80000011) from winerror.h. The documented description is “Typename has an invalid format.” The relevant context is the Windows Runtime metadata, object lifetime, asynchronous operation, activation, and apartment model.
The hexadecimal value and symbolic name of this result should remain attached to the originating API and operation instance.
Where it is encountered
- C++/WinRT, WRL, .NET projections, or native WinRT ABI calls.
- Runtime-class activation, WinMD reflection, asynchronous objects, observable state, or view lifecycle.
- Cross-thread and cross-apartment handoff between UI, ASTA, STA, MTA, broker, and background work.
The immediate focus is a malformed metadata type expression, including invalid namespace separators, generic arity, nested-type notation, or forbidden characters.
What to verify
Verify that the input is validated against WinRT type-name grammar before metadata files or deployment are blamed. That condition determines whether the same object can continue, a new object is required, or policy must change.
Correct handling and recovery
Normalize the generated name at its source, reject untrusted malformed names, and add tests for generic and nested forms used by the projection.
Reconcile partial output and server-side effects before attempting the operation again.
Difference from nearby HRESULTs
It is syntactic; RO_E_METADATA_NAME_NOT_FOUND is a well-formed lookup that found no symbol.
Practical scenario
A code generator emits a generic type name with CLR backtick syntax where WinRT metadata expects a projected form. The generator is corrected and its output snapshot-tested.
References
Looking for a different code? Search another status or error code.