Ha. This thread is anything but quiet on the inside - I got probably 30+ mails from various people in positions to make changes just yesterday, and people here worked over the weekend to try to troubleshoot.
The issue is that when we get reports like this from a place like The Green Button, they're not quantified. Like, maybe the 5 or 10 people on this thread are the ONLY ones experiencing the problem - certainly not a single OEM has reported it to us - so we don't know how to measure that against other issues that come up.
So it would be super-helpful if people sent me private messages and told me exactly what tuner and if you can find out what driver version you're using - and then any additional information about how many channels are found in the scan, how many work, etc. This especially applies to lurkers. :-)
I'm not sure how well-known this is, but in order to get an update (fix) out via Windows Update, we have to go through a TON of process - first convince our management, then the Media Center sustained engineering team, then the Windows sustained engineering team, and so on. The impact has to be very significant to get something out, because with every change we make to a supposed stable, shipped product, we run the risk of regressing something else. All this is a long way to say I have to do quite a bit of homework in order to make something happen that you see, and I'm willing to do it if you're willing to help me.
One thing that helps is knowing exactly what cards you're seeing the problem with; once we know which cards, we can find out internally approximately how many have sold and where, and we can make good guesses as to how many people are potentially affected.
This posting is provided "AS IS" with no warranties, and confers no rights.