Firstly I would like to thank all those who have contributed to providing this solution. I did manage to successfully install and get running version 11 of the fix and use it with a HDHomeRun HDHR4-2DT. It works with both SD TV using MPEG2 and HD broadcasts using H.264. I did however find that HD broadcasts were breaking up on all HD channels although only slightly. At this point I don't know for sure if this was a signal strength, codec, or video GPU related problem. I so far have been having problems trying to uninstall 11 and then install version 12 of this fix. I will have another go tonight. It allegedly uninstalls but version 12 still thinks 11 is installed and fails. However other than giving thanks my main reason for posting here is as follows. I can see that version 11 (and presumably 12) are based on the WMC from Windows 8.1. Is there any technical advantage to using that rather than WMC from Windows 7? Is there a version of this fix based on WMC from Windows 7? One issue that might relate to the above is that I am finding that Guide Tool from this site http // 1geek1tool.com/guidetool/ is consistently crashing when I attempt to launch it. The matching WMC component also causes WMC to complain that it is not compatible and indeed the Guide Tool site only mentions support for Vista and Windows 7. Has anyone else had better luck getting Guide Tool working in Win10? I find Guide Tool to be pretty much essential because Microsoft do not list many channels in the official EPG for in my case DVB-T/T2 in the UK but many of the channels are listed on for example Sky DVB-S/S2 also in the UK. I have therefore been using Guide Tool to trick WMC to using multiple EPG entries to fill in the blanks. On a totally different topic, since the creators of this fix have shown their incredible resourcefulness in extracting WMC from one version of Windows and getting it working in Win 10, would they be able to accomplish something similar in the reverse direction? What I am referring to here is the fact that Windows 10 includes as standard official Media Foundation codecs for amongst other MKV and AAC and Apple Lossless files. For older versions of Windows Apple Lossless in particular is only possible via a DirectShow filter based on an approach I originally devised and was written by Milenko Mitrovic. (This is the solution built-in to the Shark007 codec pack.) It would be much appreciated if someone could 'extract' the new Media Foundation codecs from Win10 and provide a way to install them in Windows 7 and 8.
For Windows 7 x64 ehshell.dll 6.1.7601.19061 ? Just make this mod to a current file (in use un-modded) or download the RDP patched one and do this mod to it ? (AKA, do your RDP patch on the current file and add this to the current RDP patch). Let me know and I'll try to do some testing tonight... I am on 100% Stock Windows 7 x64 right now.. As always thanks
There would not really be a big advantage for using a Windows 7 version of Windows Media Center. The parts removed from 8.1 was "Start WMC when the computer starts" and "Always on top" both can be added via the registry. Same on Windows 10 install. The BIG thing for a lot of people that was broken in the 8.1 version was 3rd party Extenders (Ceton Echo, etc), this is not a WMC problem, it's a RDP upgrade problem. So even if you were to put the Windows 7 version of WMC on Windows 10, it would not resolve the extender issue. 3rd party extenders are based on a modded verson of RDP. The ONLY Extender that works fully under Windows 8.1 is the Xbox 360. That is a questionable point on the Windows 10 version as there has been problems keeping it connected. All in all, there really is no really good reason to go through patching the 7 version to put on Windows 10... Ok, I'll try to test tonight if I can get my cablecard issue fixed (Cablecard died last night, need to pick up another one from my cable company)
Just to be clear on this latest development. My setup currently:- I have installed on my fresh Windows 10 Deskop (the one with the tuner cards in) the Version 12.7 Installer of Media Center + Ran Graznok's RDP patch to allow me to alter TV settings I wouldnt normally be able to and view video while on an RDP session to my Windows 10 Desktop from say my Windows 10 Laptop. And its all proved working ok via that setup for the past week. So to sumarise the story so far:- If i now open the ehshell.dll file contained in that RDP patch in a hex code editor and swap the top line of Hex at address 0x182112 for the bottom. Re save the dll file and re run the RDP patch installer because i can't just take ownership of the ehshell.exe file and swap in the new one as the new file won't work as it exists in some other locations and because some special systems files needs special injection for windows to run it using some .net framework ngen command or other clever stuff contained in the patch installer that is above my pay grade. After that i should be able to for the first time try pairing one of my xbox 360 extenders and find it pairs correctly (haven't tried so far) and it will hold a connection without dropping as I've been hearing drops have been happening for those trying so far. This without using any special terminal service dll tweak or terminal services wrapper thingy being requiired. And will NOT kick me off the console session of the desktop if i'm sat in front of it when my extender connects. I'm assuming this is for 6.3.9600.16384 dll? So i can find the Hex Code string? Just trying to clear up the confusion for us lesser mortals Best Regards to the Mightt Graznok!!!! Gareth
Previous patch is for 6.1.7601.19061 ehshell.dll. Here is the one for 6.3.9600.16384 x64: Code: 0x184bea 28 3E 63 00 06 2D 16 00 00 00 00 2C Please note that you must apply this mod over the RDP-patched file, and that I totally don't know if it works.
Now if we can get WMC to run over RDP, now if we could only get it to run full screen over RDP....As I tried the other day over RDP from my HTPC, I opned a video in media player (just a movie file, not a WTV), I was able to expand it full screen and video was perfectly smooth but, it got a hair choppy when it was in a window... Any modes we could force to get WMC to run in full screen over RDP ? We can run WMC in full screen with out the patch but, no video will play back Looking forward to testing this updated patch...
I had to disable my laptop screen for the laptop to join the Matrix. I was unable to run both screens at the same time, while WMC was running.
In theory, that is what is supposed to happen. In actuality, this is a test. You might want to make an image of what you have now, prior to each test. Particularly if you are testing on your production machine. Another thing that is working right now is.....port forward your WMCv12 through your router to your external IP XX.XXX.XXX.XXX:3389 TCP and use port 3389 Install Microsoft Remote Desktop 8.1.28.2 (this one is for Androids) Open WMC and watch tv on your phone, or from the other side of the planet.
Hi All, Looks like I'm failing at the first hurdle on this. I can't even get one of my xbox 360 extenders to pass the pairing stage. Currently running fresh Windows 10 Desktop build + the Version 12.7 Installer of Media Center + Graznok's RDP patch and confirmed RDP patch working a week ago by RDPing using another a laptop into my main Desktop (no more warnings). Never paired an extender before on Windows 10 prior. Altered the hex code for my already patched 6.3.9600.16384 x64 ehres.dll as Grasnok explained in post #3791. Ran the patch installer rebooted. Tried pairing one of my xbox 360 consoles and it fails at stage 2 Searching for your extender. Error "Configuration Error. An error was encountered while configuring your computer for use with this Extender." Turned my firewall off also altered RDP ports as meluvalli Said on previous post here:- "So, to get it to work/connect, I had to do a few weird things.... First thing was to change port for EH-TCP to any other port other than 3390 (Default).... Then I changed RDP Port (Located in Registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp to port 3390 so Extender would try to connect through regular RDP..." Same thing. I'm mindfull also of what was said On Post 3716 DvidinCT said:- For anyone trying/using the RDP patch, After the RDP patch, Xbox 360 extenders on Windows 7 will no longer connect. So, if your playing with the RDP patch on Windows 10 and are trying to get Extenders to work, it will fail. Maybe I should of started with my ehshell.exe as default. Tried to pair an xbox having altered the RDP ports as meluvalli said then confirmed my extender connected and took over from my console session on my desktop and then prompty disconnected after 5 mins (which i think has been the previously observed sequence). Then bypassed the rdp patch and tried this latest one see if it holds connection. Then go for the RDP patch on top? Only had a small window to test before all my crew got home and i had to revert to the default hdd with windows 8 on and everything working before i got moaned at by everyone I Have an Acronis image of everything prior to changes and will swap test to destruction on this but interested to hear peoples thoughts before my next try tomorrow. Best Regards Gareth
there is some Xbox software to install. Looking glass or "something glass" that was used in win8. I would imagine it opens the correct firewall ports, sand does other things as well.
Not sure what you mean. I'm not trying to access my media centre from an android phone or windows 8. Just trying windows 10 + Extender. Do I need some other software to get this to work?
My RDP patch fools Media Center in the sense that it thinks that remote (non local) sessions are local sessions. Considering that, I would not be surprised if it fails when it tries to connect to an Extender.
Ported WMCv12 in Windows 10 Guide Tool runs fine. You might need to install .NET 2, 3, 3.5 in windows Features. MKV's play fine without doing anything other than placing the MKV in the C:\Users\Public\Videos folder. In my case Lav 64 bit might be helping.