SSMS 17.3 Font and Color setting limit changes to 4 areas
After upgrading to ver. 17.3 of SSMS 2017, I am unable to enlarge the default font size used for grids or the object explorer (Environment Font). After running a search I several posts in the SQL Server Forum, but after trying the fix mosts sided, which was uninstalling 17.3, then install 17.2 and do the upgrade to 17.3. This was ineffective for me and others.
Under "Show settings for:" instead of listing all the options that should be listed, I see only the following. This is obviously a bug. Has anyone found a solution that fixes this problem?
Please, install SSMS 18.x (currently SSMS 18.2) which should not present this issue anymore.
Mario Ramos commented
That's weird. I also have the problem.
There are not steps to reproduce, just try to change fonts and color, e.g. the comments color. It doesn't allow you to change but basic features.
Ann W commented
Is there any plan to fix this? It has been around for a long time. Having to install an old version and then upgrade is not a good solution.
Mikael Wedham commented
I also have had the same issue. And still do. Installed yesterday with same result.
It is definately reproduceable. I got a new Surface Pro. Installed SSMS and same result!
The things available in Options - Fonts and Colors are:
[All Text Tool Windows]
[Watch, Locals, and Autos Tool Windows]
Importing settings from a really old SSMS where I could change and export works, but I would really like to be able to change the settings myself.
1. I installed a lot of versions up to ( and including 17.9) on a Clean reset Windows 10 OS.
2. I have upgraded also on other Machines - only full install package.
Never uninstalled and reinstalled. I reset the entire OS.
It is a bug that present in all SSMS 2017 builds including 17.7
I opened a SR 118050818144681 with the MS Premium Support.
The problem is happening because the entire registry branch is missing:
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\SQL Server Management Studio\14.0\FontAndColors\Cache]
SSMS Repair procedure in the Control Panel doesn't fix the issue.
That's incredibly odd. We get this, albeit frustratingly intermittently, of MacBooks running Windows, and HP Gen 9 servers running Windows Server 2016. We have even completely wiped the server back to "nothing but the OS from a fresh image" and the install of 17.6 still failed to evidence the options. That does include removal of the VS2015 Isolated Shell (followed by windows reboot just be sure).
My MacBook colleague has stripped off every vestige of every version of Management Studio from her laptop. The process of installing the 17.0 then the upgrade still met with "no options".
I have run a powershell script that one of the SQL Gurus, maybe Aaron or Erland, supplied, that scanned the registry for everything to do with SSMS, and iteratively removed all artifacts, dependent artifacts, and topmost. That was painful. Still had issues.
May I suggest that rather than repeatedly attempting to reproduce the issue, you find out what is missing from the multiple failed installs I have available even now. Having detected the missing items/registry entries, set up a simple .reg script that puts a standard deployment set of entries in the registry in the event a consumer has these issues, and there are quite a few of us judging by the MSDN Forum posts on the subject. We can then import a settings file from a "good" install on another box, and the result of the .reg + Import should be "all options are available".
How say you?