What does NTSTATUS 0xC000022C (STATUS_CONVERT_TO_LARGE) mean?

 
Previous Next
STATUS_OBJECTID_EXISTS STATUS_RETRY

STATUS_CONVERT_TO_LARGE

This is an internal allocation-control status, not proof of a licensing failure

STATUS_CONVERT_TO_LARGE is one of the unusual cases where Microsoft's NTSTATUS text exposes internal OFS allocation handling. The documented message says the operation is either retried after the containing onode is moved or the extent stream is converted to a large stream. That makes the status a control result used to change allocation strategy, not a general “file is too large” error.

The same wording is published for the corresponding Win32 system message ERROR_CONVERT_TO_LARGE. Microsoft does not publicly document the onode layout, stream-size threshold, or the exact OFS implementation path that chooses between relocation and conversion. A custom page should therefore preserve those limits rather than substitute NTFS resident/nonresident terminology or infer an alternate-data-stream threshold. “OFS” in the official text is the only subsystem attribution that is safe here.

If the value appears in a low-level trace, record the allocator call site, current stream representation, requested growth, and whether the caller retries after handling the status. A component that leaks this internal control status to an unrelated user-facing layer may have missed its expected retry/conversion path. Repeatedly retrying without changing allocation state is also suspicious, because the documented message explicitly ties retry to moving the containing onode or converting the extent stream.

What to inspect

  • Capture the allocator call site and current stream/allocation representation.
  • Verify whether the caller performs the documented relocation or conversion before retry.
  • Do not translate the code into NTFS resident-data or license semantics without producer evidence.

References

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