You are here:   Blog
Register   |  Login

Blog Archive:

* Can be used in order to search for older blogs Entries

Search in blogs

Blog Categories:

* Can be used in order to search for blogs Entries by Categories

Blog Tags:

* Can be used in order to search for blogs by keywords


Awared MVP


Microsoft® Community Contributor 

Microsoft® Community Contributor

 Read this before you use the blog! Maximize

Recent Entries


Written by: ronen ariely
28/05/2019 01:42 RssIcon

Hi guys,

Did you encounter issues with opening SQL Server Management studio version 18?

The online and offline communities discuss this issue in the last several months. You can find reports like: SSMS not run, SSMS closes immediately after startup, SSMS won't open, and so on...

Well... this blog only summarize the issue and provide the updated solution (better say "workaround")!
Everything I write in this blog is not original but summarize. You can check the following link if you want to follow the entire discussion about this issue.

This is known issue and there is new official workaround which published by the SSMS developers team.

You can view the open ticket at Microsoft feedback system in the following link: https://feedback.azure.com/forums/908035-sql-server/suggestions/37502512-ssms2018-installed-but-will-not-run

Short history:

The first workaround which was presented was to copy the file: Microsoft.VisualStudio.Shell.Interop.8.0.dll

from the directory: C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\PrivateAssemblies\Interop

into the directory: C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\PublicAssemblies

Later, a more focused solution was published: Simply remove the file C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\CommonExtensions\Platform\Microsoft.VisualStudio.MinShell.Interop.pkgdef

Note! The above solution is what I used and what I provided as a workaround which solve the issue for me. 

Anyhow, several days ago the team publish an update as you can see in the link above. This is a quote from the official updated response:

The recommended workaround, in the interim, is:
1) Close all instances of SSMS
2) Edit ssms.exe.config
3) Remove the line that has the following text (should be line 38): NgenBind_OptimizeNonGac enabled=“1”
That’s the same change that will be in the next release of SSMS 18.x

Note! the location of ssms.exe.config file is in the folder: C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE


I hope that this will help you solve the issue.
For more information please check the original post at Microsoft's feedback website.

Update: The fix for this issue was included in SSMS 18.1.