| Previous | Next |
| ERROR_ICM_NOT_ENABLED | ERROR_INVALID_TRANSFORM |
ERROR_DELETING_ICM_XFORM
The color transform could not be deleted.
ERROR_DELETING_ICM_XFORM is Win32 error 2019 (0x7E3). A transform handle is created from a defined profile chain and later released through DeleteColorTransform. The status says cleanup failed for that handle; it does not prove that the profile files should be removed or that creating another transform will repair ownership.
Typical transform-lifetime defects
- the handle was already deleted and a second cleanup path uses the stale value
- creation returned failure or a different object, but uninitialized state reached the delete routine
- several threads or wrapper objects believe they own the same
HTRANSFORM - a cached transform survives beyond the component or session that established its profiles and mode
- memory corruption changes the handle or surrounding ownership flags before shutdown
Cleanup evidence
Record the transform correlation ID, creating API, source/destination/proof profile hashes, creation and deletion threads, owner object, successful-use count, first delete attempt, process shutdown state, and the immediate GetLastError value. Log a locally assigned identifier rather than treating an opaque handle value as a durable cross-process identity.
How to investigate
Trace one transform from successful creation to its single intended deletion. Confirm that every failed creation leaves the stored handle null and that move, copy, exception, cancellation, and shutdown paths cannot each release the same resource. Reproduce with page heap or memory diagnostics when ownership appears correct.
Check whether deletion is happening concurrently with TranslateBitmapBits, TranslateColors, gamut checks, or another consumer. Microsoft documents deletion and failure reporting but does not define application-safe sharing semantics; serialize final release after all users have completed.
Recovery and prevention
Stop using the failed handle, unwind the owner, and create a fresh transform only after the profile tuple is still valid. Do not retry deletion in an unbounded loop or delete profile files to force cleanup.
Use one explicit owner, invalidate the handle immediately after a successful release, and hold references for asynchronous color work. Unit tests should cover failed creation, double cleanup, cancellation, device changes, and process teardown.
Difference from ERROR_INVALID_TRANSFORM
ERROR_INVALID_TRANSFORM normally appears when an operation is asked to use a transform that is not valid. Error 2019 is specifically the failure to destroy a transform during its cleanup lifecycle.
Example
A rendering cache gives two wrapper instances ownership of one transform. The first destructor deletes it; the second receives 2019. Making the wrapper move-only and clearing the handle after release eliminates the double-destruction path.
References
- Microsoft: System Error Codes (1700–3999)
- Microsoft: Win32 Error Codes in MS-ERREF
- Microsoft: Error codes specific to WCS
- Microsoft: DeleteColorTransform
- Microsoft: CreateMultiProfileTransform
Looking for a different code? Search another status or error code.