I'm getting a very strange error when I try to launch SSMS from my taskbar. It seems to open in normal speed, but responds to any input with just a beep. CPU usage is 0% in Task Manager, and there is no [not responding] message.
It doesn't respond to a right-click & close all windows command from the taskbar, but "End Task" from task Manager does kill it.
When I launch from the command line and specify the server using the -S switch & use Windows Auth using -E it runs fine.
This might be a very simplistic answer, but this happened to me because a dialog it was attempting to present was off of the desktop and/or hidden behind something else.
When it beeps like that, can you do the whole "Alt-Space m" and move something into focus?
The 'Connect to Server' window is off-screen. If you use Alt+F4, it will close the dialogue but keep Management Studio open. After this you can initiate a new dialogue through the menu and connect to the desired server.
After closing, the 'Connect to Server' window should appear inside of the main window the next time you start the program.
I had this same problem today and none of the solutions here worked, since it was not the connection dialog, but a different one hiding.
I went to the task manager and right-clicked on the dialog and selected "Bring to Front".
I hope this helps others!
This morning i have experienced the exact same unresponsive SSMS (No keystrokes function, have "End Task" via "Task Manager").
My environment is similar to those indicated above; Surface Pro 3 w/ 2 additional monitors (total of three).
After killing SSMS, moving SSMS to monitor #1 before closing it works. When I re-open SSMS the dialogue box properly appears on monitor #1. I can then move SSMS to monitor #2 or #3.