| Previous | Next |
| NS_E_WMPXML_EMPTYDOC | NS_E_WMP_FILESCANALREADYSTARTED |
NS_E_WMP_PATH_ALREADY_IN_LIBRARY
What this HRESULT actually isolates
The symbolic result NS_E_WMP_PATH_ALREADY_IN_LIBRARY narrows 0xC00D0FBA to the path already in library condition: the library already contains a record for the canonicalized media path. Keep the path already in library boundary visible when a later dialog reduces it to a general media error.
An additional test is to compare normalized path, file ID and existing Media object rather than string spelling alone; 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: compare normalized path, file ID and existing Media object rather than string spelling alone.
- Artifact: library type, database identity and user profile owning the operation.
- State: canonical local/UNC/URL path and file identity.
- Object identity: media object ID or HME container/item ID.
- Underlying evidence: scan/search generation and the request that superseded it.
- Correlation: first library or file-system HRESULT before the Player-level summary.
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: compare normalized path, file ID and existing Media object rather than string spelling alone.
- Make the narrow correction—reuse/update the existing record or remove the stale entry through the library API—and repeat the same producing operation.
What succeeds before this failure
Two rules frame this diagnosis. First, adding an item to the library does not move the underlying file, and a library row can survive after its path or shared object becomes unavailable. A scan, search or Home Media Experience request is stateful, so stale identifiers and overlapping operations must be separated from file-format failures.
Representative case: The same file is submitted once by drive-letter path and once through an equivalent normalized path. The example isolates only the producing component.
Related HRESULTs, different boundaries
| Result | Different boundary |
|---|---|
NS_E_WMP_FILESCANALREADYSTARTED | A library file-scan generation is already active |
NS_E_WMP_HME_INVALIDOBJECTID | The Home Media Experience object identifier no longer resolves in the current shared-library view |
NS_E_WMP_HME_NOTSEARCHABLEFORITEMS | The selected HME container does not advertise item-search capability |
If this result is followed by a broader “cannot play,” “cannot load,” or “operation failed” result, preserve the earlier event. The later code can be a consequence from a wrapper, fallback item or UI layer rather than the producing failure.
Recovery at the right layer
Resolve this result where the relevant state is produced: reuse/update the existing record or remove the stale entry through the library API. After correction, reload or recreate the owning object so cached failure state is not mistaken for a successful repair.
- Avoid deleting the entire media database before exporting the failing object IDs and paths; it can destroy the artifact or state needed to explain this result.
- Avoid assuming a successful file open proves that the library record and sharing view are current; that can replace the original HRESULT with a secondary failure from another layer.
Practical interpretation
Use it, 0xC00D0FBA 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
- Accessing the library programmatically — normative or platform material relevant to it.
- MediaCollection object — API or format context for this HRESULT.
- MediaCollection. Add method — documentation used to identify the producing boundary of it.
- Error handling in the WMP object model
Looking for a different code? Search another status or error code.