| Previous | Next |
| NS_E_WMPCORE_PLAYLIST_EMPTY_NESTED_PLAYLIST_SKIPPED_ITEMS | NS_E_WMPCORE_MEDIA_CHILD_PLAYLIST_UNAVAILABLE |
NS_E_WMPCORE_BUSY
The exact condition behind the dialog
0xC00D10B7 maps to NS_E_WMPCORE_BUSY. Its actionable interpretation is the Player core is occupied by an operation that prevents opening or playing this item now within the WMP playback core, graph and media-resource boundary; the producing mechanism is the core that resolves Player.URL, selects or builds a playback graph, chooses codecs and devices, prerolls media and advances between playlist items while reporting asynchronous errors.
An additional test is to record pending open/close/transition and operation owner; that evidence is more useful than reinstalling the Player or changing several unrelated settings at once.
Evidence to capture before retry
Preserve the first occurrence before retry or fallback changes the playback core busy evidence. Capture one consistent object generation:
| Field | What to record |
|---|---|
| Decisive check | Record pending open/close/transition and operation owner |
| Artifact identity | Ordered ErrorItem queue with errorCode, errorContext and media object for the playback core busy reproduction |
| Runtime state | Player.URL, current media sourceURL and resolved final URL for this reproduction |
| Owning object | Play state and transition immediately before failure for this reproduction |
| Lower-level result | Selected graph/source/filter or codec identity and version for this reproduction |
| Correlation | Audio/video device identity and driver generation for this reproduction |
Log paths, hashes, IDs, offsets, and HRESULTs. Exclude secrets and unrelated content from logs.
How this layer works
this workflow must be separated from a generic WMP failure: the URL, playlist item, selected source, graph and codec are distinct objects; a failure at one should not be diagnosed by replacing all of them at once. It also matters that the Error and MediaError paths can queue several results, so the first specific HRESULT and its error context are more useful than the last dialog.
Representative case: Rapid source changes overlap graph teardown and next-item open. The example isolates only the producing component.
A focused diagnostic sequence
- Start with the symbolic value this result; do not diagnose the failure from the final dialog alone.
- Record the bytes or object state that produced this condition before automatic recovery mutates it.
- Exclude a stale callback or superseded object generation as the source of this event.
- Use this deciding observation for this condition: record pending open/close/transition and operation owner.
- Apply the smallest supported remedy for this condition: wait for completion or cancel the owning operation before retrying once.
Correct the producing condition
The targeted correction for this condition is to wait for completion or cancel the owning operation before retrying once. Keep the original failing input until the same operation succeeds after one controlled change.
- Avoid installing broad codec packs before identifying the requested media subtype and missing component; it can destroy the artifact or state needed to explain this result.
- Avoid clearing the error queue or skipping to another playlist item before preserving the first failing media object; that can replace the original HRESULT with a secondary failure from another layer.
Why the symbolic name matters
| Result | Different boundary |
|---|---|
NS_E_WMPCORE_FILE_NOT_FOUND | The media file referenced by the playlist or library item is absent at its resolved path |
NS_E_WMPCORE_MEDIA_UNAVAILABLE | The media resource is currently unavailable at its local, removable or network location |
NS_E_WMPCORE_TEMP_FILE_NOT_FOUND | A temporary artifact created for download, conversion or staging disappeared before consumption |
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.
What to search for in traces
Use this result, 0xC00D10B7 and the symbolic phrase in traces. Correlate search keys with API and object.
Regression check
After correction, create a fresh Player, control, parser or playlist object and rerun the smallest reproducer for this HRESULT. Verify the resulting resource, list membership, saved file, library object or play state.
Technical references
- Windows Media Player SDK — documentation used to identify the producing boundary of it.
- Player MediaError event — normative or platform material relevant to it.
- ErrorItem object — API or format context for this HRESULT.
- Supported protocols and file types It.
Looking for a different code? Search another status or error code.