Been a while since I checked this thread. Strangely enough, sometime in summer of 2014, it began to work. I believe after a Microsoft update. You know, Microsoft, the guys who never admit to anything being wrong; act like dummies when you try to explain even though dozens of other people have complained about it, they never heard of it and have you chasing all over the place checking settings that really have nothing to do with your problem - and then suddenly it begins to work after an update.