SSMS 18.0 redraw issues when switching between multiple query windows
SSMS 18.0 redraw issues when switching between multiple query windows
Repro:
1. Open SSMS
2. Open a new query window and enter and execute a command, such as:
SELECT @@SPID;
- Open a second query window
- Using your mouse, switch back and forth between the two open query windows by clicking on their tabs.
- After several clicks (five to ten?), the content of the first window (query and result pane) may appear to be displayed in the second window, but you can't interact with any of the text.
- Switching back and forth a few more times may clear up the issue temporarily.
- The same issue may carry over to additional query windows which are opened, after switching between the various windows several times.

This issue was fixed (or better, mitigated) in SSMS 18.5
As you can see, SSMS will automatically prevent the Visual Studio Shell from using the h/w acceleration.
While I hear that for some of you this workaround did not help, it seems that for the vast majority of the people here it was beneficial, so the workaround has been baked into SSMS 18.5.
Thanks,
-Matteo
119 comments
-
Jeff commented
Never happened in 2017 but happens constantly in 18.2
-
Todd commented
It's only happens to me in SSMS 18 and 18.1, not VS 2017, 2019 or SSMS 17.x
-
Mark Burns commented
SSMS 18.1 Simple workaround: grab the scrollbar in the current tab/window and drag it - the window repaint the correct SQL and edits are enables properly.
-
Dean J. commented
It happens for me on these graphics cards: Intel HD 4600, and NVidia GT 240. It has never happened for me on Visual Studio 2015 or 2017.
It also happened in SSMS 16.x for me, but then got better in 17.x.
-
Tys commented
Disabling HW acceleration, for now, solves the issue, and I personally didn't experience any issue because of disabling this.
Here is the setting you are looking for:
https://sqlserver.pro/how-to-fix-sql-server-management-studio-graphics-problem -
Robert Woods commented
This was an issue in an old version of SSMS (maybe 13/14?), but has been fixed for a while for me. Suddenly in 18 it showed up again.
-
Chuck Hamilton commented
I have SSMS 17.9.1 and it does not show the same behaviour.
-
Glenn Burnett commented
@Matteo: I do not experience this issue with any of the following:
SSMS 17.9.1
Visual Studio Version 15.9.9
Visual Studio Version 15.9.14In testing all three of the above, the "Automatically adjust visual experience based on client performance" option was enabled, which auto-enables the "Enable rich client visual experience" and "Use hardware graphics acceleration if available" options.
Tests performed on same machine which does experience the issue with SSMS 18.0 and SSMS 18.1.
-
pbradshaw commented
I do NOT experience the problem in Visual Studio 2017, which I use every day. Version 15.9.14 with .NET 4.8.03752. I've never experienced this problem in any product other than SSMS 18.x
SSMS 17.9.1 has never exhibited this problem for me. It's what I use on a daily basis, since I found SSMS 18.x just too buggy and problematic to work with.
While I've seen reports from other people experiencing this problem with SSMS 16.x and up, I never have. This is all brand new to 18.x, and it happens so often it's impossible to use.
-
Garry Pshonik commented
@Matteo - SSMS 17.9.1 *does not* exhibit the behavior.
-
Lee commented
I am using SSMS v17.9.1 and do NOT have the same issues
Microsoft SQL Server Management Studio 14.0.17289.0
Microsoft Analysis Services Client Tools 14.0.1016.283
Microsoft Data Access Components (MDAC) 10.0.18362.1
Microsoft MSXML 3.0 4.0 6.0
Microsoft Internet Explorer 9.11.18362.0
Microsoft .NET Framework 4.0.30319.42000
Operating System 6.3.18362 -
Richard Kittrell commented
I have never experienced this issue in either VS 2017 15.9.14 nor SSMS 17.9.1. I use both of these daily. I have stopped using SSMS 18.1 until 18.2 becomes available.
-
Gordan Radovanovic commented
Have SSMS 17.9 and 18.1 on the same machine.
No issues with 17.9, only 18.1.
No issues with VS 2017 either. -
Rozenbaum Alexander commented
SSMS 17.9.1 works fine on the same machine
SSMS 18.1 glitches the same way as 18.0
P.S. I am not sure, but may be you have to know. Most of time I am running SSMS uder the different account than desktop logon. -
Graves Kilsgaard commented
I am using an Lenovo T480 with
- Intel UHD Graphics 620 & NVIDIA GeForce MX150I have to disable hardware acceleration in SSMS 18.0 else the system stalls and goes extremly slow.
As soon i am disabling Acceleration the system works fine but then i get the redraw issues. -
Anonymous commented
Intel HD Graphics 630 (driver 26.20.100.6890)
-
Petr Johánek commented
HP ProBook 650 G1 with dual Intel HD Graphics 4600 and AMD Radeon HD 8750M - permanently using Intel
-
Brandon Beeson commented
MSI Radeon HD 6950 Twin Frozr III
-
Anonymous commented
NVIDIA GeForce GTX 1050 Ti with Max-Q Design
-
Rozenbaum Alexander commented
Intel HD Graphics 630 (driver 21.20.16.4664)