What does HRESULT 0xC00D11D1 (NS_E_WMP_BAD_DRIVER) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Windows Media Player cannot play the file because there might be a problem with your sound or video device. Try installing an updated device driver.%0

Previous	Next
NS_E_WMP_DRM_NEEDS_AUTHORIZATION	NS_E_WMP_ACCESS_DENIED

NS_E_WMP_BAD_DRIVER

Diagnosing NS_E_WMP_BAD_DRIVER in the Windows Media Player playback path

NS_E_WMP_BAD_DRIVER (0xC00D11D1) is returned when the media graph reached an audio or video driver that failed capability, initialization or runtime checks.

Trace path or URL resolution, proxy and network selection, parser and codec discovery, graph construction, rendering and optional DRM as separate layers. This result identifies a narrower stage than the dialog text exposes, so preserve its operation before trying a workaround. In this case the rejected checkpoint is the media graph reached an audio or video driver that failed capability, initialization or runtime checks.

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: device instance, driver version/signature, renderer, requested format, PnP events and kernel/device error. The controlled comparison for this HRESULT is: switch to a known working endpoint or software renderer while leaving the source and codec unchanged.

Closest distinction: NS_E_WMP_AUDIO_HW_PROBLEM is audio-specific; this code can identify either audio or video driver trouble.

Capture the first failing layer

Capture	Why it matters for this HRESULT
Object or resource	device instance, driver version/signature, renderer, requested format, PnP events and kernel/device error
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

Freeze the current object state and collect device instance, driver version/signature, renderer, requested format, PnP events and kernel/device error.
Reproduce this result once without automatic retries or fallback applications.
Change only one precondition: switch to a known working endpoint or software renderer while leaving the source and codec unchanged.
compare the first nested status and next Player event with the failed run.
After testing it, restore the original configuration if the change was diagnostic only.

How to interpret the retest

Retest outcome	Interpretation
Same it 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 it.
A later HRESULT appears	The rejected condition — the media graph reached an audio or video driver that failed capability, initialization or runtime checks — 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

updating every driver without recording which device owned the failing renderer.
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

After it, a different downstream HRESULT is progress and should be recorded as a separate condition.

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