| Previous | Next |
| NS_E_WMPCORE_PLAYLIST_ITEM_ALTERNATE_NONE | NS_E_WMPCORE_PLAYLIST_ITEM_ALTERNATE_NAME_NOT_FOUND |
NS_E_WMPCORE_PLAYLIST_ITEM_ALTERNATE_EXHAUSTED
How to classify this WMP result
The symbolic result NS_E_WMPCORE_PLAYLIST_ITEM_ALTERNATE_EXHAUSTED narrows 0xC00D10A0 to the playback core playlist item alternate exhausted condition: all configured alternate references have already been attempted without success. Keep the playback core playlist item alternate exhausted boundary visible when a later dialog reduces it to a general media error.
An additional test is to record the ordered alternate list and the specific HRESULT returned by each attempt; that evidence is more useful than reinstalling the Player or changing several unrelated settings at once.
State worth preserving
Capture state before Player cleanup:
- Decisive check: record the ordered alternate list and the specific HRESULT returned by each attempt.
- Artifact: current item index, alternate index and nested-playlist depth.
- State: repeat/event boundary and the media object expected at its start or end.
- Object identity: playlist URL, format, response content type and exact downloaded bytes.
- Underlying evidence: ASX version and element stack at the failure.
- Correlation: resolved base URL for REF or ENTRYREF targets.
Log paths, hashes, IDs, offsets, and HRESULTs. Exclude secrets and unrelated content from logs.
Reproduce without destroying evidence
- Find the first component that returned this result and label that event as this 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 ordered alternate list and the specific HRESULT returned by each attempt.
- Make the narrow correction—repair at least one alternate or stop retrying after the final recorded source—and repeat the same producing operation.
What succeeds before this failure
Two rules frame this diagnosis. First, windows Media metafiles are XML documents, but a well-formed document can still violate required ASX element and attribute rules. In this case, relative references are resolved against the containing metafile URL, and nested playlists introduce a stack and a new base URL rather than a simple flat list.
Representative case: Several rollover URLs exist, but each one fails and the retry cursor reaches the end. The example isolates only the producing component.
Related HRESULTs, different boundaries
| Result | Different boundary |
|---|---|
NS_E_WMPCORE_PLAYLIST_ITEM_ALTERNATE_NAME_NOT_FOUND | The named alternate playlist cannot be found in the available alternate set |
NS_E_WMPCORE_PLAYLIST_ITEM_ALTERNATE_NONE | The playlist item defines no alternate reference to use after its primary source fails |
NS_E_WMPCORE_FAILED_TO_BUILD_PLAYLIST | The core cannot turn the downloaded/loaded playlist representation into a usable Playlist object |
If this result is followed by a broader “cannot play,” “cannot load,” or “operation failed” result, preserve the earlier event. A later wrapper error may be secondary.
Recovery at the right layer
Resolve this result where the relevant state is produced: repair at least one alternate or stop retrying after the final recorded source. After correction, reload or recreate the owning object so cached failure state is not mistaken for a successful repair.
- Avoid flattening or rewriting a playlist before preserving the failing nesting and base-URL rules; it can destroy the artifact or state needed to explain this result.
- Avoid assuming every unplayable item means the playlist parser itself failed; that can replace the original HRESULT with a secondary failure from another layer.
Practical interpretation
Use it, 0xC00D10A0 and the symbolic phrase in traces. Correlate search keys with API and object.
How to know the repair is real
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.
Technical references
- Windows Media metafile reference — normative or platform material relevant to it.
- Metafile elements reference — API or format context for this HRESULT.
- ENTRYREF element — documentation used to identify the producing boundary of it.
- REPEAT element
Looking for a different code? Search another status or error code.