HRESULT 0xC00D106C (NS_E_ASX_NOTHING_TO

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Windows Media Player cannot save the playlist because it does not contain any items.%0

Previous	Next
NS_E_ASX_INVALID_REPEAT_BLOCK	NS_E_URLLIST_INVALIDFORMAT

NS_E_ASX_NOTHING_TO_WRITE

Understanding NS_E_ASX_NOTHING_TO_WRITE in a Windows Media playlist

NS_E_ASX_NOTHING_TO_WRITE (0xC00D106C) is returned when the serializer was asked to save an ASX playlist that contains no serializable entries.

For NS_E_ASX_NOTHING_TO_WRITE, distinguish in-memory Playlist state, WPL or ASX parsing, nested-list expansion, Media-object resolution and execution of referenced items. Here, the decisive boundary is the serializer was asked to save an ASX playlist that contains no serializable entries. NS_E_ASX_NOTHING_TO_WRITE is most useful when treated as a Player checkpoint, not as a recommendation to reinstall everything.

Playlist boundary

AllStat already supplies the standard user-facing description for NS_E_ASX_NOTHING_TO_WRITE; 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 NS_E_ASX_NOTHING_TO_WRITE operation is valid.

Case-specific checkpoint: playlist count, item types, transient entries, unresolved Media objects and output path. The controlled comparison for NS_E_ASX_NOTHING_TO_WRITE is: insert one local Media item into a fresh Playlist object and save to a writable new file.

Closest distinction: NS_E_WMX_PLAYLIST_EMPTY can block an action on an empty runtime list even when no serialization was requested.

Evidence from the list model

Capture	Why it matters for `NS_E_ASX_NOTHING_TO_WRITE`
Object or resource	playlist count, item types, transient entries, unresolved Media objects and output path
State snapshot	Record the Player openState/playState or operation phase, object identity and exact timestamp when NS_E_ASX_NOTHING_TO_WRITE was returned.
First lower result	Keep the earliest Win32, Winsock, COM, parser, codec, DRM or device result that appears before NS_E_ASX_NOTHING_TO_WRITE.
Comparison record	For NS_E_ASX_NOTHING_TO_WRITE, use one known-good case that follows the same API, protocol and component path while changing only the rejected precondition.

Minimal playlist experiment

Record 0xC00D106C, NS_E_ASX_NOTHING_TO_WRITE, the exact method or command and the first failure time.
Preserve playlist count, item types, transient entries, unresolved Media objects and output path.
Perform one isolated comparison: insert one local Media item into a fresh Playlist object and save to a writable new file.
Repeat the original Player path after NS_E_ASX_NOTHING_TO_WRITE and keep any new HRESULT as a downstream result.
For NS_E_ASX_NOTHING_TO_WRITE, confirm the expected state transition rather than only disappearance of the dialog.

What the result means

Retest outcome	Interpretation
Same NS_E_ASX_NOTHING_TO_WRITE on the same object	For NS_E_ASX_NOTHING_TO_WRITE, 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 NS_E_ASX_NOTHING_TO_WRITE.
A later HRESULT appears	The rejected condition — the serializer was asked to save an ASX playlist that contains no serializable entries — was cleared for NS_E_ASX_NOTHING_TO_WRITE; diagnose the new code at its own layer.
Only one item or endpoint fails for NS_E_ASX_NOTHING_TO_WRITE	For NS_E_ASX_NOTHING_TO_WRITE, the evidence favors resource-specific data, rights, routing or device state rather than a global Player failure.

Actions that obscure the cause

creating an empty destination file before calling save.
Do not discard the first NS_E_ASX_NOTHING_TO_WRITE occurrence by repeatedly invoking Play, open, save or retry; later events can replace its original state.
For NS_E_ASX_NOTHING_TO_WRITE, do not publish credentials, private URLs, license material or complete protected-content headers; retain only redacted identifiers, lengths, hashes and protocol fields.

Technical references

Close NS_E_ASX_NOTHING_TO_WRITE only when the original operation crosses this boundary and reaches the expected next Player state.

Looking for a different code? Search another status or error code.