OK A picture is better than 1000 words. Which means, that almost surely I'm the first person in the world to have WMC running in 2012 Standard So thanks to @abbodi1406, but I did my part having the TV package archived for 8 years after discovering it (2012 essentials is likely the only windows that has all the BDA and other components packaged in a single place) So I can confirm that Microsoft-Windows-Video-TV-Core-Package-amd64-6.2.9200.16384 (from 2012 Essentials) is enough to run WMC (and other TV programs) In Server 2012 Standard/Datacenter. Also you need the LAV codecs, given on Server 2012[R2] the MSmpeg2/h264 codecs can't be unlocked with the DVD app like in server 2016+ Unless @abbodi1406 has some magic in his sleeve to unlock the codecs as well.
Thank you guys for all the work you do in keeping WMC up to date and working. I will try out your latest version when WMC next corrupts its database and creates a new mcepg3-0 dir (due to my backup) Could you make a black skin version please? Thanks Alan
@abbodi1406 After the 9200 build I finally had the chance to test the W10 builds, and the package itself seem working perfectly BUT The superuser app you used shares the same flaw that nsudo 9.x has (I detailed that many times in the MSMG thread but I'm going to summarize the problem again) In a scenario like mine, which is not so uncommon on the HTPC/Home server environment, I have a "WMC" user that does autologon, and is dedicated to watch the TV locally on the main room of my home, then I have a "MAIN" user that is dedicated to all other tasks, that I use remotely via RDP. Well both nsudo 9 and superuser64, if launched from the RDP seession, opens the CMD windows in the WMC user, not the user logged via RDP. This is at least confusing, I discovered that after a lot of time, initially I thought that nothing was happening at all given the TV is in another room (and in standby). nsudo8 (the on bundled with both my and yours old version of the installer) still works flawlessly (even on Win 11 and server 11, where nsudo 9 fails miserably)
I just tried WMC-V8.10.0 x64 on win 11 x64 ver 22H2 build 22621.2715 fully up to date, I correctly used the previous ver 8.8.5 uninstaller and rebooted and checked nothing was left over. The "another command prompt window" did not stay open, I also rebooted after it did not stay open. Any suggestions Thanks Alan
newbie question: Are there step by step instructions to add WMC to current version Windows 10? I've been using WMC with an old Windows7 machine to record/save OTA tv shows, with a hauppage tuner card and EPG 123. But I need to move up to a better computer that can handle h.265 4K movies and so on. Shall I just use the version on the EPG123 webpage: ht**s://garyan2.github.io/win10.html ? And then I thought I'd disable Windows 10 from updating once I get it working since it sounds like updates cause problems. How's that plan? Is that better than continuing using Windows7 to use WMC still?
Hi Don, WMC can be run on win10/11 with updates with no problems. I use DVBGuide for OTA updates along with EPG123 the instructions are in the readme file, under the "Installation:" section
@Don2737 Gary's WMC MSI installer is easy to install and works great on Windows 10 and 11 but AFAIK WMC of any version doesn't play H.265.
Is this your latest version? Got Wmc working Gary’s install file) but no digital tv picture. I’m using latest version of windows 10. Can you correct me if I’m wrong would the Intel Graphics 4400 causing it to not run properly? I’m just wondering as NextPVR was Ok, but Im thinking there’s a codec or potential graphics card issue for the blank picture on the live tv. I’ve even re-installed windows 10 and same problem. thanks, just a short term issue moving to a much faster pc once set up fully.
Just try WMC using the default microsoft adapter (no specific vga driver installed) to rule out a specific driver problem, WMC should work. Also you can try installing "actual multiple monitors" that long time ago I discovered it does some magic that fixes many odd WMC behaviors. (no specific configuration needed, just install it, then try WMC)
I thought that after 10 years the matter was understood pretty well. You need TI rights to install WMC. Nowadays (unline in 2015) there are many ways to do that nsudo 8 was used in my and abbodi's old installers, but the latest version from abbodi use superuser64 (which proved to be not working in all scenarios). So, if you dont want to edit yourself the installer scrips, just launch a cmd windows via nsudo, then launch the install.cmd (the one inside the bin folder) from that window.
@acer-5100 re WMC-V8.10.0, I have not seen this in the instructions, or seen it mentioned in this thread, or heard of anyone else having to do this. is there something wrong with my win 11 install, or something that needs to be done?
Sorry but you expect that someone publish something that has a problem and instead of fixing it will write something in the readme? Obviously the problem was not widespread and/or evident at the moment of the upload. Do you want a working program or you are interested in reading something? You asked, right after I reported the problem, I replied twice so to your question so what's the problem? There is no win11 just like there was no win 10, there are major builds of windows. In win 11 case something that worked with 22000 may not work with 226xx or with 23xxx, just like there are features that worked in Win10 1507 but dont work in 22H2 Did you care to read the replies and act accordingly? Perhaps no one forces you to use the very latest release from Abbodi (which brings refinements but not earth shattering novelties), I still use the 8.8.1 T-S (+ WMC mutitool in 1803 - 23H2) and it works as it worked in 2015
I originally asked for suggestion to my problem as there is no mention of it on this thread and no mention of a workaround in the readme file, no one responded. A month later I asked again, you respondeded and suggested I look at your post before my question with a suggeston. I did read your post and it didnt seem relevant to my problem, even though you gave a suggestion you didnt go into detail. I didnt know what nsudo does or superuser64 and read up on it and found out about TI "trusted installer". I have never used it, or had to and not heard about anyone else having to. I then asked if you could elaborate please, you replied and explained about TI and nsudo 8 and what to do, ok. I then ask if there might be something wrong with my win 11 install, I quoted the ver I am using in my original question, although it is fully updated, it is not at the latest version and wont update anymore. if there was a problem and it has been fixed, fine, there has been no further updates since WMC-V8.10.0 that I have seen and no other mention of my problem to suggest a fix has been made. of course I want a working program, I am curious as to whats causing it and wondering if its my "build" of win 11 I use ver 8.8.5 on win 10 22H2 build 19045.3803 with no problems I have a spare ssd with win 11 on, that I wanted to test and give feedback on. Have I said or done anything wrong, or to offend?
No one has ever used something before using it for the first time, perhaps If you ever installed any WMC package from me, abbodi and and variation from other users, you have already used. I patiently explained what they are and I explained patiently how to overcome the problem you are facing. For everything else duckduck is your friend So I still dont understand what prevents you from following the suggestions that i provided using a bit of my free time. And I think my free time is, at least, as valuable as yours. Yea that's a scoop. Don't you think that if there was a ready made meal for you, it was easier for me to provide a link to the updated file? Abbodi decided to don't take actions, And I didn't asked further given there isn't any practical impact. Overcoming the problem is deadly simple and takes something like 10 seconds, so again I still can't see where your big problem is. Follow my instructions or use an older package. That's all