Which one of these steps from the Workaround did not work? Which step do you need help with? If you have Guide data download problems (specially US residents): 1.Open notepad (right click> run as administrator) 2.Open host file ( File>open> c:\windows\system32\drivers\etc\hosts) 3.Add this to the end of the file- 2.16.216.176 cdn.epg.tvdownload.microsoft.com and place one of the below ip addresses depending on your location in the US west coast or east coast 65.55.186.113 data.tvdownload.microsoft.com central or southern us 65.55.5.170 data.tvdownload.microsoft.com ex. If you lived on the east coast you would add this to the bottom of the file: 65.55.186.113 data.tvdownload.microsoft.com 2.16.216.176 cdn.epg.tvdownload.microsoft.com 4.Save the file (file>save) 5.Open CMD command prompt (file>search for cmd>right click>run as administrator) 6.Type: ipconfig /flushdns If you type it correctly it should say: "successfully flushed the dns resolver cache." 7.Close Windows Media Center if it is open 8.Start>type "c:\ProgramData\Microsoft\ehome" 9.Delete file "mcepg2-0" and folder "mcepg2-0" this will force you to set up live tv from scratch in WMC (or delete anything named m***.db and the corresponding folder) 10.Open windows media center and go through the Live TV setup and you should now be able to download guide data
I fully understand and highly appreciate it that the 'Tricked' installation is working as it is. I just wanted to ask if others experience the same issue and might have found a solution which solves the problem. I 'm currently using 6.3.9600.16384_x64_v11.7.
Display Driver Error Anything I can do about this? Win7 RDP to Win10-WMCv12 I can play Live DRM for 2 seconds, then I get Display driver error with: "The video playback device does not support playback of protected content" STRZHD (channel 1980) is a DRM Channel.
Could you repost your original question. Edit....I found your question... That problem was fixed with v12 If you want to continue using v11, you will need to find the command. I don't remember the cmd at the moment. Open an elevated command prompt and type the command in the picture. click on v11 in my signature and start reading....you'll find it.
Well obviously there's an error in there somewhere or it would have worked. Let's start by having a look at your host file.
sorry to be rude but I have done these steps repeatedly and looked at other methods and still failed. I had WMC working perfectly until I got a windows update a few months ago and it wiped WMC. That is when the problem began. Anyways the host file at the bottom I put 2.16.216.176 cdn.epg.tvdownload.microsoft.com and 65.55.5.170 data.tvdownload.microsoft.com since I live in FL.
In the past I had few situation were I was unable to get the livetv configuration data correctly. In that case the faster thing one can do is to take the W10 iso and do an in place upgrade. Especially on SSD that takes few tenths of minutes, and spares hours of futile attempts.
Hello, Did you apply some Tweaks to Windows 10 ? If you desactivate access to Microsoft servers (M$ antispy tweaks) it will block guide DL.
I think the issue they're having is more to do with the setup data. If MC can't download the initial setup data, it doesn't go on to get EPG data. I can ping the EPG IP just fine, but I get no reply from any of the Data IPs. Something is definitely down or changed on Microsoft's end and it's only affecting people trying to setup a new Media Center from scratch.
Usually when someone answers your offer to help with... sorry to be rude It really means they don't want help. No offence intended Sergio, I am finished with this particular Guide Conversation.
Wanted to post what this issue ended up being in case anyone else comes across it. It ended up being this setting in the Intel video drivers under on of their advanced sections called dynamic contrast. Disabling that fixed my issue. Weird that it was only with hdhomerun film content. Maybe because it was mpeg2 and mkv is different? Really sent me down the wrong path in troubleshooting I can tell you that.
Yea, that's been an oft reported condition/fix on the Silicon Dust (hdhomerun) forums for some time. It also can apply to nVidia settings as well.
So, I am reluctantly moving back to Windows 7. I really got my hopes up with the success of the local instance of WMC. However, without xbox360 extender support this project is kinda pointless IMHO. Any life left in that subject? Btw, I've done the whole RDP extender from a remote PC in the past. No matter how much I wanted it to, the experience just does not compare to the polished finish of the xbox360 interface. There is definitely potential there, but after years of fiddling I never got anything that just 'worked' as well as the 360 extender (even though I surrendered certain extras I liked in the PC 'extender'). Thanks to all who have placed all of their hard work to getting this as far along as it is... Keep up the good work!
I disagree with this project being pointless without xbox 360 support, not everyone uses an xbox to watch live tv. I'm really happy we have WMC working in Windows 10.