| Previous | Next |
| NS_E_INVALID_OUTPUT_FORMAT | NS_E_PROTECTED_CONTENT |
NS_E_NOT_CONFIGURED
NS_E_NOT_CONFIGURED in a format, graph or streaming trace
The relevant condition for 0xC00D0BBC is sample processing began before all mandatory codec or writer properties were committed. Diagnose the not configured media-format check directly and avoid inferring the cause only from the visible playback symptom.
Nearby results are not interchangeable
Main distinction: the object exists and the media may be valid, but the component is not ready for processing. This differs from an unsupported format, malformed profile or end-of-stream result.
| Nearby HRESULT | How to compare it |
|---|---|
NS_E_UNEXPECTED_MSAUDIO_ERROR | Compare the owning API and first rejected value; it belongs to a neighboring checkpoint, not automatically to the same cause as this result. |
NS_E_INVALID_OUTPUT_FORMAT | the decoded or transformed output media type is not one the selected component can expose. |
NS_E_PROTECTED_CONTENT | Retain this result separately if it appears only after the condition has cleared. |
Failure anatomy
The object reached a sample-processing call before its mandatory configuration was complete. Capture which stream or input was being configured, which setter or profile operation succeeded last, and the first processing call that occurred too early.
Build a minimal object with the same profile and execute the documented setup sequence through the final configuration call before submitting any sample. Then reproduce the failing sequence with only the suspected missing or reordered step changed.
A controlled media-format test
- Log
0xC00D0BBC, the exact operation and the first failure time. - Preserve object identity, stream/input/output number, profile GUID, every configuration call in order, HRESULT from each call, and the exact processing method that first returned NS_E_NOT_CONFIGURED.
- Perform one isolated test: keep the media and profile fixed and change only the missing or reordered configuration step.
- Repeat with a newly created object through the same API. Reusing an object after partial initialization can hide the lifecycle defect by carrying state from an earlier attempt.
Profile and sample evidence
| Capture | Why it matters |
|---|---|
| Owning call | Record the API method, object identity, thread or callback and timestamp for the not configured media-format check. |
| Values to record | reader or writer object, stream and input numbers, profile identity, sample timestamps, buffer lengths and the first callback or SDK call that returned the code. |
| Object instance | Note when the reader, writer, graph, URL object, streaming session or metadata provider was created; stale state can reproduce it after configuration has changed. |
| Comparison case | Use one known-good resource that exercises the same not configured media-format check while changing only the rejected precondition. |
Misleading actions
- Do not change media, codec and profile simultaneously. Such a test cannot prove which required initialization step was absent or out of order.
- Record configuration call order, stream/input/output identifiers and profile identity; content bytes are usually less useful than lifecycle evidence for this HRESULT.
Technical references
- Windows Media Format SDK overview
- Input, stream and output formats
- Profiles
- Windows Media SDK objects
- Microsoft HRESULT registry
Treat it as resolved when a fresh object completes the documented configuration sequence and the original processing method succeeds without relying on state left by a previous attempt.
Looking for a different code? Search another status or error code.