Build 21277 - Hauppauge WinTV software stopped work

Thanks for the info. I am in communication with Hauppauge but they, so far, haven't been very helpful. They don't seem to understand the problem as I have stated despite sending a screenshot of this Microsoft thread.

How do we get Microsoft to listen? Have you provided feedback on the Insider Feedback? There appears to be no one supporting my post on the matter.

I believe the problem is with in Windows and communication with tuner drivers because none of 3rdparty app even work, just keep file bug report on feedback I'm sure it will get fix sooner or later.

I downloaded windows preview 21286.1000rs today and the same problem still exists so have gone back to Build 20279.fe again and everything  is fine  I have sent feedback to Microsoft

To all frustrated souls...I have rediscovered a contact at Microsoft and have written to him asking for his help. He immediately was interested and asked me to describe the bug and send a description of it from an affected machine to the Feedback Hub. 

I am unsure of what exactly he wants and I have already reverted to Windows 20279. I have asked him to provide further advice as to what I need to submit for Microsoft to be able to work on the problem.

I have also had a fairly formulaic conversation with someone from Hauppauge who was sure that the problem I described was impossible he said

"This doesn't make sense that its a Windows problem since the scanning

routines are pretty simple: the application tells the tuner to tune to a

particular frequency and then waits some time (usually 500 msec) for a

signal lock to be detected. If signal lock is detected, then the frequency

is added to the channel list"

He seems to think that's all that happens - not that a frequency number has to coincide with a signal for there to be an output - and that is someone from the manufacturer. We are truly doomed (if that doesn't get you, the virus or US Politics will)!.

As you can tell my hope for a solution lay with Microsoft.

To all frustrated souls...I have rediscovered a contact at Microsoft and have written to him asking for his help. He immediately was interested and asked me to describe the bug and send a description of it from an affected machine to the Feedback Hub. 

I am unsure of what exactly he wants and I have already reverted to Windows 20279. I have asked him to provide further advice as to what I need to submit for Microsoft to be able to work on the problem.

I have also had a fairly formulaic conversation with someone from Hauppauge who was sure that the problem I described was impossible he said

"This doesn't make sense that its a Windows problem since the scanning

routines are pretty simple: the application tells the tuner to tune to a

particular frequency and then waits some time (usually 500 msec) for a

signal lock to be detected. If signal lock is detected, then the frequency

is added to the channel list"

He seems to think that's all that happens - not that a frequency number has to coincide with a signal for there to be an output - and that is someone from the manufacturer. We are truly doomed (if that doesn't get you, the virus or US Politics will)!.

As you can tell my hope for a solution lay with Microsoft.

The thing is what ever MS has changes in 212177 is root caused because I test every 3rdparty from java and non dot.net app and not single one of them even work and it seem to me the OS is blocking the apps or at driver level from working and wonder if it a similar problem that Camera access had after all it to was a problem to a few years back.

Same issue as everyone, hauppauge usb stick tuner, cant scan chans with latest test versions