What does HRESULT 0xC0AAB149 (IMAPI_E_BOOT_OBJECT_CONFLICT) mean?

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: a boot object was configured for a noninitial multisession image.

Previous	Next
IMAPI_E_BOOT_IMAGE_DATA	IMAPI_E_BOOT_EMULATION_IMAGE_SIZE_MISMATCH

IMAPI_E_BOOT_OBJECT_CONFLICT

IMAPI_E_BOOT_OBJECT_CONFLICT means boot-image options conflict with previous-session import. Microsoft documents that a boot object can only be included in an initial disc image, and both ImportFileSystem and ImportSpecificFileSystem list this HRESULT. A continuation session cannot simply add a new boot object through the same FileSystemImage workflow.

Check multisession import and boot configuration order

Record whether MultisessionInterfaces was set and a previous file system was imported.
Record when BootImageOptions or the boot options array was assigned relative to import.
If bootable media is required, design it into the initial image rather than attaching boot options to an appended session.

Replacing the boot stream with another file does not resolve the conflict because the problem is the session role, not the boot-image bytes. Separate initial-disc creation from multisession append logic in the application. When diagnosing an existing builder, log import and boot-option calls in order; that call sequence should make the conflict explicit before CreateResultImage is reached.

ImportFileSystem · ImportSpecificFileSystem · BootImageOptions

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