HRESULT 0xC0AAB161 (IMAPI_E_UDF_REVISION_CHANGE_NOT

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: the UDF revision cannot be changed after importing the previous session.

Previous	Next
IMAPI_E_PROPERTY_NOT_ACCESSIBLE	IMAPI_E_BAD_MULTISESSION_PARAMETER

IMAPI_E_UDF_REVISION_CHANGE_NOT_ALLOWED

IMAPI_E_UDF_REVISION_CHANGE_NOT_ALLOWED protects multisession filesystem compatibility. After a UDF session has been imported, IFileSystemImage exposes the imported UDF revision and does not allow the caller to switch the new session to a different revision.

Preserve the revision established by the imported session

Read UDFRevision after import and log it before configuring the result image.
Do not apply generic “preferred UDF revision” defaults after an import has already succeeded.
If a different revision is required, create a fresh filesystem image rather than extending the existing UDF session.

The distinction from IMAPI_E_UDF_NOT_WRITE_COMPATIBLE matters. One code says the imported revision cannot be written compatibly by IMAPI; this code says the caller attempted to change a revision that must remain consistent with the imported session. Multisession append preserves filesystem continuity, so revision choice is constrained by prior on-disc state.

Get UDF revision · Set UDF revision · ECMA-167

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