| Previous | Next |
| STATUS_CONNECTION_IN_USE | STATUS_PROCESS_IS_TERMINATING |
STATUS_MESSAGE_NOT_FOUND
A message ID lookup failed inside a message table; this is not the same as a missing DLL
STATUS_MESSAGE_NOT_FOUND specifically names RtlFindMessage and a message-table resource. Windows message tables are special binary string resources generated by the Message Compiler and embedded through a MESSAGETABLE resource. Message text files assign message IDs and can define language variants.
The first diagnostic inputs are therefore the image or resource module, the message-table resource, requested message ID, and language selection. A module can load successfully and still lack that ID. The Win32 error ERROR_MR_MID_NOT_FOUND describes the corresponding condition where the system cannot find text for a message number in the message file.
Do not solve the problem by hard-coding the currently displayed English text. That bypasses localization and can hide a version mismatch between the executable that emitted an ID and the message resource deployed beside it. Compare the generated header/message definitions and the actual resource version shipped with the failing binary.
What to inspect
- The exact module/resource file, message ID, language ID, and resource version used by the failing lookup.
- Whether the message definition exists in the source
.mcfile and generated header for the deployed build. - Packaging or servicing changes that could mix an emitter from one version with a message-table resource from another.
References
- Microsoft: MESSAGETABLE resource
- Microsoft: Message Text Files and message IDs
- Microsoft: System error codes including ERROR_MR_MID_NOT_FOUND
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.