Been a longtime fan of Shark's codecs (but NOT the unwanted extras, obviously) so I actually already have them installed.
But I don't think this is a codec issue since a Surface Pro at Best Buy with nothing extra on it had the same issue. And so have a lot of users I've read in several forums.
I'm starting to think that certain builds of Windows 10 have this issue while others don't. My build is 10240, upgraded from 8.1 (which didn't have this issue).
Given the various posts I've seen here about the bug, MS must know about it. Let's hope a fix will come soon.