| Previous | Next |
| RO_E_CHANGE_NOTIFICATION_IN_PROGRESS | E_STRING_NOT_NULL_TERMINATED |
RO_E_ERROR_STRING_NOT_FOUND
No localized message text exists for the HRESULT
RO_E_ERROR_STRING_NOT_FOUND is HRESULT 2147483670 (0x80000016) from winerror.h. The documented description is “The text associated with this error code could not be found.” 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.
- 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 an error-display path that requested a system or runtime message for a code with no registered resource string.
What to verify
Verify that the numeric HRESULT and symbolic constant remain available even when localized text lookup fails. Validate this condition using the owning API state, not an inferred UI symptom.
Correct handling and recovery
Display a safe application fallback containing the symbolic code and correlation ID, while retaining the original HRESULT for support and telemetry.
Practical scenario
A diagnostic viewer cannot resolve a vendor HRESULT to localized text. It shows the hex value, module, operation, and support ID instead of replacing it with an empty message.
Difference from nearby HRESULTs
It concerns message formatting, not the success or failure of the original operation whose code was being described.
References
Looking for a different code? Search another status or error code.