The problem happens for me only after a reboot. One restart of SSMS fixes the problem ... until the next reboot.
There is some sort of link to VS, I just haven't had the shutdown/reboot patience to work out whether there is a sequence of doing things which avoids the issue.