ERROR_ILLEGAL_CHARACTER - 582 (0x246)

An illegal character was encountered. For a multi-byte character set this includes a lead byte without a succeeding trail byte. For the Unicode character set this includes the characters 0xFFFF and 0xFFFE.

Updated: Feb 21, 2026

Technical Meaning

The ERROR_ILLEGAL_CHARACTER error indicates that an illegal character was encountered during a specific operation. This can occur in various contexts, such as file names, directory paths, or other string-based operations.

Error Details

This error is typically associated with the following scenarios:

  • Multi-byte Character Sets: An illegal lead byte without a corresponding trail byte has been detected.
  • Unicode Character Set: The characters 0xFFFF and 0xFFFE are not valid and have caused this error.

Usage Context

This error can be encountered in various operations, such as:

  • File or directory name validation
  • Path parsing
  • String manipulation functions

Developer Interpretation

When encountering the ERROR_ILLEGAL_CHARACTER, developers should ensure that all input strings are properly formatted and validated. This includes checking for valid characters within multi-byte character sets and ensuring compliance with Unicode standards.

Related Errors

  • ERROR_PATH_NOT_FOUND: The specified path does not exist or is invalid.
  • ERROR_INVALID_NAME: The file name, directory name, or volume label syntax is incorrect.
  • ERROR_BAD_NETPATH: The network path was not found.

FAQ

Q: What causes the ERROR_ILLEGAL_CHARACTER?

A: This error occurs when an illegal character is encountered in a string-based operation. Common causes include invalid characters within multi-byte or Unicode sets.

Q: How can I prevent this error?

A: Ensure that all input strings are validated and conform to the expected character set standards before performing operations.

Summary

The ERROR_ILLEGAL_CHARACTER is a specific error indicating an illegal character encountered during string-based operations. Developers should validate inputs and ensure compliance with character set standards to avoid this error.