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-13T02:32:58+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?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2021-02-12T22:22:13+00:00

    Windows Build 21313 - WinTV still doesn't work

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2021-02-04T15:00:25+00:00

    Hi,

    The issue is when building any DVB Graph (DVB-T, ATSC, QAM etc) on any product. Analog graphs works ok.

    Microsoft Network Provider -> Tuner -> TS Capture

    The underlying issue is "Access Denied"

    I wonder if Microsoft is adding a new feature like "Camera Access Control" but for BDA TV Tuners, but hasn't build the Privacy UI yet to turn it on/off?

    I submitted a bug here. Feel free to upvote.

    https://aka.ms/AAalprh

    This is still present with the latest update Build 21301.rs_prerelease.210123-1645. I just installed KB5000626

    Jon Sayers

    Software Engineer

    Hauppauge Computer Works, Inc

    Image

    Jon,

    Thanks for the details here and for filing the feedback! Let me see if I can get this to the right people internally.

    -Eddie

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2021-02-04T12:30:33+00:00

    I can't claim to understand the issues you have raised but I appreciate your investigation into this matter. Apart from upvoting your comment - are there any other ways we can interact with Microsoft to encourage a degree of urgency with this matter.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2021-01-21T18:30:49+00:00

    I can report that Microsoft are actively involved with looking at the problem now. I received a response from Fred at Hauppauge (I believe he is a lead developer) who confirms the problem exists and suggests that as many "Insiders" as possible raise the issue with  Microsoft.

    I'm petty sure fred not the lead developer there I know must of them there.

    Like I sad for now just keep bug report on Feed Hub sooner or later MS will get to bottom of this.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments