| Previous | Next |
| DRAGDROP_S_USEDEFAULTCURSORS | DATA_S_SAMEFORMATETC |
VFW_S_NO_MORE_ITEMS
DirectShow enumeration reached the end
VFW_S_NO_MORE_ITEMS is HRESULT 262403 (0x00040103) from Video for Windows. AllStat describes this result as “The end of the list has been reached.” The high-order severity bit is clear, so this is a success result, but it carries more information than plain S_OK.
A Video for Windows or DirectShow list operation completed and has no additional item to return.
Evidence and telemetry to preserve
- preserve enumerator type and owner.
- preserve requested and returned item counts.
- preserve enumeration position.
- preserve filter graph generation or device-change timestamp.
- preserve released interface references.
Also record vfw_s_no_more_items_operation, vfw_s_no_more_items_object, vfw_s_no_more_items_state_before, vfw_s_no_more_items_state_after, UTC time, process and thread identifiers, and a correlation ID. Keep secrets out of logs while retaining GUIDs, CLSIDs, media subtypes, property IDs, row identities, and hashes needed to distinguish objects.
Where the result is encountered
- This result can appear in filter, media-type, or device enumeration in legacy media code; record the producing interface and method rather than inferring behavior from the symbolic name alone.
- This result can appear in iteration over component-owned collections; record the producing interface and method rather than inferring behavior from the symbolic name alone.
- It can appear in compatibility layers that use VFW-specific success values; record the producing interface and method rather than inferring behavior from the symbolic name alone.
The same numeric success value can be mishandled when a wrapper exposes only a Boolean. Keep the original HRESULT until the code-specific outputs and state transition have been evaluated.
State boundary that must be proved
The central question for it is whether all items already returned were consumed and the end position belongs to the same enumeration snapshot. The HRESULT alone confirms neither unrelated work nor the quality of optional outputs.
A reliable interpretation of it names the exact method contract, the object generation, and the outputs that remain valid. This prevents a success-with-information result from being promoted to full success or demoted to a generic error.
Diagnostic sequence
- capture the raw HRESULT
0x00040103immediately after the returning method and record whether the caller usedSUCCEEDED,FAILED, equality testing, or exception translation. - Identify the exact owner of it: interface, method, object instance, provider or filter version, thread or apartment, and operation phase.
- Validate the decisive contract boundary for it: all items already returned were consumed and the end position belongs to the same enumeration snapshot.
- inspect every output parameter, count, status array, returned interface, or side effect that the method documentation associates with this success-with-information result.
- Compare the observed state before and after it; do not assume that a success severity bit means every optional sub-operation completed.
- reproduce the smallest request with the same object state and then change only the condition identified by the evidence before repeating the operation.
Difference from nearby HRESULT values
S_FALSE is a generic COM end or false result; it is the media-component-specific end marker.
This distinction determines whether the caller should consume partial outputs, stop iteration, wait, reconfigure, notify the user, or perform no error recovery at all.
Correct handling, retry, and recovery
Stop the enumeration normally and keep previously returned items. Do not retry from the beginning unless the underlying collection changed or the caller intentionally requests a new snapshot.
Retry it only when the recorded state can change the documented outcome. Repeating the same call is inappropriate for a stable end marker, cancellation, unsupported format, adjusted property, or partial result whose completed side effects have not been reconciled.
Practical validation scenario
A diagnostic tool enumerates registered media components, consumes every returned entry, and receives it. It closes the enumerator and reports the completed count rather than an error.
The negative test should preserve the condition that produces it; the recovery test should alter only that condition and verify the final state as well as the HRESULT.
Developer and administrator guidance
When it crosses process, RPC, scripting, or managed-code boundaries, preserve the unsigned 32-bit value and symbolic name. A signed decimal rendering can obscure that the severity bit indicates success and can lead to incorrect exception or retry behavior.
A support report for it should include decimal 262403, hexadecimal 0x00040103, the AllStat meaning, the owning API, and the first detailed status or output that explains why the method did not return ordinary S_OK.
References
Looking for a different code? Search another status or error code.