| Previous | Next |
| VFW_E_NO_AUDIO_HARDWARE | VFW_E_PROCESSOR_NOT_SUITABLE |
VFW_E_RPZA
Exact result and bit fields
VFW_E_RPZA has the unsigned HRESULT value 2147746393 (0x80040259) and the signed 32-bit representation -2147220903. AllStat describes it as “Cannot play back the video stream: format 'RPZA' is not supported”. In the operation that produces this result, DirectShow encounters Apple Video RPZA content for which the installed graph has no supported decoding path.
The high bit is set, so this value is a failure HRESULT. Its facility field is 4 (FACILITY_ITF) and its low code is 601 (0x0259). These fields classify this result, but they do not identify which filter, thread, device, file or graph generation returned it.
Evidence worth preserving
Log the interface and method, filter CLSID and friendly name, process and thread, graph state, connected pin names, media-type summary, renderer or device identity where relevant, and the first preceding HRESULT. Record lengths and hashes instead of raw content when the incident includes media paths, codec configuration, property values and stream metadata.
- Evidence 1 for this HRESULT: stream subtype or four-character code.
- Evidence 2 for this HRESULT: container track table and codec tag.
- Evidence 3 for this HRESULT: candidate decoder list and platform architecture.
Contract boundary
This result describes a capability or format boundary in a component graph. Container recognition, elementary-stream parsing, decoder selection, property metadata and renderer acceptance are different stages and need separate evidence.
The practical owner to locate for this HRESULT is the source filter, decoder or codec property provider and downstream connection. When handling this result, capture the native result before a wrapper replaces it with a generic exception, and keep the graph generation or object identity with the record.
Conditions that can produce it
- Cause 1 for this HRESULT: the file uses the legacy RPZA codec.
- Cause 2 for this HRESULT: a decoder present on another machine is absent from this deployment.
- Cause 3 for this HRESULT: container detection succeeds but codec policy excludes the required component.
Step-by-step diagnosis
- Capture it at the first native return, not only at the top-level playback failure.
- identify the exact graph stage described here: DirectShow encounters Apple Video RPZA content for which the installed graph has no supported decoding path.
- compare the live object state, topology and input with the documented interface preconditions.
- Before changing filters, drivers, registry data or media for this HRESULT, collect the code-specific evidence below.
- Test one evidence-backed the correction on the smallest reproducible graph.
- Verify that the corrected run no longer returns it and does not merely replace it with a nearby HRESULT.
Correction strategy
- Action 1 for this HRESULT: transcode the asset to a supported format.
- Action 2 for this HRESULT: install a trusted RPZA-capable decoder when legacy playback is required.
- Action 3 for this HRESULT: detect the codec before graph construction and produce a specific compatibility message.
Example incident
A QuickTime-era training clip opens but its video pin advertises RPZA; preflight detection routes it to a conversion workflow instead of repeatedly calling RenderFile. This example keeps the diagnosis at the specific the boundary instead of treating every DirectShow failure as a codec reinstall problem.
Implementation notes
Code that handles it should preserve the original HRESULT, the failed stage and an opaque correlation identifier. After it, do not infer success from partial graph construction, and do not continue using interfaces retained from a graph or device generation that has already changed.
Operational remediation for this HRESULT should favor supported component installation, device configuration and documented DirectShow calls. Manual registry or driver changes are appropriate only when the collected evidence for this HRESULT points to that layer and a rollback is available.
Retry and recovery
Retry rule for this HRESULT: Retry only with a compatible decoder or converted asset; changing audio or renderer settings cannot decode RPZA video. A safe it retry must use a changed capability, state, object generation or input. While recovering from it, preserve cancellation and avoid replaying side effects when the original operation may have partially completed.
How it differs from nearby results
VFW_E_NO_DECOMPRESSOR is generic decoder absence, while it explicitly identifies the unsupported RPZA format. Keep those cases separate in telemetry, UI messages and retry policy because their next actions are different.
Official Microsoft references
- Microsoft: DirectShow error and success codes
- Microsoft: IGraphBuilder::RenderFile
- Microsoft: using the Filter Mapper
Looking for a different code? Search another status or error code.