SQL SERVER – SQL Server Configuration Manager Missing from Start Menu

Earlier I wrote a blog on the same topic and today I found another way to do the same thing. In this blog, we would discuss the steps you can take to open SQL Server Configuration Manager when its missing from Start Menu in the Windows operating system.

Before I begin, here is my earlier blog on the same topic with one solution. How to Find Missing SQL Server Configuration Manager? – Interview Question of the Week #089

Instead of searching, you can also get the file in C:\Windows\System32 folder.

SQL Server 2008SQLServerManager10.msc
SQL Server 2012SQLServerManager11.msc
SQL Server 2014SQLServerManager12.msc
SQL Server 2016SQLServerManager13.msc
SQL Server 2017SQLServerManager14.msc
SQL Server 2019SQLServerManager15.msc

Here is the folder and the file from my latest lab server of SQL Server 2019.

SQL Server 2016 Configuration Manager.

If you hate to open this file manually then you can create a shortcut using below steps.

  1. Open MMC.exe by going to Start > Run > mmc.exe
  2. In the menu bar, go to “File” and choose “Add/Remove Snap-in”
    Add/Remove Snap-in.
  3. That would open a new window and we need to look for “SQL Server Configuration Manager”. Highlight that and hit “Add”
    Snapping in windows snap-ins.
  4. And then hit OK.
    Snapping in sql server configuration manager.

This would open the SQL Server Configuration Manager.

SQL Server Configuration Manager.

Another method would be to create a shortcut for the below program.

C:\Windows\SysWOW64\mmc.exe /32 C:\windows\SysWOW64\SQLServerManager15.msc

You need to change the highlighted name based on the version of SQL Server.

Published by Pinal Dave on SQLAuthority. More of my work at pinaldave.com.

Registry, SQL Server, SQL Server Configuration, Starting SQL, Windows
Previous Post
SQL SERVER – SQL Service Not Getting Started Automatically After Server Reboot While Using gMSA Account
Next Post
SQL SERVER – FIX: The specified instance of SQL Server is hosted by a system that is not a Windows Server Failover Cluster(WSFC) Node.

Related Posts

13 Comments. Leave new

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.