Plex DVR Problem.... "No Channels Found" using WinTV-dualHD and Windows server 2012 R2.

Hi all.

I’ve run into a bit of a problem and was wondering if anyone here has encountered it.

For the last few years I have been running Plex on my server which uses Windows Server 2012 R2 without any problems. The current PMS version is 1.9.0.4252

Today I installed a WinTV - dualHD tuner to take advantage of the PVR functionality.

The Win-TV tuner shows up in device manager with no issues.

The tuner also appears as recognised hardware in the Plex “PVR setup” screen. However when you continue to the next page to search for channels the progress bar spins straight round to 50%, pauses for a couple of seconds, and then displays an exclamation mark and the message “No Channels Found”.

I’ve installed the Tuner on my Windows 10 PC with the WinTV 8.5 software and this finds plenty of channels with the antenna in the same location so it is not an antenna / reception issue.

Has anyone come across this before, or could shed some light on whether this could be a Plex or OS issue?

Thanks in advance.

Did you do drivers only for the Plex server? The supported Tuners/Antennas page makes specific note regarding conflict with WinTV software.
See “Notes” - second from bottom re: Windows

Hi JamminR, thanks for your reply.

I had originally installed the whole bundle with the WinTV software. I then saw that note you mentioned when I was searching for a solution.

I uninstalled WinTV and restarted hoping that that could be the issue, but unfortunately the original problem remains. :frowning:

My guess is you didn’t get it completely uninstalled. I have the same tuner and it worked in Win 7, Win 10 and now in Linux Mint. Make sure that you have everything including the drivers removed and start over.

did you find a solution to this issue? I am on windows server 2012r2 as well. No channels found. Only drivers installed.

Hi JaKiSoN.

Unfortunately I haven’t found a solution so the tuner is basically redundant as I still have no PVR functionality.

At least it is good to know that I am not the only one with the issue. Perhaps that would encourage the devs to take a look at it?