| Previous | Next |
| NS_E_WMPCORE_WMX_LIST_ATTRIBUTE_VALUE_EMPTY | NS_E_WMPCORE_WMX_LIST_ITEM_ATTRIBUTE_NAME_EMPTY |
NS_E_WMPCORE_WMX_LIST_ATTRIBUTE_VALUE_ILLEGAL
Where the Player stopped
NS_E_WMPCORE_WMX_LIST_ATTRIBUTE_VALUE_ILLEGAL is HRESULT 0xC00D1094. At the playback core WMX list attribute value illegal checkpoint it means the WMX list attribute name is accepted, but its supplied value is illegal for that property; the result belongs to Windows Media playlist attribute-value validation, not to an unspecified Player failure.
An additional test is to record the raw lexical value, expected type/range and conversion result before application; that evidence is more useful than reinstalling the Player or changing several unrelated settings at once.
How to prove the condition
- Find the first component that returned this result and label that event as the playback core WMX list attribute value illegal boundary.
- Freeze the input and object identity associated with the failing operation before WMP fallback or cleanup changes it.
- Reconstruct the immediately preceding successful state, then identify the call or event that crossed into failure.
- Perform the code-specific test: record the raw lexical value, expected type/range and conversion result before application.
- Make the narrow correction—emit a value permitted by the property contract without changing the already recognized name—and repeat the same producing operation.
Minimum useful incident record
Capture state before Player cleanup:
- Decisive check: record the raw lexical value, expected type/range and conversion result before application.
- Artifact: raw value including whitespace, quoting and escaping.
- State: expected data type, enumeration or range for that property.
- Object identity: conversion result before the property is applied.
- Underlying evidence: producer version and a known-good value for the same attribute.
- Correlation: accepted attribute name and owning list element.
Log paths, hashes, IDs, offsets, and HRESULTs. Exclude secrets and unrelated content from logs.
Why the producing component matters
Before changing state, remember that a legal attribute name can still carry an empty, out-of-range or unsupported value; this result therefore starts after name lookup succeeds. A second platform rule is that the raw lexical value and the expected property type or enumeration are more useful than only the serialized playlist line.
Representative case: A legal list property receives an unsupported enumeration token or malformed numeric value. The example isolates only the producing component.
A narrow remediation path
Resolve this result where the relevant state is produced: emit a value permitted by the property contract without changing the already recognized name. After correction, reload or recreate the owning object so cached failure state is not mistaken for a successful repair.
- Avoid renaming the accepted attribute instead of diagnosing its value contract; it can destroy the artifact or state needed to explain this result.
- Avoid coercing the value generically without recording the original lexical representation; that can replace the original HRESULT with a secondary failure from another layer.
Neighboring codes to separate
| Result | Different boundary |
|---|
If it is followed by a broader “cannot play,” “cannot load,” or “operation failed” result, preserve the earlier event. A later wrapper error may be secondary.
Completion criteria
Repeat the action that returned it and verify that the same object crosses the former this checkpoint. Success means reaching the next expected load, parse, playlist, control or playback state—not merely suppressing a dialog.
A representative failure pattern
Use it, 0xC00D1094 and the symbolic phrase in traces. Correlate search keys with API and object.
Technical references
- Windows Media metafile reference — normative or platform material relevant to it.
- Metafile elements reference — API or format context for this HRESULT.
- Playlists and media items — documentation used to identify the producing boundary of it.
- XML 1.0 specification
Looking for a different code? Search another status or error code.