A few good tools to keep in your toolkit are: DCA and PlayReady (download from Microsoft) Lav Filters 64 or 32 (from Github) Seans WMC backup Guide Tool TakeOwnership By the way, if you pay the 5 bucks to register Guide Tool, you can edit the duplicates and backup your channels. The backup can be restored to any new builds you might try out. Seans WMC backup saves all your series setups. I don't think WMCv12 will be the last one. TakeOwnership installs into your file explorer. Right Click...TakeOwnership with a single click.
I did pay the donation fee. The only thing I don't have on your list is TakeOwnership. I usually do it through a .bat file, but I will check that out. I have also use MceBackup because you can schedule it to run daily. I've had success with both it and Sean's WMC backup. This was my first use of the DCA tool and I will keep that in the toolbox as well.
I tried it and many others, I thought that it would be easy to get something better than WMC ... after all this effort, couldn't run quicker enough to WMC!
First post. First, thank you to the people behind this. You rock! Second...I need help. I recently upgraded from 8.1 to 10 and tried installing V12 of this and it failed. Realized that Win10 has .NET 3.5 disabled. Fixed that and received a successful install. Upon install and restart, media center will NOT launch. It's as if nothing is occurring. Searching here in this thread it was suggested to do the MediaCenterRecoveryTask from Task Scheduler. Tried that, no change. Then I tried to sfc /scannow. Reboot, nothing. It will NOT launch. Any feedback and help is appreciated! Cheers, Keith
I had the same issue upgrading from one build of Windows 10 to the next. I did a clean install. Then WMC worked.
Hello, After a bug due to SFC /scannow that destroyed patched WMC files (I had V8 or V10 version, I don't remember), I did an uninstall via V12 .cmd files after settings backup, and a new install after reboot. All worked like a charm, especially backup settings restore.
It's the V10 that is affected by that problem. Anyway just replacing the patched files by hand would have fixed the problem
NET 3.5 isn't needed by WMC on w8/10 If the recovery task didn't work try to stop all the WMC related services and delete manually the configuration files inside \programdata\microsoft\ehome
What is the purpose of Guide Tool since it was made for Windows 7 where the Guide in WMC that comes with it works?
Never used it but seem working nicely on w10. I guess the purpose is the speedup of the paring channel/lineup process
Guide Tool allows mapping channels to different i.e. multiple guide sources, for example if your real Microsoft guide source is DVB-T in the UK on a specific transmitter you would obviously set WMC up in WMC on that basis. Unfortunately though the reality is that a single specific guide source like this is typically missing many channels, in this case one can use Guide Tool to map these channels to an alternative choice e.g. DVB-S via Sky even though you are not using DVB-S via Sky. By doing this you combine the data from two or even more Microsoft sources to hopefully fill in all the gaps. I have done this on my Win7 setup and using this solution been able to fill in most but not all the gaps in the Microsoft guide data. Guide Tool can do a few other things especially if you pay the small sum for it.
I still cannot get it (Guide Tool 1.2.5) working on Win10 (64-bit), I have fully enabled NET 3.5 in Windows Features. It crashes instantly when I try launching it, and yes WMC is running. On the topic of WMC it complains about the Guide Tool addin and offers to disable it. This is with WMC v12 from this thread.
While I agree Kodi is not an equivalent replacement for WMC which even I as a Mac user still regard as the best computer TV app there is by far, it is possible to use an official HDHomeRun plugin in Kodi for live TV. HDHomeRun do have a DVB-T/T2 tuner for non-US customers which therefore covers much of the rest of the world, and 'claim' they will be releasing a DVB-S/S2 tuner 'soon'.
I'm taking that the "Troll" won, he got what he wanted. Guys can we keep this on topic and working on WMC for Windows 10, Getting Extenders working and Patching RDP sessions to run WMC with video over RDP ? Thanks !
Tried sfc /scannow to no avail. Tried MediaCenterRecoveryTask with no success. Here are the logs from Event Viewer: Code: Application: ehshell.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.InvalidOperationException at MediaCenter.Store.SqlLite.SqlLiteErr.LogAndThrowException(Int32, System.String, System.Object[]) at MediaCenter.Store.SqlLite.ObjectStore.Open(System.String) at MediaCenter.Store.SqlLite.ObjectStoreManager.Open(System.String, Boolean) at Microsoft.MediaCenter.Store.ObjectStore.Open(System.String, System.String, System.String, System.Reflection.Assembly, Boolean) Exception Info: System.InvalidOperationException at Microsoft.MediaCenter.Store.ObjectStore.Open(System.String, System.String, System.String, System.Reflection.Assembly, Boolean) at Microsoft.MediaCenter.Store.ObjectStore.Open(System.String, System.String, System.String, Boolean) at Microsoft.MediaCenter.Store.ObjectStore.AddObjectStoreReference() at Microsoft.MediaCenter.Store.ObjectStore.get_DefaultSingleton() at ServiceBus.UIFramework.UserControlPoint.Launch(System.String) Code: Faulting application name: ehshell.exe, version: 6.3.9600.16384, time stamp: 0x5215efc2 Faulting module name: KERNELBASE.dll, version: 10.0.14271.1000, time stamp: 0x56c6e0cd Exception code: 0xe0434352 Fault offset: 0x000000000000d7b8 Faulting process ID: 0x23ec Faulting application start time: 0x01d172fc2fdcc3b2 Faulting application path: C:\Windows\ehome\ehshell.exe Faulting module path: C:\WINDOWS\system32\KERNELBASE.dll Report ID: 1c96575a-3fea-488c-b913-fe7d327a6372 Faulting package full name: Faulting package-relative application ID: Code: Fault bucket 94622878228, type 5 Event Name: CLR20r3 Response: Not available Cab Id: 0 Problem signature: P1: ehshell.exe P2: 6.3.9600.16384 P3: 5215efc2 P4: mcstoredb P5: 6.3.9600.16384 P6: 5215cc8d P7: 7d P8: 34 P9: System.InvalidOperationException P10: Attached files: C:\ProgramData\Microsoft\Windows\WER\Temp\WER70EC.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ehshell.exe_b75b8af2118181827f86e76266e77ea1b5e81ff_5f18ef41_15e27830 Analysis symbol: Rechecking for solution: 0 Report ID: 1c96575a-3fea-488c-b913-fe7d327a6372 Report Status: 0 Hashed bucket: c3616fcb66fededd3c59478e22c589b4 Contents of AppCrash_ehshell.exe_b75b8af2118181827f86e76266e77ea1b5e81ff_5f18ef41_15e27830: Code: Version=1 EventType=CLR20r3 EventTime=131012291653326461 ReportType=2 Consent=1 UploadTime=131012291655481697 ReportIdentifier=6ed7f2a7-deef-11e5-89b2-2818784bfab2 IntegratorReportIdentifier=1c96575a-3fea-488c-b913-fe7d327a6372 NsAppName=ehshell.exe Response.BucketId=c3616fcb66fededd3c59478e22c589b4 Response.BucketTable=5 Response.LegacyBucketId=94622878228 Response.type=4 Sig[0].Name=Problem Signature 01 Sig[0].Value=ehshell.exe Sig[1].Name=Problem Signature 02 Sig[1].Value=6.3.9600.16384 Sig[2].Name=Problem Signature 03 Sig[2].Value=5215efc2 Sig[3].Name=Problem Signature 04 Sig[3].Value=mcstoredb Sig[4].Name=Problem Signature 05 Sig[4].Value=6.3.9600.16384 Sig[5].Name=Problem Signature 06 Sig[5].Value=5215cc8d Sig[6].Name=Problem Signature 07 Sig[6].Value=7d Sig[7].Name=Problem Signature 08 Sig[7].Value=34 Sig[8].Name=Problem Signature 09 Sig[8].Value=System.InvalidOperationException DynamicSig[1].Name=OS Version DynamicSig[1].Value=10.0.14271.2.0.0.256.48 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=3081 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=6f13 DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=6f13d0d71ae1e049b39f145a01b502b4 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=9f5e DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=9f5e85a7839d4bcb6213bc9d0b8a025d UI[2]=C:\Windows\ehome\ehshell.exe UI[3]=Windows Media Center has stopped working UI[4]=Windows can check online for a solution to the problem. UI[5]=Check online for a solution and close the program UI[6]=Check online for a solution later and close the program UI[7]=Close the program LoadedModule[0]=C:\Windows\ehome\ehshell.exe LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll LoadedModule[2]=C:\WINDOWS\system32\KERNEL32.DLL LoadedModule[3]=C:\WINDOWS\system32\KERNELBASE.dll LoadedModule[4]=C:\WINDOWS\system32\msvcrt.dll LoadedModule[5]=C:\WINDOWS\system32\ole32.dll LoadedModule[6]=C:\WINDOWS\system32\combase.dll LoadedModule[7]=C:\WINDOWS\system32\RPCRT4.dll LoadedModule[8]=C:\WINDOWS\system32\bcryptPrimitives.dll LoadedModule[9]=C:\WINDOWS\system32\sechost.dll LoadedModule[10]=C:\WINDOWS\system32\GDI32.dll LoadedModule[11]=C:\WINDOWS\system32\USER32.dll LoadedModule[12]=C:\WINDOWS\system32\win32u.dll LoadedModule[13]=C:\WINDOWS\system32\OLEAUT32.dll LoadedModule[14]=C:\WINDOWS\system32\ucrtbase.dll LoadedModule[15]=C:\WINDOWS\system32\SHLWAPI.dll LoadedModule[16]=C:\WINDOWS\system32\ADVAPI32.dll LoadedModule[17]=C:\WINDOWS\SYSTEM32\mscoree.dll LoadedModule[18]=C:\WINDOWS\system32\IMM32.DLL LoadedModule[19]=C:\WINDOWS\system32\kernel.appcore.dll LoadedModule[20]=C:\WINDOWS\system32\uxtheme.dll LoadedModule[21]=C:\Program Files\Common Files\microsoft shared\ink\tiptsf.dll LoadedModule[22]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll LoadedModule[23]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll LoadedModule[24]=C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll LoadedModule[25]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\mscorlib\08755eb887123213c19ac0ce55a074ed\mscorlib.ni.dll LoadedModule[26]=C:\WINDOWS\system32\clbcatq.dll LoadedModule[27]=C:\WINDOWS\SYSTEM32\sxs.dll LoadedModule[28]=C:\WINDOWS\SYSTEM32\VERSION.dll LoadedModule[29]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System\dad68b1b83b3117946364062ac618976\System.ni.dll LoadedModule[30]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\Microsoft.M1fb29482#\4f207121f4bbfb4fdfc23a2c53e8394e\Microsoft.MediaCenter.UI.ni.dll LoadedModule[31]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll LoadedModule[32]=C:\WINDOWS\system32\rsaenh.dll LoadedModule[33]=C:\WINDOWS\SYSTEM32\bcrypt.dll LoadedModule[34]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll LoadedModule[35]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\Microsoft.Mac4b2f20#\d18b1e6a0d7fe941087354460a44ff58\Microsoft.MediaCenter.Shell.ni.dll LoadedModule[36]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\Microsoft.M6a850d50#\1a8837fb88d5a2a49f13e80c6aed7bb0\Microsoft.MediaCenter.ni.dll LoadedModule[37]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\Microsoft.M375d8927#\e277e80dcb0e23d22479bd0df99778ae\Microsoft.MediaCenter.Sports.ni.dll LoadedModule[38]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\ehshell\538de86608355efaeba1687127111e14\ehshell.ni.dll LoadedModule[39]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\mcstore\1ecef1679fa5ba9c97f45ef274cc9890\mcstore.ni.dll LoadedModule[40]=C:\Windows\ehome\EhUI.dll LoadedModule[41]=C:\WINDOWS\system32\POWRPROF.dll LoadedModule[42]=C:\WINDOWS\SYSTEM32\dxgi.dll LoadedModule[43]=C:\WINDOWS\SYSTEM32\d3d9.dll LoadedModule[44]=C:\WINDOWS\system32\WS2_32.dll LoadedModule[45]=C:\WINDOWS\system32\SHELL32.dll LoadedModule[46]=C:\WINDOWS\system32\cfgmgr32.dll LoadedModule[47]=C:\WINDOWS\SYSTEM32\DSOUND.dll LoadedModule[48]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.14271.1000_none_ac15ea49add3c7fe\gdiplus.dll LoadedModule[49]=C:\WINDOWS\system32\windows.storage.dll LoadedModule[50]=C:\WINDOWS\SYSTEM32\MSIMG32.dll LoadedModule[51]=C:\WINDOWS\system32\shcore.dll LoadedModule[52]=C:\WINDOWS\SYSTEM32\WINMM.dll LoadedModule[53]=C:\WINDOWS\system32\profapi.dll LoadedModule[54]=C:\WINDOWS\SYSTEM32\WTSAPI32.dll LoadedModule[55]=C:\WINDOWS\SYSTEM32\dwmapi.dll LoadedModule[56]=C:\WINDOWS\system32\SETUPAPI.dll LoadedModule[57]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll LoadedModule[58]=C:\Windows\ehome\ehtrace.dll LoadedModule[59]=C:\WINDOWS\SYSTEM32\msftedit.DLL LoadedModule[60]=C:\Windows\ehome\ehuihlp.dll LoadedModule[61]=C:\WINDOWS\SYSTEM32\ATL.DLL LoadedModule[62]=C:\WINDOWS\system32\NETAPI32.dll LoadedModule[63]=C:\WINDOWS\SYSTEM32\SLC.dll LoadedModule[64]=C:\WINDOWS\system32\WINTRUST.dll LoadedModule[65]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.14271.1000_none_cde82d6573246025\COMCTL32.dll LoadedModule[66]=C:\WINDOWS\system32\MSASN1.dll LoadedModule[67]=C:\WINDOWS\system32\CRYPT32.dll LoadedModule[68]=C:\WINDOWS\SYSTEM32\WINSTA.dll LoadedModule[69]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV LoadedModule[70]=C:\WINDOWS\SYSTEM32\sppc.dll LoadedModule[71]=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL LoadedModule[72]=C:\WINDOWS\SYSTEM32\SRVCLI.DLL LoadedModule[73]=C:\WINDOWS\SYSTEM32\NETUTILS.DLL LoadedModule[74]=C:\WINDOWS\SYSTEM32\ntmarta.dll LoadedModule[75]=C:\Windows\ehome\ehres.dll LoadedModule[76]=C:\WINDOWS\SYSTEM32\SspiCli.dll LoadedModule[77]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Xml\129ea3a83283bc1f4ac443c1044d1a1d\System.Xml.ni.dll LoadedModule[78]=C:\WINDOWS\SYSTEM32\sqmapi.dll LoadedModule[79]=C:\WINDOWS\System32\MMDevApi.dll LoadedModule[80]=C:\WINDOWS\System32\DEVOBJ.dll LoadedModule[81]=C:\WINDOWS\System32\PROPSYS.dll LoadedModule[82]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL LoadedModule[83]=C:\WINDOWS\SYSTEM32\wintypes.dll LoadedModule[84]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll LoadedModule[85]=C:\WINDOWS\system32\MSCTF.dll LoadedModule[86]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\mcstoredb\d26cb9a5c542ba567b0d1f0e39939d1c\mcstoredb.ni.dll LoadedModule[87]=C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mcstoredb\v4.0_6.3.0.0__31bf3856ad364e35\mcstoredb.dll LoadedModule[88]=C:\WINDOWS\SYSTEM32\RASAPI32.dll LoadedModule[89]=C:\WINDOWS\SYSTEM32\rasman.dll LoadedModule[90]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\ehiProxy\58b7e126356818cc8efb454ae13412c8\ehiProxy.ni.dll LoadedModule[91]=C:\WINDOWS\system32\sqlceoledb40.dll LoadedModule[92]=C:\WINDOWS\system32\sqlceqp40.dll LoadedModule[93]=C:\WINDOWS\system32\sqlcese40.dll LoadedModule[94]=C:\WINDOWS\system32\psapi.dll LoadedModule[95]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\diasymreader.dll State[0].Key=Transport.DoneStage1 State[0].Value=1 FriendlyEventName=Stopped working ConsentKey=CLR20r3 AppName=Windows Media Center AppPath=C:\Windows\ehome\ehshell.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=7E19DA245B38C56D613DAC6405F3AB72 MetadataHash=-524052124
WMC is supposed to be NOT running, when you start guidetool. Have another look at the Windows Features picture...... NET 3.5 is NOT Fully Enabled
Come on guys dont reply to stupid statements with other stupid statements. While Kodi is not on par with WMC on the GUI side, it wins hands down on setup side. All you have to do is to instal the tv plugin, and enable it. To connect with an endless list of backends, WMC included via DVBLINK and WMC via ServerWMC. In case the backend and kody aren't on the same PC you need also the IP. That's all. The configuration is retained, even if Kodi isn't properly installed. The same is true for Mediaportal which (unlike Kodi) is a direct WMC competitor. Only MythTV has a steep learning curve, but almost everything else beats WMC hands down on ease of setup.