Shouldn't everything be documented here to follow through from the original issue? Shouldn't it stay here due to the extreme age of the thread to demonstrate that M$ hasn't effectively solved this issue? I am having the same problem on a freshly installed windows 10 pc. Everything looked just fine in 8.1 on this exact same hardware. All drivers are up to date, tried all of the proposed solutions that had no effect on the issue at hand. Someone going to do something about this? It is clearly a wide spread issue that needs to be addressed.
Absolutely, it's a computer wide issue and it's happening on different programs so it's a W8.1/10 bug, not a specific program issue. I do agree that if you're having a different problem than what we're experiencing then please create a separate thread.