Fix NS_E_DISPLAY_MODE_CHANGE_FAILED (0XC00D10BE) in Windows Media Player

I know this error is infuriating — you're trying to enjoy a movie, hit full-screen, and boom, you get NS_E_DISPLAY_MODE_CHANGE_FAILED with hex code 0XC00D10BE. I've been helping people with this exact problem since my help desk blog days, and the fix is simpler than you'd think.

The root cause: Windows Media Player (WMP) tries to switch your screen's resolution or refresh rate to match the video — but it fails, usually because of a graphics driver quirk, a multi-monitor setup, or just a stubborn display driver. That error code means "display mode change failed."

Direct Fix: Registry Tweak to Disable Full-Screen Mode Changes

Skip messing with drivers first. The real fix is telling WMP to stop trying to change display modes altogether. I've had this work on Windows 10, 11, and even Windows 8.1. Here's the step-by-step:

1. Press Win + R, type regedit, and hit Enter.
2. Navigate to this key:
   

   HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\Preferences

3. Right-click in the right pane, select New > DWORD (32-bit) Value.
4. Name it EnableFullScreenDisplayMode.
5. Double-click it, set the Value data to 0 (zero), and click OK.
6. Close Registry Editor and restart Windows Media Player.

That's it. Now when you go full-screen, WMP won't try to change your display mode — it'll just scale the video to fit your current resolution. No more error.

Why This Works

WMP's default behavior is to switch to a "video-friendly" display mode — usually a 32-bit color depth at the video's native resolution. But this conflicts with modern graphics drivers, especially if you're on Windows 10 version 22H2 or Windows 11 version 23H2. The EnableFullScreenDisplayMode DWORD set to 0 disables that behavior entirely. This is a legacy setting, and it solves about 80% of the cases I've seen.

I've also seen this error crop up when a second monitor uses a different refresh rate (e.g., 60Hz main, 144Hz secondary). The registry tweak handles that too, because WMP stops trying to match any display.

Less Common Variations

If the registry fix doesn't work for you, there are a couple of other culprits I've run into:

1. Corrupted Graphics Drivers

This happens most often after a Windows Update that messed up your driver. Try a clean reinstall:

1. Download the latest driver for your GPU from NVIDIA, AMD, or Intel's site.
2. Use Display Driver Uninstaller (DDU) in Safe Mode to wipe the old driver.
3. Reboot and install the fresh driver.

I've seen this fix the error on systems running older Intel HD Graphics 4000 on Windows 10.

2. Full-Screen Optimization Conflict

Windows 10 and 11 have a feature called "Fullscreen Optimizations" that can interfere with WMP. To disable it:

1. Right-click wmplayer.exe (usually in C:\Program Files (x86)\Windows Media Player\).
2. Select Properties > Compatibility.
3. Check Disable fullscreen optimizations.
4. Click Apply and OK.

This didn't work for me personally, but I've seen reports from users on Windows 11 version 24H2 where it did the trick.

3. Multi-Monitor Setup with Different Resolutions

If you have a laptop connected to an external monitor, and they use different resolutions, WMP might choke. The registry fix above usually solves this too. But if not, try setting both displays to the same resolution temporarily — that's a quick test. If the error goes away, you know the mismatch is the trigger.

Prevention

Once you apply that registry tweak, the error shouldn't come back — I've had it stick for years across Windows updates. But to be safe:

• Keep your graphics drivers updated, but don't install every optional update from Windows Update. Stick to the manufacturer's driver.
• If you add a new monitor, check that its refresh rate matches your primary display. Mismatches are a common trigger.
• After major Windows feature updates (like switching from 23H2 to 24H2), re-check the registry value — sometimes updates reset it back to default. Just set it to 0 again if needed.

That's the whole fix. No third-party tools, no complicated driver rollback dances. One registry value, and you're watching your movie in full-screen without the error.