What does HRESULT 0xC00D36F6 (MF_E_NO_BITPUMP) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Internal. Bitpump not found.%0

Previous	Next
MF_E_RT_WOULDBLOCK	MF_E_RT_OUTOFMEMORY

MF_E_NO_BITPUMP

Interpret the result in the pipeline

MF_E_NO_BITPUMP (0xC00D36F6) is a failure result from Windows Media Foundation. The generated section above already contains the platform message; the useful extra information is that this result isolates an internal data-pumping component required by the selected Media Foundation path could not be located or created.

The producer is the internal pipeline assembly step rather than the application media data itself, so diagnosis should begin with that object and its state rather than with a broad reinstall or an unrelated codec change. A representative occurrence is a damaged platform component or incompatible custom media component prevents creation of the internal pump during graph setup.

Decisive observations

Observation	What to capture for `MF_E_NO_BITPUMP`
Primary discriminator	the topology, source and sink types, installed component versions, first preceding activation error, and whether the failure reproduces in a stock pipeline
Owning object	the internal pipeline assembly step rather than the application media data itself, including its object identity and generation
Timeline marker	the call immediately before an internal data-pumping component required by the selected Media Foundation path could not be located or created and the completion event, callback, or state change that followed
Comparison artifact	one known-good run that changes only this condition: rebuild a minimal topology with system components and compare it with the failing custom-component graph

The decisive boundary is an internal data-pumping component required by the selected Media Foundation path could not be located or created. Preserve the original the internal pipeline assembly step rather than the application media data itself and the first result in the chain: a later UI message can replace this precise code with a generic playback, setup, network, or device failure.

Minimal experiment

Record MF_E_NO_BITPUMP, 0xC00D36F6, the returning method, process architecture, Windows build, and component version.
Capture the topology, source and sink types, installed component versions, first preceding activation error, and whether the failure reproduces in a stock pipeline before retry logic changes the object.
Perform this narrow comparison: rebuild a minimal topology with system components and compare it with the failing custom-component graph.
For MF_E_NO_BITPUMP, keep the input, account, URL, device, media type, and requested action unchanged unless one is the single tested variable.
After correcting MF_E_NO_BITPUMP, create a fresh object or process where lifecycle state may have been retained, then repeat the original call.

What the result does not prove

MF_E_NO_BITPUMP does not by itself prove a machine-wide media-platform failure. In this case, a missing decoder normally yields a topology or codec error, not this internal bit-pump result. The MF_E_NO_BITPUMP evidence does not justify deleting license stores, clearing every proxy setting, installing codec packs, or rewriting media files before its producer is identified.

Similar messages, different checkpoints

Result	Different checkpoint
`MF_E_RT_OUTOFMEMORY`	No more RT memory available; compare this boundary specifically with `MF_E_NO_BITPUMP`.
`MF_E_MEDIAPROC_WRONGSTATE`	MediaProc is in the wrong state; compare this boundary specifically with `MF_E_NO_BITPUMP`.
`MF_E_DISABLED_IN_SAFEMODE`	The Media Foundation platform is disabled when the system is running in Safe Mode; compare this boundary specifically with `MF_E_NO_BITPUMP`.

Targeted recovery

The supported corrective direction is to repair or update the component installation and remove the custom element that prevents pipeline assembly; applications should not instantiate undocumented internals. Success means more than disappearance of a dialog: the same method must pass the same checkpoint, the expected event or output must appear, and no broader fallback HRESULT should replace MF_E_NO_BITPUMP.

For a MF_E_NO_BITPUMP incident, keep the symbolic constant together with 0xC00D36F6. For MF_E_NO_BITPUMP, that pairing preserves the checkpoint when signed integer fields or wrapper logs obscure the original Media Foundation or Windows Media facility.

Technical references

Media Foundation architecture — reference used for the MF_E_NO_BITPUMP checkpoint.
Media Foundation error codes — reference used for the MF_E_NO_BITPUMP checkpoint.
Media sources — reference used for the MF_E_NO_BITPUMP checkpoint.
Media Foundation events — reference used for the MF_E_NO_BITPUMP checkpoint.

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