| Previous | Next |
| STATUS_INVALID_IDN_NORMALIZATION | STATUS_ALREADY_REGISTERED |
STATUS_NO_UNICODE_TRANSLATION
The conversion target cannot represent at least one source character
STATUS_NO_UNICODE_TRANSLATION is a representability problem: at least one Unicode character has no mapping in the requested multibyte code page. This differs from malformed input encoding and from an IDN-normalization failure. The source text can be valid Unicode and still be impossible to express losslessly in a legacy code page.
WideCharToMultiByte converts UTF-16 text to a selected code page. Microsoft documents a default-character mechanism for characters that cannot be represented and exposes whether a default character was used. Code-page information also identifies the default translation character. Depending on flags and API contract, lossy substitution may be permitted or the caller may treat it as a conversion failure.
Capture the target code-page identifier, source UTF-16 code units around the first failing character, conversion flags, and whether default-character substitution was allowed. For data interchange, prefer a Unicode encoding such as UTF-8 when the protocol permits it. Do not “fix” the status by deleting non-ASCII characters: that changes identifiers, paths, or user data and can introduce collisions.
What to inspect
- Log the numeric target code page and conversion flags.
- Identify the first unrepresentable Unicode scalar/code-unit sequence.
- Use UTF-8 or another Unicode encoding when the storage/protocol contract supports it.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: WideCharToMultiByte
- Microsoft: Code Pages
- Microsoft: CPINFOEX
- Unicode Standard 17.0
Looking for a different code? Search another status or error code.