Yes, restart is the only solution sometimes. And pictures are speaking a thousand words here…

1_SQL_Server_Restart_is_the_only_solution_Well_sometimes

SSMS has been keeping very busy lately, for hours !

2_SQL_Server_Restart_is_the_only_solution_Well_sometimes

Object Explorer does not recognize Start, Stop, etc – for the time being !

3_SQL_Server_Restart_is_the_only_solution_Well_sometimes

SSMS runs out of steam, tired of being busy, though there is enough available memory on the box.

4_SQL_Server_Restart_is_the_only_solution_Well_sometimes

Last but the not the least: Configuration Manager’s TRY/CATCH comes into play.

Services.msc? same as Object Explorer: cant start, stop or pause SQL service.
Solution: Start -> Restart !