| Previous | Next |
| E_IMAPI_ERASE_CLIENT_NAME_IS_NOT_VALID | IMAPI_E_INVALID_PARAM |
IMAPI_E_FSI_INTERNAL_ERROR
IMAPI_E_FSI_INTERNAL_ERROR comes from the IMAPI2FS image-building layer, not from the optical recorder write path. The IFileSystemImage object maintains an in-memory hierarchy of directories, files, file data streams, file-system selections, session parameters, and staging state before CreateResultImage produces the final image stream. This HRESULT therefore points at an internal failure while IMAPI is manipulating that image model.
Preserve the image-building sequence that led to the failure
- Record the last
IFileSystemImage,IFsiDirectoryItem, orIFsiFileItemcall and the exact item path. - Capture whether a previous session was imported, whether staging is enabled, and which file systems are selected for creation.
- Rebuild the image from a fresh
MsftFileSystemImageobject to distinguish persistent input data from corrupted object state.
Do not diagnose this as a media write-speed or recorder problem unless a later recorder API also fails. At the IMAPI2FS stage, the useful reproduction is the smallest ordered set of image mutations that triggers the HRESULT. If a particular file or alternate stream is involved, isolate that item and retain the original IStream behavior, because changing the source stream can hide the image-layer failure.
IFileSystemImage · IMAPI2FS header · IMAPI return values
Looking for a different code? Search another status or error code.