What does HRESULT 0xC0AAB104 (IMAPI_E_INVALID_VOLUME_NAME) mean?

 
Previous Next
IMAPI_E_NO_OUTPUT IMAPI_E_INVALID_DATE

IMAPI_E_INVALID_VOLUME_NAME

IMAPI_E_INVALID_VOLUME_NAME is returned when the value assigned through IFileSystemImage::put_VolumeName is not valid for IMAPI2FS. Microsoft documents a 15-character limit and different allowed character sets for ISO 9660 versus Joliet and UDF. The failure is about the image volume identifier, not a directory or file name inside the image.

Validate the identifier against the file systems being generated

  • Log the exact volume name and its length before assigning it.
  • Record FileSystemsToCreate; ISO 9660 has a more restricted documented character set than Joliet or UDF.
  • If multiple file systems are emitted, choose a name acceptable to the combined output requirements rather than validating against only one format.

Do not sanitize the value silently after the HRESULT and then report success without preserving the original input. The rejected identifier is the useful evidence. A default volume name is generated if none is supplied, so applications that do not require a specific label can avoid custom validation entirely. For user-specified labels, validate length and characters before COM assignment and show the exact constraint that failed.

VolumeName · File systems to create · FsiFileSystems


Looking for a different code? Search another status or error code.