What does HRESULT 0xC00D11BF (NS_E_WMP_GOFULLSCREEN_FAILED) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Windows Media Player cannot switch to Full Screen. You might need to adjust your Windows display settings. Open display settings in Control Panel, and then try setting Hardware acceleration to Full.%0

Previous	Next
NS_E_WMP_NO_PROTOCOLS_SELECTED	NS_E_WMP_NETWORK_ERROR

NS_E_WMP_GOFULLSCREEN_FAILED

Diagnosing NS_E_WMP_GOFULLSCREEN_FAILED in the Windows Media Player playback path

NS_E_WMP_GOFULLSCREEN_FAILED (0xC00D11BF) is returned when the Player-level transition to full-screen presentation could not be completed.

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 the Player-level transition to full-screen presentation could not be completed.

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: video presence, renderer state, window ownership, monitor geometry, display-mode result and foreground restrictions. The controlled comparison for this HRESULT is: confirm windowed rendering, then request full screen on the active monitor after playback reaches running state.

Closest distinction: NS_E_DISPLAY_MODE_CHANGE_FAILED is the lower display-mode switch failure and may be nested beneath this result.

Capture the first failing layer

Capture	Why it matters for this HRESULT
Object or resource	video presence, renderer state, window ownership, monitor geometry, display-mode result and foreground restrictions
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 0xC00D11BF together with its object and operation phase.
Collect video presence, renderer state, window ownership, monitor geometry, display-mode result and foreground restrictions before changing the machine.
Use this single-variable test: confirm windowed rendering, then request full screen on the active monitor after playback reaches running state.
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 — the Player-level transition to full-screen presentation could not be completed — 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

re-encoding the media before testing window and renderer state.
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

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.