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.
Build 21277 - Hauppauge WinTV software stopped work
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.
140 answers
Sort by: Oldest
-
Anonymous
2021-01-14T21:33:40+00:00 -
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
-
Anonymous
2021-01-14T22:34:11+00:00 great news, thanks.
-
Anonymous
2021-01-21T18:07:08+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.
-
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.