What does HRESULT 0xC00D1072 (NS_E_WMX_ITEM_TYPE_ILLEGAL) mean?

 
Previous Next
NS_E_WMX_ITEM_DOES_NOT_EXIST NS_E_WMX_ITEM_UNSETTABLE

NS_E_WMX_ITEM_TYPE_ILLEGAL

Understanding NS_E_WMX_ITEM_TYPE_ILLEGAL in a Windows Media playlist

NS_E_WMX_ITEM_TYPE_ILLEGAL (0xC00D1072) is returned when the requested object type is not permitted at that location in the WMX/WPL playlist model.

Distinguish in-memory Playlist state, WPL or ASX parsing, nested-list expansion, Media-object resolution and execution of referenced items. The actionable checkpoint is the requested object type is not permitted at that location in the WMX/WPL playlist model. Although this result may appear as “cannot play” or “cannot save,” it belongs to a specific object state that should be diagnosed directly.

Playlist boundary

AllStat already supplies the standard user-facing description for this HRESULT; this custom block instead isolates the additional technical boundary. Earlier success in file lookup, network connection, parser creation or graph construction does not prove that the later the operation is valid.

Case-specific checkpoint: parent element type, requested child type, source playlist format and API method used to create it. The controlled comparison for this HRESULT is: create the same item under the documented parent in a new playlist and compare the resulting hierarchy.

Closest distinction: NS_E_WMX_ITEM_UNSETTABLE means an existing item cannot be assigned, not that its type is forbidden.

Evidence from the list model

CaptureWhy it matters for this HRESULT
Object or resourceparent element type, requested child type, source playlist format and API method used to create it
State snapshotRecord the Player openState/playState or operation phase, object identity and exact timestamp when this result was returned.
First lower resultKeep the earliest Win32, Winsock, COM, parser, codec, DRM or device result that appears before this result.
Comparison recordUse one known-good case that follows the same API, protocol and component path while changing only the rejected precondition.

Minimal playlist experiment

  1. Capture the resource identity and parent element type, requested child type, source playlist format and API method used to create it.
  2. verify that the caller uses the current Playlist, Media, Network, graph, device or DRM object generation.
  3. Run the narrow experiment: create the same item under the documented parent in a new playlist and compare the resulting hierarchy.
  4. Do not mix the result experiment with a codec pack, Player reset or broad registry cleanup.
  5. After this result, treat a new specific HRESULT as evidence that this boundary was cleared.

What the result means

Retest outcomeInterpretation
Same it on the same objectThe governing state or value is unchanged, or the caller is reusing an object created before the relevant change.
Fresh object succeedsLifetime, cached configuration or stale playlist/graph state contributed to it.
A later HRESULT appearsThe rejected condition — the requested object type is not permitted at that location in the WMX/WPL playlist model — was cleared for this HRESULT; diagnose the new code at its own layer.
Only one item or endpoint fails for this HRESULTThe evidence favors resource-specific data, rights, routing or device state rather than a global Player failure.

Actions that obscure the cause

  • forcing an unsupported node through raw XML editing.
  • Do not discard the first occurrence by repeatedly invoking Play, open, save or retry; later events can replace its original state.
  • do not publish credentials, private URLs, license material or complete protected-content headers; retain only redacted identifiers, lengths, hashes and protocol fields.

Technical references

The result fix is demonstrated by the same Player path succeeding with the same resource, not by another application opening it.


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