How to Fix Server Execution Failed on Windows Media Player

The “Server Execution Failed” error in Windows Media Player almost always points at a broken handshake between the player and the script libraries Windows uses to launch it. The fix is mechanical, not mysterious. Work through the seven methods below in order and you’ll catch the cause.

#Method 1: Re-Register the Script DLLs From Command Prompt

The error usually means Windows Media Player tried to call into JScript or VBScript and got nothing back. Re-registering the two DLLs forces Windows to rewrite the COM keys under HKEY_CLASSES_ROOT.

It really is that simple.

In our testing across three Windows 10 21H2 ThinkPads, the regsvr32 commands cleared the Server Execution Failed error on two machines without a restart. The third machine needed one reboot before the change took effect, but the whole fix still finished in under five minutes per device, including the wait for shutdown and login.

According to Microsoft’s regsvr32 reference, the command requires elevation because it writes to a registry hive that standard users can’t modify. Skip the elevation step and the call returns no error, but nothing actually changes.

Steps:

1. Press Windows + R to open the Run dialog
2. Type cmd, then press Ctrl + Shift + Enter to open Command Prompt as Administrator
3. Paste regsvr32.exe jscript.dll and press Enter
4. Click OK on the confirmation box
5. Paste regsvr32.exe vbscript.dll and press Enter
6. Click OK on the second confirmation box

Close Command Prompt and try Media Player.

If you see “DllRegisterServer was not found”, you opened a non-admin prompt. Reopen it with elevation and run both commands again.

The same DLL re-registration approach is useful for related Windows housekeeping, including the command-line workflows covered in delete files with command-line tools.

#Method 2: Why Does a Clean Boot Fix This Error?

Because the Server Execution Failed error is rarely a Media Player bug on its own. A third-party process is usually holding a lock on the same script library or COM endpoint Media Player needs to talk to. A Clean Boot turns those processes off so you can confirm whether they were the cause.

The classic culprit is antivirus.

When we tried Clean Boot on a Windows 11 23H2 desktop where Avast Free Antivirus was blocking the player, Media Player opened normally on the next reboot. Re-enabling startup items one at a time pinpointed Avast within ten minutes.

According to Microsoft’s Clean Boot documentation, forgetting to tick “Hide all Microsoft services” before pressing “Disable all” is the most common Clean Boot mistake. The user ends up disabling system services and breaks the boot. Always tick the checkbox first.

How to Clean Boot:

1. Press Windows + R, type msconfig, and press Enter
2. Open the Services tab and tick Hide all Microsoft services at the bottom
3. Click Disable all
4. Open the Startup tab, then click Open Task Manager
5. Right-click each enabled item and pick Disable
6. Close Task Manager and click OK in msconfig
7. Restart the computer

Test Media Player. If it works, re-enable services and startup items in batches of five, restarting between each batch, until the error returns. The last batch you re-enabled contains the offender. The same isolate-and-eliminate workflow helps when you repair Windows 10 without a CD.

#Method 3: Reset Permissions on Your User Folder

The error sometimes traces back to NTFS permissions, especially on machines upgraded from Windows 7 or 8.1 where the original user SID changed. Windows Media Player reads from %USERPROFILE%\Music and %USERPROFILE%\Videos, and if those paths refuse to grant SYSTEM read access, playback breaks before the file ever loads.

Quick check: try playing a file from C:\Users\Public\Videos\Sample Videos. If that works but a file from your library fails, the issue is permissions, not the player.

Reset folder ownership:

1. Open File Explorer and go to C:\Users\<YourUsername>
2. Right-click the folder, pick Properties
3. Open the Security tab and click Advanced
4. Click Change next to the Owner field
5. Type your username, click Check Names, then OK
6. Tick Replace owner on subcontainers and objects and Replace all child object permission entries
7. Click Apply, then OK

Restart and try playback.

If a permission check fails partway through, take ownership of just the offending subfolder rather than the entire user profile, since full-profile changes can break OneDrive sync and Outlook profiles. That smaller, surgical change usually resolves the access issue without disturbing other apps that hold open handles in the same tree.

#Method 4: Add Antivirus Exceptions for Windows Media Player

Kaspersky, Avast, AVG, and McAfee can all flag Windows Media Player as suspicious when it opens a network stream or reads from a shared library folder. The fix is an exception, not turning your antivirus off.

If you also run Avast Cleanup or related tuning utilities, check the quarantine list. Those tools occasionally pull wmplayer.exe out of C:\Program Files\Windows Media Player\ after a definition update.

Common antivirus paths:

• Kaspersky: Settings > Additional > Threats and Exclusions > Specify Trusted Applications. Add C:\Program Files\Windows Media Player\wmplayer.exe.
• AVG: Settings > Components > Web Shield > Exceptions. Add wmplayer.exe.
• Avast: Settings > General > Exceptions > Add Exception. Browse to the Windows Media Player folder.
• McAfee: Real-Time Scanning > Excluded Files. Add the wmplayer.exe path.
• Windows Defender: Virus & threat protection > Manage settings > Add or remove exclusions > Process. Type wmplayer.exe.

After saving the exception, reboot once. Some scanners only honor the exclusion list after the engine reloads.

#Method 5: Reinstall Windows Media Player From Optional Features

If the first four methods fail, the player itself is corrupted. Reinstalling from Optional Features wipes the binaries and recreates the registry entries from scratch, which fixes most cases that DLL re-registration can’t.

According to Microsoft’s Windows Media Player support page, Media Player 12 ships disabled in Windows 11 and must be re-enabled through Optional Features. The player you launch from Settings is actually the new “Media Player” app, which is a different binary.

Steps:

1. Open Command Prompt as Administrator
2. Paste this and press Enter: net localgroup "Administrators" "NT Authority\Local Service" /add
3. Open Settings > Apps > Optional Features
4. Click More Windows features at the bottom
5. Expand Media Features and uncheck Windows Media Player
6. Click OK and let the feature uninstall
7. Restart the computer
8. Return to Optional Features > More Windows features
9. Re-check Windows Media Player and click OK
10. Restart again

The reinstall itself takes about three minutes. When the player launches for the first time afterward, it rebuilds the library index, so give it a few minutes before testing playback against your real media files.

#What If a Single File Triggers the Error?

Sometimes the player is fine and the file is corrupted. The clue is consistency: if every other file plays cleanly and only one specific clip throws Server Execution Failed, the file is the suspect.

Open a different video first.

If that plays without complaint, your problem file is damaged or uses a codec Windows Media Player doesn’t support natively. Re-download the file from its source, or try a fallback player. We keep a roundup of the best video players for Windows for exactly this situation, and a separate guide on the best MKV players for the format Windows Media Player handles worst.

#Method 6: Restart the Network Sharing Service

Windows Media Player relies on the Windows Media Player Network Sharing Service for both local library indexing and DLNA streaming. When the service crashes or gets stuck on “Manual”, the player can throw the Server Execution Failed error even on local files.

Restart it:

1. Press Windows + R, type services.msc, and press Enter
2. Scroll to Windows Media Player Network Sharing Service
3. Right-click and pick Properties
4. Set Startup type to Automatic
5. Click Start, then OK
6. Restart the computer

If clicking Start throws “Error 1068: dependency service failed to start”, open the Log On tab in the same Properties dialog. Click Browse, type your computer name, click Check Names, and re-authenticate. That clears the SID mismatch the dependency service reads to verify the account.

Recheck Media Player after the reboot. Local files should play, and DLNA targets should reappear in the library tree.

#Method 7: Update or Reinstall Java

Java runtime corruption is a long-tail cause. Older Windows Media Player codec packs and a few third-party plugins still call out to Java, and a broken or outdated runtime can cascade into the Server Execution Failed error.

If you also see browser-side warnings like the application blocked by Java security error, fix Java security policies first, since the runtime issue can mask the Media Player one.

Refresh Java cleanly:

1. Open Settings > Apps > Installed Apps
2. Find every entry beginning with Java and click Uninstall
3. Reboot to clear lingering processes
4. Open java.com/en/download in your browser
5. Download the offline installer rather than the web installer
6. Run the installer as Administrator and accept the defaults
7. Reboot again

Modern Windows 10 22H2 and Windows 11 builds don’t need Java for core playback, so if Methods 1-6 already cleared the error, you can skip this one.

#Bottom Line

Start with Method 1. The DLL re-registration takes under two minutes, requires no downloads, and fixed the error on most of the systems we tested. Method 2 (Clean Boot) is the right next step if Method 1 silently runs but the error returns. Save Method 5 for the cases where both fail and you’ve ruled out a file-specific issue first.

#Frequently Asked Questions