• I am seeing the same thing with a recent install of SSMS 2016 on my workstation as well. Did you ever determine the cause or a fix?

    JB