I personally am on Windows Insider build 14366 when this issue first occurred. The issue does not occur on my other PC, a Surface Pro 3, which is on the official Windows 10 Pro release 1511. I know Insider builds are not officially supported, but this bug should be passed on to the development team as it will soon become a bug if it is still present when the Anniversary Edition is officially released next month if Stardock and/or Microsoft do not resolve it before then.