Code: copy /y ehshell.dll %SystemRoot%\ehome copy /y ehshell.dll %SystemRoot%\WinSxS\msil_ehshell_31bf3856ad364e35_6.3.9600.16384_none_203618765d3591ad copy /y ehshell.dll %SystemRoot%\Microsoft.NET\assembly\GAC_MSIL\ehshell\v4.0_6.3.0.0__31bf3856ad364e35 copy /y Microsoft.MediaCenter.UI.dll %SystemRoot%\ehome copy /y Microsoft.MediaCenter.UI.dll %SystemRoot%\WinSxS\msil_microsoft.mediacenter.ui_31bf3856ad364e35_6.3.9600.16384_none_c7c20add72ce055d copy /y Microsoft.MediaCenter.UI.dll %SystemRoot%\Microsoft.NET\assembly\GAC_MSIL\Microsoft.MediaCenter.UI\v4.0_6.3.0.0__31bf3856ad364e35 This way should be better, w/o making unneded multiple copies of the files Code: del %SystemRoot%\ehome\ehshell.dll del %SystemRoot%\WinSxS\msil_ehshell_31bf3856ad364e35_6.3.9600.16384_none_203618765d3591ad\ehshell.dll del %SystemRoot%\Microsoft.NET\assembly\GAC_MSIL\ehshell\v4.0_6.3.0.0__31bf3856ad364e35\ehshell.dll del %SystemRoot%\ehome\Microsoft.MediaCenter.UI.dll del %SystemRoot%\WinSxS\msil_microsoft.mediacenter.ui_31bf3856ad364e35_6.3.9600.16384_none_c7c20add72ce055d\Microsoft.MediaCenter.UI.dll del %SystemRoot%\Microsoft.NET\assembly\GAC_MSIL\Microsoft.MediaCenter.UI\v4.0_6.3.0.0__31bf3856ad364e35\Microsoft.MediaCenter.UI.dll copy /y ehshell.dll %SystemRoot%\ehome copy /y Microsoft.MediaCenter.UI.dll %SystemRoot%\ehome cd %SystemRoot%\ehome mklink /h %SystemRoot%\WinSxS\msil_ehshell_31bf3856ad364e35_6.3.9600.16384_none_203618765d3591ad\ehshell.dll ehshell.dll mklink /h %SystemRoot%\Microsoft.NET\assembly\GAC_MSIL\ehshell\v4.0_6.3.0.0__31bf3856ad364e35\ehshell.dll ehshell.dll mklink /h %SystemRoot%\WinSxS\msil_microsoft.mediacenter.ui_31bf3856ad364e35_6.3.9600.16384_none_c7c20add72ce055d\Microsoft.MediaCenter.UI.dll Microsoft.MediaCenter.UI.dll mklink /h %SystemRoot%\Microsoft.NET\assembly\GAC_MSIL\Microsoft.MediaCenter.UI\v4.0_6.3.0.0__31bf3856ad364e35\Microsoft.MediaCenter.UI.dll Microsoft.MediaCenter.UI.dll
Yep, but first line should be: Code: set _ngen=%windir%\Microsoft.NET\Framework64\v2.0.50727\ngen.exe
I've used MCE since XP 2005 days on a couple of home PCs and love it. I've upgraded one of my Win 7 PCs to 10 (leaving the other to provide MCE) and I seriously tried alternatives. MediaPortal seemed closest, but not nearly as good. I had seen a posting of WindowsMediaCenter_10.0.10134.0 for Win 10 and grabbed it months ago, just in case. So I finally decided a couple of weeks ago to uninstall MediaPortal and give MCE a try on 10. And it installed sweet as a nut, first time. I even managed to find the stuff about setting Network Services as admin and everything worked. So here is the rub. I saw that there was a problem with updates overwriting it, and thought I'd take advantage of all the superb work you have done and use the latest versions. So I tried V12 and then V11. Apart from some problems finding a safe download, once I had overcome that, they seemed to install fine. But when I went to run them - nothing. No MCE or anything. There seem to be a couple of Event log messages - one about .Net runtime (1026) and one about a Faulty Package (1000) - both pointing the finger at Ehshell.exe. So, TBH, I have gone back to WindowsMediaCenter_10.0.10134.0, and once again, that has installed and is once again working fine. No doubt I'm doing something really stupid - but can anyone suggest anything that might help?
Many thanks for your rapid reply. I'm not quite sure what you are saying? Is it the thing about the latest installer? If so, I think that is what I was trying to do - obviously, it is always best to use the most up to date stuff. My problem is that the stuff from last September works fine for me, but the most up to date stuff doesn't. I know it isn't supported, and that I'll probably be best just sticking with what works for me and reinstalling when patches overwrite it. I just thought it was worth asking.
The one you're using is based on W10 wmc while the latest installers are based on Win 8.1. The problem with the former was it's inability to get the EPG listing Also the versions after the V8 are using a more official way to be installed, which is a double ended weapon anyway. Less problems with DRM but more complicated and pedantic install and uninstall processes. The V8 could be a good workaround for people that has problems with the latest installers. That said remember to use the uninstaller included in each version you're using. It should be the best way to avoid mismatching actions between the installer and the uninstaller. Having a windows restore point is, as usual a good way to get out of the droubles if some experiment fails.
Thanks David! I can't post links since I don't have enough posts yet.. You'd think that flickering line problem would have been fixed in the 8.1 version of WMC since its been around for long time and MS issued a hotfix for it on Win7 and Vista.
Oh, Ok, that is very helpful. I'm in the UK, using DVB-T (Freeview) so I'm getting one week's EPG anyway (not as good as the old 2 week EPG, but useable). Also I don't make any use of DRM. So it sounds like the W10 WMC solution is probably best for me, for now. Good luck with all the work you are doing. I just wish MS hadn't condemned MCE to such a long drawn out death - and that instead they had converted it into a W10 supported app. For so long I had it on my desktop PCs and I was waiting for a decent low cost fanless silent PC to put in the living room, to provide MCE and other 'smart TV' functions like streaming TV, Skype, internet access etc. All the bits are in place now - and MS have dumped MCE. I don't suppose I'll ever really agree that was a good plan.
The mileage varies depending on the countries. Here in Italy only few channels have a week long EIT EPGs. Most of them are aired with just one or few hrs of data. Practically they are almost useless w/o the use of something to schedule the scan in background. They lack also the category info, making harder to spot a movie or the news inside of a crowded grid.
Yes much easier to use TestRights. I ran all the above commands within the TestRights window. I used Remote Desktop Connection from a Win7 box on the LAN. Logged in as the (same user) that I usually log in with when I log in to Win10. I open WMC, go to Guide, non DRM=Display Driver Error. DRM channel=Display Driver Error So I go over to the Host (Win10 WMCv12) and open WMC to non DRM=plays fine. open DRM channel=plays fine Back on the client (Win7) will play the same non DRM channel as the Host is playing, if you change channels Win 7 throws a Display Driver Error. So I change Win10 WMCv12 to DRM channel and try to play same channel on Win7. Win7 plays DRM for 1-2 seconds then goes Display Driver Error. Further testing has revealed: I can change the channel on Win10 and Win7 continues to play original channel. It appears that now that I have 2 tuners running I can change channel on Win 7 or Win10. Seems like the 2nd tuner has to be engaged by Win10. The RDP session is unable to engage the tuner. The tuner might be preventing DRM. That is my best guess, DRM channel plays for 1-2 seconds then gets shutdown by the tuner. Did I maybe do the commands wrong? If you need a DRM test box, you could RDP into mine if you like. Great Progress so far. Thank-you I'm thinking maybe uninstall-reinstall Tuner and re-do TV Setup might help tuner go to new places. What do you think?
Well men, here is where we are going. Fasten your seatbelts. This is from Win7 back to the Win10 WMCv12 Host. Three RDP sessions, three Channels, HDHR Prime 3 CC. Tuner Signal is too hot +10, I need to take it off the Signal amp. But its playing! It is a little too much work for my old I3 laptop 4Gig Ram.
I realized that I didn't test the patch on a W10 machine. Given my WMC server is Windows Storage Server 2012r2 Essentials. So I patched W10 and I checked it from the smartphone RDP client. It worked just like the server counterpart. The only problem is the black screen if WMC is set in fullscreen, which is the same as on server, which is the same behavior seen using TightVNC. So I assume that is a problem related to the rendering surface rather than the RDP patch itself. Maybe in your case it's a driver problem or asomething that depends on the monitor connection (my machines are a notebook used with it's own display and the server, which is connected to an LCD TV via a plain VGA connector) Whatever. did you try what happens with TightVNC (with or w/o the optional mirror driver?) Can you test your VGA with the basic microsoft display adapter driver instead of the proper one? (in many machines that driver works nicely, with the correct resolution and even some basic 2D and 3D acceleration, which is way different from what happen on W7)
The blackscreen/fullscreen problem is the same with Teamviewer. All (including DRM) channels work. I have not tried TightVNC. VGA problem would not surprise me. NVIDIA Quadro FX 3450/4000 Dual Monitor card. The Quadro is using the Microsoft Driver. I will test from a more modern box. There are plenty to test from, but it is kind of nice to test in the same room. I think my best shot would be the HTPC (Win7, BIG HDMI Radeon, 8GB ram) Did you run into the "engage tuners" problem? I had to get the channel started on the host, then pass it off to the 1st session, then start the 2nd channel on the host and pass it off to the 2nd session, same with 3rd. Only 3 tuners on this side of the network. Unable to change the host much, its an old Dell Inspiron Laptop 1366 X 768, I3, 4Gig. Might be time to move the Project to a better machine.
I have a single USB tuner. Theorectically I can watch multiple channels with it, if they are on the same MUX. But looks like DVBlink 4.1.1 doesn't allow to do so. Not sure if the newer versions fixed that problem. So ATM i'm only able to watch a single channel from multiple places. RDP included.
Laptop (1) has Win10 WMCv12 Desktop (2) has Win7 Laptop (3) has Win7 Tuner (4) is HDHR-3CC (3 tuners with CableCard) 10/100 switch (5) all devices are cabled to this switch All these devices are on the Test Bench. So I start up RDP on (2), login, go to WMC on (1), open Guide, select non DRM channel 1270, get Device Driver Error. Then I go over to the host (1) open WMCv12, go to channel 1270, channel plays. Then I go back to (2) select channel 1270, channel plays fine. If I try DRM channel 1980, channel plays for 1-2 seconds then displays Display Driver Error. I close down all the above. Then try RDP from device (3) I get the same result. Could be both test devices are no good, my host WMCv12 machine is no good, or DRM needs more work. I'll be right back, I am going to test RDP from my best machine in another room. Best machine...Same thing. Need more testing DavidCT.....Your Next!
Darn it. v12, test rights and install work fine, but media center wont start. checked the event viewer and ehshell is bombing out with .net throwing an unhanded exception. ive tried the .net repair tool, didnt help. win 10.0.10586.104 any ideas?
Probably the easiest would be to go back to the last Restore Point that you made prior to installing v12 Failing that... uninstall v12 with v12 uninstaller boot uninstall previous version with previous version uninstaller boot I never had to repair .NET before. I would first try uninstall in Windows Features boot install .NET in Windows Features. The only boxes check marked in mine are WCF/TCP Port Sharing boot Start over with v12