What does HRESULT 0xC00D36F0 (MF_E_CANNOT_PARSE_BYTESTREAM) mean?

 
Previous Next
MF_E_DISABLED_IN_SAFEMODE MF_E_SOURCERESOLVER_MUTUALLY_EXCLUSIVE_FLAGS

MF_E_CANNOT_PARSE_BYTESTREAM

MF_E_CANNOT_PARSE_BYTESTREAM means source creation reached the parsing stage and the supplied bytes could not be interpreted as the expected media data. This is different from MF_E_UNSUPPORTED_BYTESTREAM_TYPE, where resolver discovery cannot find a suitable handler.

Preserve the bytes that actually failed

  • Capture the initial stream bytes, total bytes made available, URL extension, and MF_BYTESTREAM_CONTENT_TYPE.
  • Check for truncated downloads, an HTML error body returned for a media URL, encryption, or a wrapper format that the selected handler does not parse.
  • For a custom stream, confirm that reads return the requested byte ranges and do not report end-of-stream prematurely.

The source resolver chooses byte-stream handlers using the URL extension and MIME type. Those hints can select a parser, but they do not transform the content. Renaming a file or inventing a MIME type can therefore move the failure from handler selection to this parse error.

Microsoft: CreateObjectFromByteStream · Microsoft: scheme and byte-stream handlers · Microsoft: Source Resolver


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