Just tried the above, and looks like the /dx9 switch alone is not enough to run WMC trough a RDP session. Maybe it works on a Remote FX session, but from my POV, unless one windows setup this way for other purposes, the effort isn't worth the result. An additional VGA dedicated to Remote FX on an server running h24 can raise the power consumption and the electrical bill in a perceivable way. Months ago I asked to the great Graznok (the author of the actual patches) to look to remove the checks for the RDP sessions. Those patches anyway didn't work for me, and surely had to be further investigated, that approach looks way more promising to me, but the drawback is that we need a "Graznok level" hex editing guru to accomplish the wanted result.
Not sure if this is what you mean, or if this is the result of the Great Graznok removing the checks you mention, but I have overcome the Multiple Remote Desktop Connections problem.
I'm talking about the checks that WMC does to understand if it's launched over an RDP connection. Allowing multiple RDP (to a client machine) is a problem solved since the "stone age" trough the terminal server patches and/or additional services/wrappers. I think MSMG has even the possibility to patch the service at the ISO/WIM level. Anyway that isn't even my personal problem given the machine where I run the WMC server role, is an actual windows server. So the multiple RDP connections are allowed natively.
Somewhat related to the Softsled concept, I am able to Teamviewer in and have a fully working WMC from anywhere LAN, WAN or 4G. Mr Graznok replied with the statement that Teamviewer uses a "Mirror Driver". Teamviewer installs a Service...in ProgramFiles(x86)
Oh those checks. I thought the RDPWrapper thing was old. Directions are everywhere. Ive been digging around everywhere trying to get a hardware extender working. Ceton Echo. Been learning some good stuff related to extenders (software and hardware). During every failed attempt.
Here is a twist for you. No Hookers tonight. I did not do the Graznok RDP HEX patch that you gave me. I set Win10 to sleep after 1 minute, then in advanced set for Hybrid Sleep. I go over to a Win 7 box, Use Remote Desktop Connection to Win10, try WMC live tv NO GO (I got the Video error). Recorded TV NO GO. (wont even try.. no error) So I try WMP. WMP plays Recorded TV. Not very well mind you, but it plays. I am going to try WMP Live next. Will edit post after test. Test continued... WMP plays Recorded and Live TV. No surprise DRM channels will not play in WMP with or without Remote Desktop. Could you try Hybrid sleep plus dx9? Can you tell me how to convince WMCv11 or v12 to use dx9?
Hi All, Something went completely wrong with my install and while it looks like installed fine, media center will not launch. Also running the uninstall script does not seem to remove all the files. how do I remove/unistall everything so that I can give it one more try? I'm using the v12 scripts. thanks elviso
According to the thread you posted just launch ehome.exe /dx9 trough a shortcut or command line. Not sure if it's effective on w10, anyway no error is returned, so it's likely working.
I had the same problem. I had to get the old eHome directory out of the way so that I could get a new install to go. I just opened a ADMIN command prompt and renamed \windows\eHome \windows\xxxeHome. then the installer worked
Try to launch the WMC recovery task. Usually WMC not starting means corrupted/invalid configuration files. The recovery tasks just cleans up them for you.
I restored the compilation of windows that has blocked wmc and everything returns to normal operation. Specifically is this: Upgrade to "Windows 10 Pro" version 1511, 10586. I disabled windows update temporarily until the issue is resolved.
Hi ... Thanks For V12..... But I uninstall v11 and reboot then install v12 ..... but have error ... what this is ? Prepare... Install DISM packages... Deployment Image Servicing and Management tool Version: 10.0.10586.0 Image Version: 10.0.10586.0 Processing 1 of 1 - Adding package Microsoft-Windows-MediaCenter-Package~31bf385 6ad364e35~amd64~~6.3.9600.16384 [==========================100.0%==========================] An error occurred - Microsoft-Windows-MediaCenter-Package Error: 0x800f0922 Error: 0x800f0922 DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log Installing package failed, reverting... You may reboot and try again refer to C:\Windows\Logs\CBS\CBS.log to find error details Press any key to exit.
Finally figured that out, it appears that the name of the dx9 file is d3d9.dll and name of the dx8 file is d3dhthk.dll Tried both, and like you say doesn't change anything, other than the navigation through the guide while using Remote Desktop is better with dx9 Might be interesting to find out what happens on 32 bit Win10, I see that d3d9.dll is considerably bigger (bigger=smarter?) in System32 compared to SysWow64 What amazes me is WMP plays non drm video very well in Remote Desktop, however WMC video is completely locked out. Somehow (don't remember how I did this) I ended up with a DTCP1 download of a drm channel. It was streaming to somewhere, but not to me. I was clicking and trying a bunch of UPnP stuff in WMP when it happened. My crystal ball says I have a week of reading in my future.
Well, clearly they did it on purpose to push the sale of the Xbox and the other extenders, now that business is practically gone, but the restriction stayed.