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 No comments

140 answers

Sort by: Most helpful
  1. Anonymous
    2021-02-17T14:07:39+00:00

    A drag indeed. Great minds at Microsoft and Hauppauge seem to have a problem. I am no software expert but I know that something changed in 21277 and that should be identifiable. What was that change implemented - what benefits were supposed to be obtained? Surely that change could be reversed.

    The world is burning and Microsoft can't fix a video issue. Is there any hope?

    We believe we have identified the root cause and are working on a fix. Unfortunately, these things take time to get from triage to releasing a fix when it comes to operating system changes. If this feature is important I suggest you continue to pause updates until a build with the fix is released.

    -Eddie

    The problem is not specific to Hauppauge.  I am experiencing the same problem with 2 different DVB-TV usb sticks. 1 of them is a MyGica and the other is an old Apex unit.  Both of them worked just fine until 20279, and from there on, started giving the error messages that the units were being used or not available. 

    I am hoping for a quick fix as I need the TV input for my daily work.

    Tks.

    We're working on it. We also don't recommend running Dev Channel builds on critical systems.

    -Eddie

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-02-13T17:42:39+00:00

    Despite my moaning, I appreciate you are working on the issue. I am unfamiliar with software development processes and possibly underestimate the time required to problem solve and then implement fixes.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-02-13T15:54:40+00:00

    Thank you for letting us know. But if this is the case, why isn't the issue acknowledged in the list of unresolved issues?

    Appreciate the feedback here. Unfortunately, we can't list every known issue in the blog posts. When the fix is included, it will be noted in the blog post.

    -Eddie

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2021-02-13T15:52:59+00:00

    A drag indeed. Great minds at Microsoft and Hauppauge seem to have a problem. I am no software expert but I know that something changed in 21277 and that should be identifiable. What was that change implemented - what benefits were supposed to be obtained? Surely that change could be reversed.

    The world is burning and Microsoft can't fix a video issue. Is there any hope?

    We believe we have identified the root cause and are working on a fix. Unfortunately, these things take time to get from triage to releasing a fix when it comes to operating system changes. If this feature is important I suggest you continue to pause updates until a build with the fix is released.

    -Eddie

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2021-02-13T15:33:14+00:00

    Who knows, maybe Microsoft. Suffice to say that I am confident - because of my communication with both Microsoft and Hauppauge - that they are investigating the problem. The amount of gusto being applied to find a solution is unknown to me.

    It not on Hauppauge end it what ever had change in 21277 this is MS doing

    Was this answer helpful?

    0 comments No comments