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.
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: Most helpful
-
Anonymous
2021-01-21T18:07:08+00:00 -
Anonymous
2021-01-14T22:34:11+00:00 great news, thanks.
-
Anonymous
2021-01-14T13:06:00+00:00 I have done that as have a couple of other people. Not that it seems to matter.
Just keep at it sooner or later it will get address
-
Anonymous
2021-01-14T13:05:06+00:00 Yep, are you all also getting NTFS thorn write errors?They wrote it was fixed it 21292, but its still not..
-
Anonymous
2021-01-14T12:58:14+00:00 I have done that as have a couple of other people. Not that it seems to matter.