Windows Media Player Not Working? 5 Proven Fixes & a Better Alternative

Why Is Windows Media Player Not Working?

Before jumping into fixes, it helps to understand why Windows Media Player (WMP) breaks in the first place. From an engineering standpoint, WMP relies on a stack of components: COM-registered DLL files, codec filters registered in the Windows registry, and the Windows Media Foundation pipeline. When any layer in that stack gets corrupted or misconfigured, the whole player can fail in one of several ways:

• WMP launches but immediately crashes: typically a corrupted wmp.dll or broken COM registration
• WMP opens but won't play files: usually a missing or incompatible codec (the decoder that translates compressed video/audio back into playable data)
• WMP shows a black screen with audio: a video renderer or DirectX issue

The remaining two are less common but worth knowing. Error-code failures (e.g., 0xC00D36FA or 0xC00D11CD) are actually the easiest to diagnose. And if WMP is missing altogether on Windows 11, that's expected: Microsoft ships it as an optional component called "Windows Media Player Legacy" that must be manually enabled.

I've reproduced all five scenarios on my Dell XPS 15 and confirmed each fix below works on both Windows 10 (22H2) and Windows 11 (23H2).

Fix 1: Run the WMP Troubleshooter (Windows 10 & 11)

The built-in troubleshooter is the right first move. It scans WMP's registered components, resets the media library cache, and attempts to re-register broken DLL files automatically, all without requiring admin command-line work.

Steps for Windows 10:

1. Press Windows + X and select Control Panel
2. In the search box, type troubleshooting and click Troubleshooting
3. Select View all from the left panel
4. Scroll to Windows Media Player Settings and double-click it
5. Right-click the troubleshooter and select Run as administrator
6. Follow the on-screen prompts and apply any fixes it suggests

Steps for Windows 11:

1. Press Windows + I to open Settings
2. Navigate to System → Troubleshoot → Other troubleshooters
3. Scroll to find Windows Media Player and click Run
4. Apply recommended fixes and restart WMP

The troubleshooter resolves roughly half of WMP launch failures in my experience, particularly those caused by a corrupted media library database. If WMP still won't open after this step, move to Fix 2.

Fix 2: Re-Register WMP DLL Files

This fix targets the most common cause of WMP refusing to launch: unregistered or corrupted COM components. DLL files are shared code modules that WMP depends on, including vbscript.dll, jscript.dll, and wmp.dll itself. When these lose their registry entries, which can happen after a failed Windows Update or third-party software install, WMP breaks silently.

Re-registering them with regsvr32 forces Windows to rebuild those registry entries.

Steps:

1. Click Start, type cmd, then right-click Command Prompt and select Run as administrator
2. In the Command Prompt window, run these three commands one by one, pressing Enter after each:

     regsvr32 vbscript.dll
     regsvr32 jscript.dll
     regsvr32 wmp.dll

3. You should see a success dialog for each command. If any shows an error, note the error message — it may indicate the DLL file itself is corrupted (see Fix 3)
4. Close Command Prompt and relaunch Windows Media Player

I tested this fix on a machine where WMP displayed a "Windows Media Player encountered a problem" error on launch, and the DLL re-registration resolved it within 30 seconds. No restart required.

Fix 3: Reinstall Windows Media Player via Windows Features

If re-registering DLL files didn't work, the WMP installation itself may be partially corrupted. The cleanest solution is to remove WMP through Windows Features and reinstall it. This replaces all WMP files from the Windows component store without affecting your user data or media library.

Steps for Windows 10:

1. Press Windows + R, type appwiz.cpl, and press Enter
2. In Programs and Features, click Turn Windows features on or off (left panel)
3. Scroll to Media Features and expand it
4. Uncheck Windows Media Player and click OK
5. Restart your computer
6. Repeat steps 1–3, re-check Windows Media Player, click OK
7. Restart again

Steps for Windows 11:

The process is slightly different. On Windows 11, WMP is listed as "Windows Media Player Legacy" under Optional Features:

1. Open Settings → Apps → Optional features
2. Search for Windows Media Player Legacy
3. If it's installed, click it and select Uninstall, then restart
4. Return to Optional features, click Add a feature, search for Windows Media Player Legacy, and install it
5. Restart when prompted

Note for Windows 11 users: If you can't find WMP at all, this is normal. Microsoft replaced the legacy WMP with a new "Media Player" app in Windows 11 22H2. The new app handles most formats but lacks some of WMP's advanced library and DVD features. You can still install the legacy version via Optional Features using the steps above.

Fix 4: Decode WMP Error Codes and Fix the Root Cause

Windows Media Player's error codes are actually diagnostic gold: each one points to a specific failure in the media pipeline. Here's a reference table for the most common codes I've encountered, along with the targeted fix for each:

For codec errors (0xC00D11xx / 0xC00D36FA):

The fastest resolution is installing K-Lite Codec Pack. This installs the most common video and audio decoders, including H.264, H.265/HEVC, and VP9, that Windows doesn't ship by default. Download the Basic version from the official K-Lite site and run the installer with default settings. Restart WMP after installation.

For hardware acceleration issues (0xC00D1059):

In WMP, go to Tools → Options → Performance → Advanced and toggle the hardware acceleration slider. Some GPU drivers conflict with WMP's DirectX rendering pipeline, reducing acceleration sometimes resolves persistent black-screen issues.

Fix 5: System Restore for Windows Media Player

If none of the above fixes work, and WMP was working correctly before a recent system change (Windows Update, driver install, or software install), System Restore can roll your system back to a known-good state while preserving your personal files.

Steps:

1. Click Start and type System Restore
2. Select Create a restore point from results, then click System Restore in the dialog
3. Click Next, then choose a restore point dated before WMP started failing
4. Click Scan for affected programs to review what will change
5. Click Next → Finish to begin the restore process

The system will restart automatically. System Restore does not affect documents, photos, or other personal files, but only system files and installed applications from after the restore point date are rolled back.

Important: If you don't see any restore points, System Restore may have been disabled on your machine. In that case, proceed to the alternative below.

What Has Replaced Windows Media Player? Meet PlayerFab

If you've tried all five fixes and WMP still isn't cooperating, or if you're on Windows 11 and want a media player that doesn't require troubleshooting, it's worth asking: what has replaced Windows Media Player as the go-to option?

Microsoft's answer is the new Media Player app built into Windows 11, which handles MP4, MKV, and most common formats cleanly. But it lacks DVD playback, advanced codec support, and the kind of hardware-accelerated 4K performance that modern media demands. The alternative I recommend and use daily is PlayerFab.

Why PlayerFab Handles What WMP Can't

PlayerFab is built on a different media engine than Windows Media Foundation. Where WMP relies on system-registered codecs, PlayerFab bundles its own codec library internally. That means:

• No codec installation required: MP4, MKV, AVI, MOV, FLV, and dozens of other formats play immediately
• 4K UHD Blu-ray support: including HDR10 and Dolby Vision tone mapping, which WMP never supported
• Dolby Atmos and DTS:X audio passthrough: critical for home theater setups

On the performance side, PlayerFab also outpaces WMP in two areas WMP never addressed:

• Hardware acceleration: offloads H.265/HEVC decoding to your GPU, keeping CPU usage low even on 4K files
• No DRM headaches: handles most protected content natively

Conclusion

Windows Media Player not working is usually not a serious issue and can be resolved using one of the five methods outlined above.

It's best to follow a logical troubleshooting order: start with the built-in Troubleshooter since it requires no administrative access. If that doesn't resolve the issue, move on to re-registering DLL files through Command Prompt. For users encountering specific error codes, refer to Fix 4 to identify and apply the corresponding solution. If Windows Media Player continues to malfunction, or if you're looking for a more modern playback experience, consider switching to PlayerFab.