This issue is still not resolved. I would appreciate a follow-up. Dropping a canned cut & paste response, then never coming back to check whether it worked or not is unprofessional at best. It would be nice to be able to use the software I paid for. It's a shame when FREEWARE works better, is more reliable, and has superior tech support.
Windows Media Player - Intermittent error when trying to play media file-Server Execution Failed
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.
Windows for home | Previous Windows versions | Music, photos, and video
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.
131 answers
Sort by: Oldest
-
Anonymous
2009-12-31T21:12:59+00:00 -
Anonymous
2010-01-02T15:33:50+00:00 Bump!
-
Anonymous
2010-01-05T13:32:16+00:00 STILL no response from Microsoft. BUMP.
-
Anonymous
2010-01-05T17:02:28+00:00 I have got the same problem with "The server {ED1D0FDF-4414-470A-A56D-CFB68623FC58} did not register with DCOM within the required timeout." on my Windows 7 Pro x64. I get it mostly with WMP Classic on both x86 and x64 versions of the player. It does not happen very often but I have got quite a few corrupted MP3 and video files because of that I guess. I am clueless how to solve the error. The possible errors could be also due to things that are installed on my computer:
- Outpost Firewall installed
- K-Lite Codec Pack (Standard)
- Media Player Classic x64 or/and x86
The problem is that if I try to play the file after I get the message of server execution errors, the computer becomes non-responsive and then hangs. I do not get any logs after that except for that I have presses the reset button The previous system shutdown at ... was unexpected. Again, it does not happen every time I play the files but I will try to experiment with it a little.
here is a qote from another post that looks similar to our problem:
[quote]
I had the same problem ...
I just opened the task manager and sow "IME" program not responding
end it by task manager
and everything goes alright
Windows 7 RTM 7600 x64
...
[/quote]
tridy (Stockholm, Sweden)
-
Anonymous
2010-01-05T18:12:01+00:00 If I had venture a guess, it would be that Microsoft is scared to answer. If they confirm that they do indeed have a problem that is corrupting files then they have a huge issue on their hands. If they stick their heads in the sand and refuse to answer, then the issue is partially defused. I find it ironic that this is supposed to be a "media friendly" operating system, and yet this is quite realistically the SECOND time in its very short life that they've had a file corruption issue (possibly the EXACT same corruption issue). Microsoft obviously doesn't know how to fix it, and they're deathly afraid to say so.
OR, they already got our money and now they don't care at all.
Either way looks like it's doubtful we get a straight answer or any tangible help.