Appearance
VersionSQL menu missing in SSMS 21/22 (non-standard install path)
VersionSQL registers itself with SSMS 21/22 by copying a small "package definition" file (.pkgdef) into SSMS's Extensions folder. If SSMS 21/22 is installed in a non-default location, the installer may not detect it and the .pkgdef files remain in the VersionSQL install folder.
Symptoms
- VersionSQL installed successfully, but it does not appear in SSMS 21/22.
- Reinstalling does not help.
Where the installer leaves the PKGDEF files
If SSMS 21/22 is not detected, the files are left here:
- SSMS 21:
C:\Program Files (x86)\VersionSQL\VersionSQL.pkgdef - SSMS 22:
C:\Program Files (x86)\VersionSQL\VersionSQL22.pkgdef
Step 1: Identify your SSMS install path
The easiest way is to locate SSMS.exe:
- Start menu → search "SQL Server Management Studio"
- Right-click → "Open file location"
- Right-click the shortcut → "Open file location" again
- Locate
SSMS.exeand copy its full path - The extension folder is next to
SSMS.exeunderCommon7\IDE\Extensions.
Step 2: Copy the PKGDEF file into the SSMS Extensions folder
Before copying:
- Close SSMS completely.
- You may need administrator rights to write under
C:\Program Files\....
For each SSMS version you use:
- Create this folder if it doesn't exist:
<folder containing SSMS.exe>\Extensions\VersionSQL\
- Copy the correct
.pkgdeffile into that folder and ensure the destination file name isVersionSQL.pkgdef.
That means:
- SSMS 21
- Copy
C:\Program Files (x86)\VersionSQL\VersionSQL.pkgdef - To
<folder containing SSMS.exe>\Extensions\VersionSQL\VersionSQL.pkgdef
- Copy
- SSMS 22
- Copy
C:\Program Files (x86)\VersionSQL\VersionSQL22.pkgdef - To
<folder containing SSMS.exe>\Extensions\VersionSQL\VersionSQL.pkgdef(rename on copy)
- Copy
Example destinations (default installs):
- SSMS 21:
C:\Program Files\Microsoft SQL Server Management Studio 21\Release\Common7\IDE\Extensions\VersionSQL\VersionSQL.pkgdef
- SSMS 22:
C:\Program Files\Microsoft SQL Server Management Studio 22\Release\Common7\IDE\Extensions\VersionSQL\VersionSQL.pkgdef
Step 3: Rescan extensions (SSMS 22 only)
SSMS 22 does not scan for extension changes on startup. After copying the file, run once in an administrator command prompt:
"<full path to SSMS.exe>" /setup
Then start SSMS normally again.
Verification
- Restart SSMS.
- Confirm VersionSQL appears in the UI.
If it still does not load:
- Run SSMS with
/logand checkActivityLog.xmlfor package load errors. - Contact support at
[email protected].