There was an update on
VS Connect.
It now looks likes it's now being handled as an application issue as we first hinted.
"Posted by Mark [MSFT] on 23/09/2016 at 22:41
Thank you for reporting your issue with Visual Studio. This issue has now been fixed, and will be released with (the next update) to Visual Studio."