![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(160, 21%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
Hi Speedy_13,
I would use the FBH, post a link back here for Eddie and contact Hauppauge they might have beta drivers to install.
Build 21277 - Hauppauge WinTV software stopped work
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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
2020-12-17T23:06:10+00:00 I had the same problem so reverted to older build to get the tv to work. Have stopped windows updates. hope to hear this is fixed soon.
-
Anonymous
2020-12-18T02:35:42+00:00 I too have reverted. The problem is that we will probably never know if the problem gets solved in later builds unless we try it out.
It would be better if we were able to communicate more directly with Microsoft. I posted the problem on the Insider Feedback but last time I looked I was the only person that had. I wonder if Microsoft take any notice of issues where only one user mentions it,
-
Anonymous
2020-12-18T16:04:06+00:00 I always wonder if they pay any attention also. This is he first time I have had a problem like his with any updates. Thanks for the reply. Nice to know I am not the only one with this problem. That way its not just me and maybe my system. Happy Holidays. Be safe.