Graznok, I keep backups and I had a patched one with the 2 fixes (volume and display res) and it worked with Extenders. So tonight I figured I would try your patch again as it was not working on my current install for some reason. So I restored the one with the patch.... I tested it, the volume and res check is working as it should, I was able to connect to the Extender fine. I extracted WMC7601x64-RDP-patch-V2.7z, I added the 2 patches (volume and display res) and your updated RDP patch. I ran the script and WMC ran fine. I connected via RDP, Recorded TV played fine but, live TV would go to "Display error". After this, I poped out of RDP, ran WMC on the computer, then I went into the other room to try the EXTENDER..... Same problem as alone with the RDP patch, it shows connecting (downloading from the PC) and it just times out trying to connect. This patch didn't work for the Extender....
Thanks, now I remember how they got the Echo almost working. Somebody just told me about this a couple months ago. What I heard they did was upgrade a completely configured (with extenders) Win7, to Win8 or 8.1. I have tried this on Win10 (one time). Win10 deleted all/most of the configuration, with the exception of the MCX account's. I totally missed Win8/8.1 (2013-2014). I was busy figuring out how to build a network...wire, router, switch, server, etc.
After update to Windows 10 Pro 14271, and clean install of this WMC patch, Windows Media Center will not start.
It is too complicated to solve this issue at the moment, because there are globally two solutions: Make Media Center to think that all sessions (local and remote, eg. Extender) are local ones in order to get DirectX rendering and video playback, and suppress every remote session unit test, but this is likely making Extender connections to crash. Keep remote session in order to get Extender working as expected but force video playback, either under GDI rendering (but in that case video isn't played at all) or by enabling DirectX while session is remoted.
So, let me understand. After over 1.000.000 (one million) of unique accesses, we have the pleasure to get the attention of a new users at his 5th message?. I think you should ask something yourself before asking here.
Maybe you simply don't know what your talking about... Try to use JRMC or KODY for TV services, and look at how simple they are...
I guess the main reason is....WMC plays and records DRM channels. You are not going to collect many "likes" in this thread with the "rubbish" statement.
DirectX over RDP would be awesome. So I can play Media Center back and when I get sick of watching TV, I could start up a game of Call of dudy as well I'll have to admit, that would be really cool, not just for Media Center...lol This issue was resolved. Interesting find. The app came with it's own "RegisterMCEapp.exe" that it installs in Program files, so what I did was install it, let it fail, Checked the Reg file (the batch file was in the installed directory) and saw where it was calling to "RegisterMCEapp.exe" in the folder, I changed the script around to use %Systemroot%\ehome\RegisterMCEapp.exe This app installed with out a problem on a unmodded machine...odd.. After running it, it installed fine and works in a modded WMC....This was with Revision3 app that still works and pulls down current data/videos that play back in WMC... Just a fyi to anyone running into this problem. Media Center studio fails to run but, I moved over to Media Center themer so I should be able to drop that app for good. So far, I tried 3 native WMC apps and they seem to all install fine. More testing to come but, over all, it's fixed.
With a clean Windows 10 install, use ver 12 and with an upgrade use ver 11. Been working perfect for me.
Just uninstalled ver 11 (because I had the EPG processing error) and installed ver 12 on a fresh Windows 10 Enterprise x64. Now everything works fine but every time I run WMC I get the following warning (see image below): EhTray.exe The publisher could not be verified. Are you sure you want to run this software? And even if I uncheck the "Always ask before opening this file" option, it keeps coming back. Any idea how to get rid of it? I tried to search the thread but I couldn't find any reference to this problem.
This regedit will get rid of all those low risk file type notifications Code: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Associations] "LowRiskFileTypes"=".zip;.rar;.nfo;.txt;.exe;.bat;.com;.cmd;.reg;.msi;.htm;.html;.gif;.bmp;.jpg;.avi;.mpg;.mpeg;.mov;.mp3;.m3u;.wav;" "DefaultFileTypeRisk"=dword:00001808
Well, this solution seems a little too extreme; anyway I can exclude only ehtray.exe and not every possible executable? Wondering why in ver 11 was working just fine. What changed in ver 12?