Guys, I clean installed Win10 1903 18362.30. Installed OTA HDHR drivers. Then Installed WMC v13. It says no tuners detected. I used to know a fix for this. Been searching, to many results to WeeD through. What is the fix now? Does this v13 work on 1903?
I did similar but restored my v8.8.3 backup before trying to use the tuners. I didn't have to scan in WMC (I did in HDHR just in case), the tuners just worked. At this point my only issue is the same from 1803, I can't run full screen and I often get a decoder error on playback. I'm mainly using Emby Theater for playback so it's only an issue when something is still recording. I haven't switched to Emby for recording and fully ditch WMC yet because: 1) All of my shows are already scheduled in WMC and it'll take forever to get them into Emby. 2) I don't like the way the guide works in Emby Theatre's couch mode as much as WMC. If you want to know why just use them both, the way WMC works is what it should do. For example it's easier to move to another day with a remote, and you can hold down the arrow buttons and it goes faster, etc. etc. 3) I don't often keep my recordings, so I like the folder view you get in WMC. The only way I've been able to duplicate how that works in WMC in Emby is using the ServerWMC plugin. For some stupid reason you can't set it to group per program in Emby's built in recorded TV, it just barfs all 20+ items I have in my recorded tv folder into a long list of files. In MWC it groups them by show perfectly. There are a few things I would like to keep and convert to an H265 MKV and move to a series folder, so it would be great if we had a way to tell Emby to convert and move a file on demand in Theater. I guess long term my solution to fully move to Emby will be to embrace post-processing and move things into per series folders, but so far my attempt to figure out how to set that up hasn't worked. I went through all of the Emby settings to enable series processing of Recorded TV but it doesn't do anything. I don't know what I missed and haven't had time to dig through the wiki to figure it out. Someday... or I'll get lucky and they'll eventually fix all the above before I get around to doing it LOL ;-).
HI guys just installed fresh win 10 1903 install wmc player and is not completely working, trying to play wtv files but an error about codecs comes up, tuners work and scan in but wont show live tv error says both tuners are busy but it actually records ok but doesnt play back recorded tv with wmc , but wtv file is ok with another player
Found out a fix for no tuner detected. No I am stuck at Downloading TV Setup Data. I put in the entries in the hosts: Are these right? Anything else to do? 65.55.186.113 data.tvdownload.microsoft.com 2.16.216.176 cdn.epg.tvdownload.microsoft.com Tuner detect fix: Go to Services. Scroll down the Services list and find Windows Media Center Receiver Service. Right-click Windows Media Center Receiver Service, and then click Properties. Click the Log On tab, and then select Local System account. Click Apply, and then click OK on the Services message. Restart the computer.
As documented in any number of previous posts, there are DLLs that need to be replaced in later versions of win10. Technodevotee's package has a utility to replace them automatically or you can do it by hand if look for posts mentioning MSVidCtl.dll.
While MS's servers have been rather unreliable my logs indicate they've been available for at least the last few days. That doesn't necessarily mean you're going to be able to set a new installation up without retrying the setup dozens of times however. Those IP addresses are old and 2.16.216.176 doesn't work any more. The easy but not completely free ($25/year) solution is to use EPG123, a solution I recently adopted and can attest that it works really well. Even when the MS servers are up and you can talk to them and you've got your WMC setup done the quality of their guide info is inferior to the Zap2it data EPG123 pulls down. Highly recommended, garyan2 did a bang up job with it.
If you're still having trouble with full screen playback you can use my launcher, not sure if anyone ever got full screen working lately without using earlier versions of win10. Personally even if you could get full screen working I prefer my launcher as WMC no longer hogs the cursor.
Yea I actually use it sometimes, but the issue is I have stacked 60" Panny Plasma TVs and the bottom one is at eye level (I know, first world problems). If I put WMC on the bottom TV it leaves the WMC window's top header on the bottom of the top TV. I don't want to get burn in so I don't want to run it that way for more than an hour or two. I tried swapping the TVs in Windows display setting and it worked to push the top bar out of the bottom TV's viewing area (because that TV was now the "top display" to Windows), but then I kept getting confused when I wanted to drag stuff to the top TV because they were backwards LOL...
Hmm, tricky one. I guess somewhere or other those display coordinates are stored in the registry and you could move the top display 32 or more pixels up (assuming it's not the primary display of course, otherwise you'd have to move the other one down), but good luck finding them. Guess you'd have to search for values like 1920 occurring near 1080 or what have you. Serious voodoo.
Definitely affected me. Kept noticing graphic glitches. And occasional lag spikes. Just while on desktop idling. I won't boot to 1903 partition until MS fixes it sometime in August.
I'd be checking your video drivers. I updated the sacrificial laptop to 1903 shortly after it was released and while I haven't set up WMC on it I did notice that RDP to the machine presents a nice solid black screen instead of anything useful. Digging into it MS recommend display driver update as the solution, barring that setting the display driver to plain generic VESA level of functionality (of course that thing was made in Vista's day so no new display drivers for it, no way MS can fall back to legacy behavior, pathetic) so they clearly changed something deep in the kernel so if you've got a recent display device I'd be pulling down some experimental drivers. Or sticking with 1809 of course... I'll set up WMC on my 1903 box see if I see your lag issues. UPDATE: Yeah, my 1903 box runs WMC without laginess so it's idiosyncratic, still bet video drivers are going to be the root of the issue though. And sometimes Windows Update has the right driver, I updated another of my boxes to 1803 months ago and it's network card lost it's ability to wake on LAN, going into the device manager and selecting update driver fixed the issue much to my surprise. Of course RDP to my 1903 box is still borked so the July patches didn't rectify that.
I finally gave up and updated 1511 I hard locked to 1903. I can't get it to see my HDHomeRun Prime so I'll use Plex or the Silicon Dust record ap. I have a tower that has 7 ultimate 64 and a I7 980 that I can run WMC on if I can get it to wake up from sleep reliably and use my newer 4960x tower to recode the captures if I want to keep using WMC. Sucks that they decided to kill WMC seeing how it's still the only option that supports the movie channels DRM. Luckily I only have one movie channel that I hardly watch but it's the principle of it as much as anything. I've been through all of the work arounds and it's getting to be not worth all the aggravation every time no tuner was available etc to try and fix it yet again. My box has been locked to 1511 since it came out but other things were having issues.
I finally spent some time investigating this issue and found what was causing it (some missing COM registrations in the MSVidCtl manifest that were not properly generated by the mt.exe tool). That said, I read that a few folks here had to replace CPFilters.dll in System32 and it's not clear to me why as it works fine on my 1903 18362 VM without that. But maybe it was caused by the fact WMC still used the global MSVidCtl.dll for some operations? It's also possible it was just a regression in CPFilters.dll that was later fixed (since this file was updated by MSFT mid-June). I haven't migrated any prod' machine to 1903 yet, so that would be great if someone was willing to give my 8.8.4 package a try: if you're interested, please tag me and I'll PM you the Mega link. I finally managed to reproduce that on a test machine and updated the 8.8.4 package to include a local copy of CPFilters.dll and an assembly manifest, which should solve the issues caused by the breaking changes in 1903. Thanks.