Hi.. Thanks for the tool. I'm having a few problems with this however. WMC cannot download tv setup data. I changed the hosts file as suggested. Maybe there is a problem that I am in Colombia right now and it has trouble with the region. It doesn't find any channels after not being about to download the data. I'm connected to cable through an elgato eyetv hybrid USB tuner. Next PVR can find several channels but really I want to use WMC because the channels change slowly with Next PVR and the program locks up.
To be clear I was asking about the xbox extender fix. In meluvalli's post that is linked from page 1, the instructions include downloading Mcx2Prov.zip and NTRights.zip. Those download links are outdated and broken.
Hi Kamo, what version are you using? What upgrade path did you take to windows 10? what version of windows 10 are you using?
Thanks Five, You need to be more specific in the future, there are several versions and many different ways to get to many different versions of windows 10.
Sorry for the confusion. I quoted meluvalli and it linked to his post. For anyone else that is looking for the xbox 360 fix, I found a post via google for T-S. If you use the alternative branch, it includes both the correct Mcx2Prov.exe.X360 and the NTRights.exe file. You will still need to do some legwork. I tried using meluvalli's directions and got an error message when adding my extender. They were followed to a T. (I put the xbox 360 version of Mcx2Prov.exe in the bin\MediaCenter directory before installing WMC. I modified the installer.bat to include the two lines meluvalli provided. I then installed the latest version of RDPWrapper and WMCv12. No issues with install. Rebooted. Ran WMC as admin and tried to add an extender. All the error message says in WMC is "An error was encountered while configuring your computer for use with this Extender." meluvalli, if you are still active, my windows 10 version is 1607 OS build 14393.187. Have you come up with another workaround that works? Anything else to try?
check event viewer and see if any errors happened at the time you attempt the extender setup, I've had issues like that when running xbox as extender with various updates. there were a few fixes i'm not certain if they are included in the installer, or if they need to be manually done. at any rate if you find an error in event viewer it gives a place to focus.
Looks like it is the modified Mcx2Prov.exe that is the issue. I get an application error with that one. I used the file Mcx2Prov.exe.XB360 from T-S version (alternative branch). Code: Faulting application name: Mcx2Prov.exe, version: 6.3.9600.16384, time stamp: 0x5215e514 Faulting module name: FunDisc.dll, version: 10.0.14393.0, time stamp: 0x57899a44 Exception code: 0xc0000005 Fault offset: 0x0000000000005b5e Faulting process id: 0x1e40 Faulting application start time: 0x01d216a394f42568 Faulting application path: C:\WINDOWS\ehome\Mcx2Prov.exe Faulting module path: C:\Windows\System32\FunDisc.dll Report Id: 85b1f039-648c-4122-a64c-05680955d9c0 Faulting package full name: Faulting package-relative application ID:
I'm using the latest version, I just downloaded it from here. Although I did have an earlier version installed that I found online. I went through the uninstall process before installing the latest version. I upgraded to windows 10 from windows 7. I'm using the latest windows 10 as well. I know there is a problem with using HDhomerun with the anniversary update but I thought since I'm using a normal usb tv tuner it would be fine. Maybe I assumed incorrectly :|
You should be OK. Try to reset your settings with the script included in w8.8.1 and start over the configuration
I uninstalled WMC, rebooted and carefully went through the steps again. The first time I had replaced the Mcx2Prov.exe file in the wrong directory. I had done the one in bin\MediaCenter\Windows\ehome instead of placing it simply in bin\MediaCenter. I tried to install WMC, got an error and said reboot and try again. Rebooted, ran the rights.bat and then the installer.bat, everything was fine. Rebooted again. Went into C:\windows\ehome and verified that Mcx2Prov is indeed 10537. Ran WMC as admin and tried to add extender again. On the xbox it acts like it's going to connect. It goes to the black screen and says contacting... But on the computer it only made it through top 2 checkboxes when adding extender. Configuring computer settings and searching for your extender. After a minute or so, it errors out. This time when I check event viewer, no errors or anything. The only thing in windows logs\applications in that time frame is all related to software protection service.
So my darn laptop updated to a new windows update. I saw that WMC was deleted so i tried everything i've done in the past but didn't work (No tuner, which my tuner is working well).. So i went to updates on my laptop and decided to go back to my previous version and so i did. Now i see WMC was deleted and i had to reinstall it. I did everything again but still saying "No TV Tuner" any suggesting? I tried "If WMC does not find any tuners (HDHomerun): restart the system then put the system in sleep state and then wake it back up" and nothing.
Windows 10 Anniversary update wiped out WMC I'm another victim of the anniversary update. I was running version 10.0.14393.0 perfectly fine - only using it to record OTA TV on Hauppauge tuners. After the anniversary update wiped out WMC, I tried to reinstall but am getting this error: Image Version: 10.0.14393.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. Has anyone else had any luck getting this to work again after anniversary update? I've tried uninstalling/rebooting/re-installing - no luck yet. Any help is appreciated. EDIT: I may have gotten a successful install; however, launching ehshell.exe does nothing... Another edit: I'm an idiot. I was apparently using an older version; installing 8.8.1 seems to be working. Maybe my stupidity will help someone else...
Hi all, I just wanted to say thanks to those who put the time in to get the working builds of WMC up and available. Normally I would grab and run but effort like this should be acknowledged. 1607 also killed WMC v12 for me which was nicely working prior, so great to have a working version available > Thanks T-S. Like many others, I am no real fan of the alternatives to WMC and purchased windows 8.1Pro really specifically for WMC. Therefore I am greatful for the constant effort to enable the regression of WMC in windows 10 to be bypassed. Much appreciated! Best Regards J
Thanks to all who are keeping WMC up and running on Win10 ... and hopefully on the Anniversary Update as well as some point in the future?!? Quick question on running WMC from within a RDP session: I installed T-S's "WMC9600x64-RDP-patch-V2.7z" RDP patch and can now launch WMC from within the RDP session but I can't run WMC in full screen mode. When I maximize WMC, the screen is blacked out and I can only minimize WMC by hitting the windows key. Interestingly, when I hit the windows key and the windows start menu pops up, I can then see WMC in full screen mode in the background but cannot make it the active window without triggering a black screen again. The only way I've found to get out of the situation is to minimize the WMC window which immediately reverts back to a usable WMC window. So WMC seems to be running just fine when maximized but something is triggering a black screen. Anybody seen this behavor before? Am I missing something from the RDP patch? You only have to run this patch on the WMC server correct? i.e. - I don't have to also run this patch on any machine I'm launching RDP on and connecting to my WMC host - correct? Thanks much