Error codes in imapi2fserror.h

• 0xC0AAB100: Internal file system error occurred.^[1]
• 0xC0AAB101: The value specified for parameter '%1!ls!' is not valid.^[1]
• 0xC0AAB102: FileSystemImage object is in read only mode.^[1]
• 0xC0AAB103: No output file system specified.^[1]
• 0xC0AAB104: The specified Volume Identifier is either too long or contains one or more invalid characters.^[1]
• 0xC0AAB105: Invalid file dates. %1!ls! time is earlier than %2!ls! time.^[1]
• 0xC0AAB106: The file system must be empty for this function.^[1]
• 0xC0AAB108: Specified path '%1!ls!' does not identify a file.^[1]
• 0xC0AAB109: Specified path '%1!ls!' does not identify a directory.^[1]
• 0xC0AAB10A: The directory '%1!s!' is not empty.^[1]
• 0xC0AAB10B: '%1!ls!' is not part of the file system. It must be added to complete this operation.^[1]
• 0xC0AAB110: Path '%1!s!' is badly formed or contains invalid characters.^[1]
• 0xC0AAB111: The name '%1!ls!' specified is not legal: Name of file or directory object created while the UseRestrictedCharacterSet property is set may only contain ANSI characters.^[1]
• 0xC0AAB112: '%1!ls!' name already exists.^[1]
• 0xC0AAB113: Attempt to add '%1!ls!' failed: cannot create a file-system-specific unique name for the %2!ls! file system.^[1]
• 0xC0AAB118: Cannot find item '%1!ls!' in FileSystemImage hierarchy.^[1]
• 0xC0AAB119: The file '%1!s!' not found in FileSystemImage hierarchy.^[1]
• 0xC0AAB11A: The directory '%1!s!' not found in FileSystemImage hierarchy.^[1]
• 0xC0AAB120: Adding '%1!ls!' would result in a result image having a size larger than the current configured limit.^[1]
• 0xC0AAB121: Value specified for FreeMediaBlocks property is too small for estimated image size based on current data.^[1]
• 0xC0AAB128: Data stream supplied for file '%1!ls!' is inconsistent: expected %2!I64d! bytes, found %3!I64d!.^[1]
• 0xC0AAB129: Cannot read data from stream supplied for file '%1!ls!'.^[1]
• 0xC0AAB12A: The following error was encountered when trying to create data stream for '%1!ls!':^[1]
• 0xC0AAB12B: The following error was encountered when trying to enumerate files in directory '%1!ls!':^[1]
• 0xC0AAB130: This file system image has too many directories for the %1!ls! file system.^[1]
• 0xC0AAB131: ISO9660 is limited to 8 levels of directories.^[1]
• 0xC0AAB132: Data file is too large for '%1!ls!' file system.^[1]
• 0xC0AAB133: Operation failed because of incompatible layout of the previous session imported from the medium.^[1]
• 0xC0AAB138: Cannot initialize %1!ls! stash file.^[1]
• 0xC0AAB139: Error seeking in '%1!ls!' stash file.^[1]
• 0xC0AAB13A: Error encountered writing to '%1!ls!' stash file.^[1]
• 0xC0AAB13B: Error encountered reading from '%1!ls!' stash file.^[1]
• 0xC0AAB140: The working directory '%1!ls!' is not valid.^[1]
• 0xC0AAB141: Cannot set working directory to '%1!ls!'. Space available is %2!I64d! bytes, approximately %3!I64d! bytes required.^[1]
• 0xC0AAB142: Attempt to move the data stash file to directory '%1!ls!' was not successful.^[1]
• 0xC0AAB148: The boot object could not be added to the image.^[1]
• 0xC0AAB149: A boot object can only be included in an initial disc image.^[1]
• 0xC0AAB14A: The emulation type requested does not match the boot image size.^[1]
• 0xC0AAB150: Optical media is empty.^[1]
• 0xC0AAB151: The specified disc does not contain one of the supported file systems.^[1]
• 0xC0AAB152: The specified disc does not contain a '%1!ls!' file system.^[1]
• 0xC0AAB153: Consistency error encountered while importing the '%1!ls!' file system.^[1]
• 0xC0AAB154: The '%1!ls!'file system on the selected disc contains a feature not supported for import.^[1]
• 0xC0AAB155: Could not import %2!ls! file system from disc. The file '%1!ls!' already exists within the image hierarchy as a directory.^[1]
• 0xC0AAB156: Cannot seek to block %1!I64d! on source disc.^[1]
• 0xC0AAB157: Import from previous session failed due to an error reading a block on the media (most likely block %1!u!).^[1]
• 0xC0AAB158: Current disc is not the same one from which file system was imported.^[1]
• 0xC0AAB159: IMAPI does not allow multi-session with the current media type.^[1]
• 0xC0AAB15A: IMAPI can not do multi-session with the current media because it does not support a compatible UDF revision for write.^[1]
• 0xC0AAB15B: IMAPI does not support the multisession type requested.^[1]
• 0xC0AAB15C: IMAPI supports none of the multisession type(s) provided on the current media.^[1]
• 0xC0AAB15D: MultisessionInterfaces property must be set prior calling this method.^[1]
• 0xC0AAB15E: Could not import %2!ls! file system from disc. The directory '%1!ls!' already exists within the image hierarchy as a file.^[1]
• 0x00AAB15F: Feature is not supported for the current file system revision, image will be created without this feature.^[1]
• 0xC0AAB160: Property '%1!ls!' is not accessible^[1]
• 0xC0AAB161: UDF revision cannot be changed because of the previously imported session^[1]
• 0xC0AAB162: One of the multisession parameters cannot be retrieved or has a wrong value.^[1]
• 0xC0AAB163: You cannot change the file system to be created, because the file system in the imported session and the one in the new session must match.^[1]
• 0xC0AAB200: The image is not 2kb aligned. Only 2048 bytes aligned images are supported.^[1]
• 0xC0AAB201: No valid file system Volume Descriptor was found in the iso image. This image format is not supported and the resulting disc might not be readable.^[1]
• 0xC0AAB202: No image was set (neither path nor stream was given).^[1]
• 0xC0AAB203: Image size exceeds MAXLONG sectors - too big.^[1]

Sources

1. imapi2fserror.h from Windows SDK 10.0.14393.0