[DISCUSSION] Patch WMC to run on Windows 10 final & possible alternatives

1) Does Remote Desktop Connection work? From one of your workstations to the Host? I had a little trouble with the patch, I had to edit my own files, and place them in the installers bin. Not sure if this makes a difference, but I have RDP wrapper 1.6 installed also.

2) When Xbox freezes while connecting, Do you get any error in Event Viewer?

 

Windows 10 Pro x64 build 10586 won't install these packages.

 

What "packages" are you talking about?

 

Yes. RDP Connection works, just not in full screen mode. And Yes, I am using RDP Wrapper as well.

No. Last thing in log is: The Media Center Extender session was established. Event ID 115. Again, the host machine things it's connected and logged in and running per Task Manager. Windows Media Center is running under the MCX user profile. Just XBox doesn't display anything and freezes. Note: When I say freezes, I don't mean the XBox completely freezes to the point you can't do anything... If on the Host Machine within task manager I "sign off" the MCX User, XBox disconnects from the host machine and is usable again.

Also, on a side note... Without the ehshell.dll patch, like I said before, XBox connects just fine, just can't watch videos. I have heard several people complain that if they get there's connected, it disconnects after 5 minutes or so... Mine was connected for over two hours without disconnect. Just FYI.

Also, just a thought... I wonder if we are going about the patch the wrong way? The patch, forces it to use the same graphics as if you were at the local machine.... Meaning for example... When you start Media Center, the Green Logo actually is animated with the patch when you start it with Remote Desktop and the patch.. However, normally it's not... I assume this means it's using the 3D graphics... Without the patch, you can load WMC in full screen no problem, but there's no 3D graphics... So, instead of patching it to "Always use 3D graphics", patch it to not care about RDP Connection for video play back...

Or even better yet... Default for Extender is to connect to port 3390... We are manipulating the system to "tricking" it to really use 3389... However, the problem with the original 3390 is, you get an error when you try to Remote Into that port saying there is No Remote Desktop License on the machine... Where is this License stored on a true WMC machine??? If we could get that license to "install" on Windows 10 machine, then this may actually solve all our problems because we would be using the RDP 5.2 that XBox Extender is designed for and may allow the video to play correctly.....

 

New Issue with XBox 360 Extender found....

So, without the ehshell.dll patch (again, xbox 360 doesn't connect with this patch), I also can't play any of my music files... It shows all my music in WMC, but if I select one to play it, it acts like it's playing it, but the timer stays at 0:00 long and it truly doesn't play... So, I tried this through a client machine remote desktoping into my WMC machine and it works fine.. So again, this is an Extender issue . All sound effects from WMC work through the XBox... So it's not like NO sound works. It's an issue with streaming the music files.

 

So xbox uses 3390. RDP uses 3389. Ceton Echo uses 3391 Win7 can run all these at the same time. I am curious to know what has been removed. It appears Win7 had some sort of carousel or router to plug in or forward all these various connections into WMC. Maybe Connection Manager?..... I suppose we should just concentrate on one at a time until we see a pattern. 3389 is working and your success is forwarding 3390 to 3389

What does your Wireshark or Fiddler look like? While xbox is trying to run.

 

I have zero interest in "likes" . My question was quite literal. Why does anyone still use this?

 

flag called on the play - tu quoqe , 1st down- away team

 

This is what I tried to do, without success for now.

 

You ask a question, you have answers. What else?

 

Net 2, 3, and 3.5

And thank you for your fast reply.

 

Hi,
.net Features are not included in the pack, you have to activate them in Windows 10 (Control Panel, add/remove features).

 

Two things came into my mind when i read your findings.

a) are we missing some ports the extender is needing ? i have attached a overview from the Links DMA 2100 extender
manual with an overview of all needed ports.



b) When its true this special RDP Connection to an extender is using some extra protocols for video/audio rendering outside
of the session and a set of specialized virtual channel extensions.

from https : // github. com/FreeRDP/FreeRDP/wiki/Windows-Media-Center


....Videos are not played using RDP’s Multimedia Redirection extension or RemoteFX. Instead, they are played using RTSP. Videos also appear to be transcoded on-the-fly by the Media Center such that the extender can play them.....


I also like your idea to find this terminal license and port it to W10.....

 

I tried downloading them and installing from Microsoft download. The installs failed. I will try using add/remove features but I don't recall seeing them listed there. Will follow up soon.

P.S. No NET Framework program is available in apps and feature or in optional features. The only optional features are fonts, graphics tools, and Insider Hub.

P.S. I want to reiterate that the guide itself works, but it refuses to download the show schedule so I can click on a show I like and set it to always record.

http: //s26. postimg .org/ 61smxy515/ guide.jpg

 

Ver 12 didn't work for me.

I had ver 11 installed on Windows 10 Enterprise 1511.10586.104 and mostly working except for two issues:

1. WMC returning errors while processing downloaded EPG data
2. A strange warning ID 414 in the Windows log about Task Scheduler service finding a misconfiguration in the NT TASK\Microsoft\Windows\Media Center\mcupdate_scheduled definition.

So I decided to give ver 12 a try:

1. Uninstalled ver 11
2. Restarted the computer
3. Downloaded ver 12 zip, and unblocked from the property dialog (otherwise I would get the ehtray.exe publisher could not be verified error dialog I posted at page 384 about)
4. Installed ver 12
5. The installer gave me a DISM error
6. Run uninstaller again and restarted the computer
7. Installed ver 12 again and this time it completed successfully
8. Restarted the computer one last time

Now everytime I run WMC, nothing happens. I click the WMC icon, I see the Windows circular hourglass mouse for a few seconds and that's it.

Any idea what's happening?

 

I could never get it to work with Enterprise, I use Pro and all is fine.

 

I remember my first computer

 

Riddle me this "Troll", If you don't like WMC, who cares ? If you like other options, AWSOME for you, Use those products and flame on those forums. WMC fits for other people fine for what it does. I am not going to "feed the troll" and say why this is better or that is worse. There is no point, if you like something use that and be done with it.

Please keep your thoughts to yourself, there is NO reason for you to flame people on their choices.

Everyone should just "report" his posts, there is not a really good reason to flood this thread with posts like this (even mine !)

 

Yes, posts like his do interrupt the creative process.

 

If a Certificate is considered to be a License, Media Center Extender Certificate for Win7 is stored in MMC/ConsoleRoot/

I was unable to find the same Certificate in Win10 with these instructions.

EDIT.....see 2nd pic.....I didn't look hard enough. The Certificate exists in Win10.

I wonder if someone used these instructions to reset all the MCX accounts, then installed the extenders after a fresh Certificate, would improve the operability of Xbox.