What does HRESULT 0x8004170C (FILTER_E_UNKNOWNFORMAT) mean?

FILTER_E_UNKNOWNFORMAT

The selected filter does not recognize the document format

FILTER_E_UNKNOWNFORMAT is HRESULT 0x8004170C. Windows documents it as “The document format is not recognized by the flter.”

Interpretation in context

This result belongs to probing or loading source bytes before IFilter chunk enumeration begins. The handler cannot match the actual file structure to a format it knows how to parse.

Conditions to test

• The extension is incorrect.
• The file is truncated or contains another format.
• The registered handler does not support this format version.
• Content sniffing reaches an unsupported container.

Compare the failing case with a control that preserves leading signature bytes and file length and changes only extension, MIME type and detected format; this prevents unrelated environment differences from dominating the test.

Incident record

• Check leading signature bytes and file length.
• Check extension, MIME type and detected format.
• Check chosen handler CLSID and version.
• Check known-good sample from the same producer.

Capture leading signature bytes and file length before releasing objects, closing handles or reconnecting. Retain the raw HRESULT with extension, MIME type and detected format, component version, UTC timestamp and correlation ID.

Step-by-step diagnosis

1. Compare magic bytes with the claimed extension.
2. Open the file in the owning application and validate its format.
3. Test the same bytes with the registered handler directly.
4. Avoid changing associations until misclassification or handler coverage is proven.

Preserve the component version and target identity, then alter only the condition described as the handler cannot match the actual file structure to a format it knows how to parse.

Retry decision

Correct the file classification, repair the document or install an appropriate trusted handler; identical retries cannot change format recognition. Record whether probing or loading source bytes before IFilter chunk enumeration begins produced any content, update or state transition before returning.

Retry only after a concrete change in leading signature bytes and file length or extension, MIME type and detected format.

What the value cannot establish

It does not by itself prove registry corruption or a globally missing filter association. Without the call boundary for probing or loading source bytes before IFilter chunk enumeration begins, it also cannot identify which wrapper or configuration layer introduced the condition.

Adjacent contract states

FILTER_E_EMBEDDING_UNAVAILABLE can occur after a parent was recognized; this HRESULT rejects the current object format itself.

Developer and administrator actions

• Record leading signature bytes and file length with the returned HRESULT
• In telemetry, correlate extension, MIME type and detected format with the target and component generation
• For regression coverage, force the documented condition: the handler cannot match the actual file structure to a format it knows how to parse

Concrete scenario

A PDF extension is applied to an HTML error page downloaded by a proxy. Signature logging reveals why the PDF handler rejects it.

Official Microsoft references

• Microsoft: Content-Indexing values — official contract information relevant to this HRESULT.
• Microsoft: filter handlers in Windows Search
• Microsoft: IFilter interface
• Microsoft: testing filter handlers
• Microsoft: Filter-Interface values