Seen the same issue in SSMS 2014, the temp fix we found was to run regsvr32 "C:\Program Files (x86)\Common Files\Microsoft Shared\VS7Debug\coloader80.dll", but I doubt that's a viable solution for every installation!

We have a fix for this problem in our latest Visual Studio Preview release. If you'd like to try out the fix, you can obtain early access to the preview build here: https://www.visualstudio.com/vs/preview

Hi Dan, Can you create a new report by using Report A Problem in Visual Studio (It's on the Help Menu under Send Feedback) since this issue has been closed for a long time? Thank you for your patience.

This issue has been fixed and is now available in our latest update. You can download the update via the in-product notification or from here: https://www.visualstudio.com
Thanks to everyone who provided feedback and votes.

Hi. It's July 2017 and I've the same problem now. Few days ago I've uninstall VS 2017 Community, Sql Server, SSMS and reinstall them hoping this would have fixed it but it didn't. Is there anything may I look into to fix this problem? Every time I have to exit SSMS, perform regsvr32 "C:\Program Files (x86)\Common Files\Microsoft Shared\VS7Debug\coloader80.dll" and restart SSMS. Thank you

See https://developercommunity.visualstudio.com/content/problem/18997/vs-2017-community-breaks-visual-studio-2008-a-visu.html and https://developercommunity.visualstudio.com/content/problem/3678/maybe-urelated-but-ssms-err-when-debugging-sp-afte.html and probably others.