The problem still persists in 4.16.3-release with VS 2017 Community 15.2 (26430.16). The suggested fix below works.