| Previous | Next |
| NS_E_WMP_DSHOW_UNSUPPORTED_FORMAT | NS_E_WMP_NONMEDIA_FILES |
NS_E_WMP_PLAYLIST_EXISTS
Diagnosing NS_E_WMP_PLAYLIST_EXISTS in the Windows Media Player playback path
NS_E_WMP_PLAYLIST_EXISTS (0xC00D119B) is returned when playlist creation collided with an existing library playlist name or identity.
Trace path or URL resolution, proxy and network selection, parser and codec discovery, graph construction, rendering and optional DRM as separate layers. Record what the Player had already completed because later retries often replace the original evidence. The specific rejected condition is playlist creation collided with an existing library playlist name or identity.
Playback 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: requested name, existing PlaylistCollection entries, case normalization and whether the item is static or auto-generated. The controlled comparison for this HRESULT is: enumerate current playlists, choose a unique name and create a new empty list once.
Closest distinction: NS_E_WMX_ATTRIBUTE_ALREADY_EXISTS concerns metadata inside one playlist, not the playlist collection.
Capture the first failing layer
| Capture | Why it matters for this HRESULT |
|---|---|
| Object or resource | requested name, existing PlaylistCollection entries, case normalization and whether the item is static or auto-generated |
| State snapshot | Record the Player openState/playState or operation phase, object identity and exact timestamp when this result was returned. |
| First lower result | Keep the earliest Win32, Winsock, COM, parser, codec, DRM or device result that appears before this result. |
| Comparison record | Use one known-good case that follows the same API, protocol and component path while changing only the rejected precondition. |
Controlled playback comparison
- Start from the original call and log
0xC00D119Btogether with its object and operation phase. - Collect requested name, existing PlaylistCollection entries, case normalization and whether the item is static or auto-generated before changing the machine.
- Use this single-variable test: enumerate current playlists, choose a unique name and create a new empty list once.
- repeat on a fresh object if the original predates a configuration, device or resource change.
- validate the expected next operation, not just initial open or object creation.
How to interpret the retest
| Retest outcome | Interpretation |
|---|---|
| Same this result on the same object | The governing state or value is unchanged, or the caller is reusing an object created before the relevant change. |
| Fresh object succeeds | Lifetime, cached configuration or stale playlist/graph state contributed to this result. |
| A later HRESULT appears | The rejected condition — playlist creation collided with an existing library playlist name or identity — was cleared for this HRESULT; diagnose the new code at its own layer. |
| Only one item or endpoint fails for this HRESULT | The evidence favors resource-specific data, rights, routing or device state rather than a global Player failure. |
Actions that obscure the cause
- deleting the media files referenced by the existing playlist.
- 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
- Supported protocols and file types
- Using Windows Media in DirectShow
- Working with codecs
- DirectShow filters
- Microsoft HRESULT registry
Retain before-and-after evidence for this HRESULT so object recreation or content replacement is not mistaken for random retry success.
Looking for a different code? Search another status or error code.
