This issue only occurs with a specific few releases in version 17.10, it ended up being a known bug that was fixed in later versions and is no longer in issue for recent builds. The solution if you encounter it is to upgrade VS.