I don't know if this behaviour will be fixed by abbodi's new way integration, but I noticed that StartRecording scheduled task was never created by ehShed service on Windows 10 WMC pre-builds. It sounds like Network Service account cannot write in registry since Windows 10.
Sorry for the delay regarding dism-based package i'm just trying to find the best way yo handle it so far, it seems that we still need trustedinstaller rights and it's the best/cleaner way setacl.exe and powershell can do the job, but taking ownership caused some errors, specially when doing offline installation
*I fixed it - see end of post* I wasn't aware of that, but I'm not sure I want to go with that setup. I used procmon and found it was looking for ehRecObj\6.0.6000.0 in the Assembly folder in C:\Windows and C:\Window\Microsoft.Net. I also noticed it was checking in the Windows Server\Bin folder. I tried dropping the ehRecObj.dll from c:\Windows\ehome into that folder, but then it gives me an error that the assembly's manifest definition does not match the assembly reference. My GUESS as to what's going on... ehRecObj.dll in the downloaded package is 6.3.9600.16384 ehRecObj.dll on my Windows 7 machine is 6.1.7601.17514, and my Windows 7 machine looks for ehRecObj\6.1.0.0 in the Assembly folders. I *think* the Windows 10 machine should be looking for ehRecObj\6.3.0.0 I assume ehRecObj.dll with version 6.0.6* must be a Vista version number, and it's just defaulting to that because something is missing somewhere that tells it to look for 6.3.0.0. *This is the fix* So going off that, I found a corrupted registry entry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion\PublisherPolicy\Default\v4.0_policy.6.0.ehRecObj__31bf3856ad364e35\1\6.3.0.0 The key ConfigFilePath had a corrupt character at the end. I removed that, and now its: C:\Windows\Microsoft.NET\assembly\GAC_MSIL\policy.6.0.ehRecObj\v4.0_6.3.0.0__31bf3856ad364e35\policy.6.0.ehRecObj.config After fixing that, it looks for the proper ehRecObj in the assembly folder. Thanks for the ProcMon idea, I always forget about that.
Does this WMC for Windows 10 decode protected cable channels? Hello, I have upgraded my PC from Windows 8.1 Pro with WMC to Windows 10 Pro and found this wonderful thread to bring WMC back to Windows 10. Great work and a whole lot of appreciation and thanks to all those developers who have accomplished this feat! Anyway, I just installed the latest version of the WMC file from this thread (WindowsMediaCenter_6.3.9600.16384_x64_v8) on my Windows 10 PC and I am using a HDHomeRun Prime cable TV box with 3 tuners in it. I got it to play regular broadcast channels via the HDHomeRun box but as soon as I try to change to an encrypted or protected channel, WMC hangs and says that system setting have changed and you should perform a system restore. After this restarting WMC fails to show any channels and just hangs and I have to kill it in task manager. Then I found out that I can just rerun the HDHomeRun setup software to repair Windows Settings and then WMC will work for non-protected channels again. But as soon as I tune to a protected channel, it hangs and locks up again and will not play properly until I run HDHomeRun setup again. So my question for help is this: Is this Windows 10 WMC hack working to decode DRM protected channels yet? If so, what am I missing that I need to do to configure WMC to make it start showing all the DRM protected channels? Is anyone using this to watch Time Warner Cable encrypted DRM protected channels (using HDHomeRun Box) successfully and if so, what are the necessary steps after installing the base package to get it working? I am uploading here a screen capture of the WMC error I got when I tried to tune in to a protected channel. I hope the picture shows up.
Not sure if I'm missing something here, but once I get into "Computer Management", I'm not seeing a "Local Users and Groups" link anywhere. I'm running Win 10 Home, so hopefully this isn't one of those Win 10 Pro limitations.
try the instructions in the post #1157 Code: net localgroup Administrators "NETWORK SERVICE" /add Don't think i can post links... h t t p://forums.mydigitallife.net/threads/61061-DISCUSSION-Patch-WMC-to-run-on-Windows-10-final-amp-possible-alternatives?p=1142008&viewfull=1#post1142008
Hello T-S, would you be able to tell me if this Windows 10 WMC port supports watching the protected channels yet? I've combed through this thread and can't seem to determine if folks are just watching unprotected channels only or can see the encrypted channels also? I am using a HDHomerun Prime box with Cable Card with paid subscription to my Time Warner Cable channels. But this Windows 10 WMC won't decode the encrypted channels and throws an error each time I tune to one. I can only watch the regular over the air channels that they apparently don't encrypt. Is there something extra I need to install to decrypt the channels? (My Windows 8.1 Pro WMC works with all the channels but this Windows 10 WMC port does not).
I'm not in the US nor I use any protected channel here. But according to what I read here paid European channels are working, but American cable cards are working only on free channels.
Okay, thanks for clarifying that. I guess there is more work to be done. I wonder what part of the WMC handles the decryption or decoding here in the USA. Is it that PlayReadyPC program?
So much reading... so I just ask. To me, WMC has always been more than just a (DVD/Media) player. 1. Does this method support non-XBox extenders? I have read that Win8 wmc does not support 3rd party extenders. This is not show stopper as extender UI is kind of old anyway and ServerWMC enables possibilities to use modern apps. 2. How long guide may work? When this dies wmc is useless.
So I am wondering what and where it is in the OS that needs to be fixed to make it work... is it in a Registry key entry specifically tied to and calculated based on hardware and software it is running on? Or is it a program that needs to be modified to decode properly? Does anyone know or have a clue what registry key(s) to examine on an old good working Windows 8.1 Pro machine I have and maybe I can copy or add those keys to the Windows 10 Pro machine and see if it works? I have a PlayReady-v1.3.2313.10-amd64.msi program for Windows 8 downloaded from Microsoft. Has anyone tried to run and apply this over the current Windows 10 WMC update to see if it works to decode DRM channels or will it corrupt everything?
Hi I'm hoping you guys can help. Im on Windows 10 and wanted to keep using Media Centre. I downloaded the files and ran as per instructions. Media Centre is on my PC and will now open, however it seems to not progress past "downloading tv setup data". Did a quick google and found it was due to mcupdate.exe not running. Running this didn't help it download but it did let me progress past that stage. Currently scanning for channels now but is it possible to get the TV guide working or is that a limitation of using it on Win 10? Thanks
Great job on the x64 version for the Windows Media Center. I've installed and tested and everything works. I have a Ceton InfiniTV 6 PCIe, guide works, I've haven't committed to it totally so I don't know if scheduling a recording works properly. I have the Ceton working across my network, and all my PCs see the tuners. I have a Windows 10 x32 and tested the x32 install, the guide does not work, more to the point mcupdate.exe doesn't load. What am I missing? I'm an "Insider" and have my builds installed quite regularly - as expected, the new builds remove Media Center. The process basically means running the install script and then reinstalling the ceton drivers and verifying everything again. Thankfully the insider builds are not that frequent. Some might wonder how I got the x86 Ceton drivers on x86 Windows 10 since Ceton hasn't produced a Windows 8 x86 installer. I took the Windows 7 installer, extracted the files and modified the x86 installer to change the install condition. It looks for the OS =601 and SP level =1, I changed these settings to >=601 to the SP level to 0. Once this is done, right click on the modified .msi file and install. Ceton x86 drivers on x86 Windows 10. Mind you, this is not supported by Ceton. Thank you all for your hard work on this!