What does HRESULT 0x80040282 (VFW_E_DVD_MENU_DOES_NOT_EXIST) mean?

 
Previous Next
VFW_E_DVD_WRONG_SPEED VFW_E_DVD_CMD_CANCELLED

VFW_E_DVD_MENU_DOES_NOT_EXIST

Exact result and bit fields

VFW_E_DVD_MENU_DOES_NOT_EXIST has the unsigned HRESULT value 2147746434 (0x80040282) and the signed 32-bit representation -2147220862. AllStat describes it as “The specified menu doesn't exist”. In the operation that produces this result, IDvdControl2 is asked to show a DVD menu that the current disc or title set does not contain.

The high bit is set, so this value is a failure HRESULT. Its facility field is 4 (FACILITY_ITF) and its low code is 642 (0x0282). These fields classify this result, but they do not identify which filter, thread, device, file or graph generation returned it.

Contract boundary

This result belongs to the legacy DirectShow DVD Navigator contract. DVD state is authored and stateful: domains, user-operation controls, titles, menus, streams, command objects and graph construction each impose different preconditions.

The practical owner to locate for this HRESULT is the DVD Navigator, graph builder, decoder inventory and renderer topology. 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 disc was authored without that optional menu.
  • Cause 2 for this HRESULT: the requested DVD_MENU_ID is invalid for the current title set.
  • Cause 3 for this HRESULT: the application assumes every disc provides audio, angle or chapter submenus.

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 disc identifiers, navigation state, parental settings and media paths.

  • Evidence 1 for this HRESULT: requested menu identifier.
  • Evidence 2 for this HRESULT: current domain, title and VTS.
  • Evidence 3 for this HRESULT: disc menu inventory and preceding title-set change.

Step-by-step diagnosis

  1. Capture it at the first native return, not only at the top-level playback failure.
  2. identify the exact graph stage described here: IDvdControl2 is asked to show a DVD menu that the current disc or title set does not contain.
  3. compare the live object state, topology and input with the documented interface preconditions.
  4. Before changing filters, drivers, registry data or media for this HRESULT, collect the code-specific evidence below.
  5. Test one evidence-backed the correction on the smallest reproducible graph.
  6. 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: query or infer menu availability before enabling a command.
  • Action 2 for this HRESULT: fall back to the root or title menu when appropriate.
  • Action 3 for this HRESULT: treat optional-menu absence as content variation, not disc corruption.

Retry and recovery

Retry rule for this HRESULT: Retry only after entering a title set that actually contains the requested menu or choosing another menu. 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.

Example incident

A player always exposes a chapter-menu button, but a simple disc has only a root menu; hiding the unsupported control prevents it. This example keeps the diagnosis at the specific the boundary instead of treating every DirectShow failure as a codec reinstall problem.

How it differs from nearby results

VFW_E_DVD_NO_BUTTON means a menu context lacks the requested button; it means the requested menu is absent. Keep those cases separate in telemetry, UI messages and retry policy because their next actions are different.

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.

Official Microsoft references

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