Build 21277 - Hauppauge WinTV software stopped work

Anonymous
2020-12-11T22:48:48+00:00

After upgrade Win 10 to the latest build, my Hauppauge Win-TV 10 software doesn't work. It will find the TV tuner (Hauppauge HVR-2200), but when I chose any channel, the screen is still black and I've got such info: "Er ror starting Live TV - Device in Use - Check Cortana is not using your Win-TV-HVR-2200 Serial:0". Which is strange, because I have no Cortana (in Polish Windows it's unavailable).

After reinstalling Win-TV 10 it can detect TV tuner, but when scanning channels can't find any except S-Video input (which is active, with cable TV STB connected to). When I chose in, I've got the same info as previously "Er ror starting Live TV - Device in Use - Check Cortana is not using your Win-TV-HVR-2200 Serial:0".

Windows Insider program | Apps on Insider preview

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

140 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2021-02-19T20:27:13+00:00

    Just let all know 21318 is no go

    Thanks. Fix is working its way through the process. Keep an eye on the blog posts when it's available. I'll make sure it's listed in the fixes section. I will also update this post.

    -Eddie

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2021-01-22T10:40:27+00:00

    Windows 10 v. 21296 + WinTV 10 v.39009 = still doesn't work

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2021-01-14T21:40:10+00:00

    The problem has now been raised at Microsoft and one of their team is experimenting using a Hauppauge USB tuner. I have asked for that person to advise me of their findings. Any information I get from that source will be made available through this forum.

    That good to hear

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2021-01-14T21:33:40+00:00

    The problem has now been raised at Microsoft and one of their team is experimenting using a Hauppauge USB tuner. I have asked for that person to advise me of their findings. Any information I get from that source will be made available through this forum.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  5. Anonymous
    2021-01-07T11:28:57+00:00

    To all frustrated souls...I have rediscovered a contact at Microsoft and have written to him asking for his help. He immediately was interested and asked me to describe the bug and send a description of it from an affected machine to the Feedback Hub. 

    I am unsure of what exactly he wants and I have already reverted to Windows 20279. I have asked him to provide further advice as to what I need to submit for Microsoft to be able to work on the problem.

    I have also had a fairly formulaic conversation with someone from Hauppauge who was sure that the problem I described was impossible he said

    "This doesn't make sense that its a Windows problem since the scanning

    routines are pretty simple: the application tells the tuner to tune to a

    particular frequency and then waits some time (usually 500 msec) for a

    signal lock to be detected. If signal lock is detected, then the frequency

    is added to the channel list"

    He seems to think that's all that happens - not that a frequency number has to coincide with a signal for there to be an output - and that is someone from the manufacturer. We are truly doomed (if that doesn't get you, the virus or US Politics will)!.

    As you can tell my hope for a solution lay with Microsoft.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments