What does HRESULT 0xC0AAB121 (IMAPI_E_IMAGE_TOO_BIG) mean?

 
Previous Next
IMAPI_E_IMAGE_SIZE_LIMIT IMAPI_E_DATA_STREAM_INCONSISTENCY

IMAPI_E_IMAGE_TOO_BIG

IMAPI_E_IMAGE_TOO_BIG is tied directly to IFileSystemImage::put_FreeMediaBlocks. Microsoft documents that the property sets the maximum number of blocks available for image creation and that assigning a value smaller than the estimated size of current data fails. A value of zero represents an unlimited block count.

Compare the proposed limit with the current image estimate

  • Record the old and new FreeMediaBlocks values together with UsedBlocks.
  • Check whether content was added before the application recalculated target-media capacity.
  • For a real burn, use media/device-derived image defaults or SetMaxMediaBlocksFromDevice instead of a stale constant.

This is a configuration-time failure, not evidence that reading a file stream failed. The image is already estimated to require more blocks than the new ceiling allows. Either reduce the hierarchy first or set a limit consistent with the target capacity. Be careful when changing media after image construction: a smaller replacement medium can make a previously acceptable image impossible to fit.

FreeMediaBlocks · IFileSystemImage · CreateResultImage


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