If you upgraded your Windows 10 machine from an earlier version of Windows 10, and are running Visual Studio 2015, this post describes a workaround to a known issue. If you installed Windows 10 cleanly, or upgraded directly from Windows 7 or 8.x, then there is no issue, feel free to skip this post.
Once again, thanks to the efforts of users ...