This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Windows Media Player - Server Execution Failed
I'm currently running Windows 7 Ultimate, 64-bit version.
Just recently started receiving this error about 2 weeks ago. The first media file I open with WMP works fine. All subsequent media files, regardless of type, hangs for about a minute and a half then pops up an error.
Nice error box with a red X stop sign and then:
C:/path to the file I tried to run/name.extension of said file
"server execution failed"
Task manager shows WMP running in background, stopping the process does not help. Restarting explorer does not help either. Full shutdown/restart just restarts the cycle. First file works, then the rest don't. No time issues either, I can launch it, play songs all day, change songs at random, etc.. If I close it, then try to restart, I get the error. Does not matter how long I wait between closing and restarting. Does not matter what file is opened.
This error is in the event log at times corresponding to my "server execution errors"
The server {ED1D0FDF-4414-470A-A56D-CFB68623FC58} did not register with DCOM within the required timeout.
Also tried:
Control Panel, Programs, Turn Windows Features On/Off and disabled WMC and WMP.
Rebooted.
Went back, re-enabled both programs.
Rebooted.
Worked for about 10 minutes, then started back with the same error.
I have also tried all of the suggestions available here: http://www.thewindowsclub.com/troubleshooting-windows-media-player-in-windows-7 with no result.
I've ran 7 since the beta was first available and had zero issues with this. I did a clean install of the retail version when it released, and had no issues until now. I have not installed anything other than Windows Updates. Computer is clean, I've ran multiple malware/spyware scans and antivirus scans.
I've also tried the system file checker (SFC), which found nothing.
It's also interesting to note, Windows Media Player Classic works flawlessly.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Diggers,
Have you attempted the clean boot suggested by others? If you are not experiencing MP3 corruptions, your problem might not be related to zcd7s.
"Server Execution Failed" is too common an error message to have a single cause, so we need a little more information.
Bump
See my post:-
Addendum, the files do not get corrupted but once laptop restarted they will execute and play the MP3 fine.
The files run fine on my older XP SP2 laptop without crashing at all.
Regards
Diggers
Bump
Bump!
This started happening on a clean installation of 7, only thing running at the time was Komodo (ZA didn't have a version for 7 at release, and Windows firewall is not a true firewall despite what MS insinuates) and Avast (which I've used both personally, and sold to my customers for years with absolutely no problems. Works way better than the bloatware that Symantec, Mcafee, or Trend put out, and it doesn't spy on you... *cough Norton's cough*.) I disabled both at the time and had no change in symptoms. I only downloaded the K-Lite and Winamp programs AFTER WMP started eating my MP3's, so I could continue to listen to music while Microshaft is busy ignoring the problem. WMP will play the file, then eventually it will corrupt it. Winamp and Classic will still play it fine. WMP will not play that file again period, regardless of library rebuilds, uninstallations, holding my mouth just right, and everything else MS has repetitiously suggested. The only way to get the file to play again in WMP is to replace it with a known working backup.
As best I can tell, the symptoms seem to fit the problem MS claims they fixed back in the beta. Would be nice if MS would actually respond to this thread with something other than a cut and paste BS answer with the intent to stall until I go away. Heck, I'd even settle for timely responses instead of this once a month BS. Maybe if they actually cared/tried we could drill down and actually resolve this issue. But then again, why would they care, they already got our money........
