SSMS 18.8 crashes when re-docking tabs

Zoomy 261

When I un-dock a tab in SQL Server Management Studio and later attempt to re-dock it, SSMS crashes. This happens every time, and I can reproduce the problem at will. All I have to do is un-dock a tab (let's say, in order to view two SQL queries in different tabs side-by-side) and then attempt to re-dock it, and SSMS will crash. Looking at the Event Viewer, I find two successive error messages each time the crash happens (see the pasted messages below).

Please fix this! It's wreaking havoc on my usual workflow. Thanks.

Message #1:

Application: Ssms.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.NullReferenceException at System.Windows.Interop.HwndMouseInputProvider.HasCustomChrome(System.Windows.Interop.HwndSource, RECT ByRef) at System.Windows.Interop.HwndMouseInputProvider.GetEffectiveClientRect(IntPtr) at System.Windows.Interop.HwndMouseInputProvider.PossiblyDeactivate(IntPtr, Boolean) at System.Windows.Interop.HwndMouseInputProvider.Dispose() at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef)

Accepted answer

Vinnie Amir 376 Reputation points

2021-02-15T21:58:59.813+00:00
Fix:

Close all SSMS windows, and find your SQL Mgt Studio EXE file, mine was in:

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

If you cant find it, right click your shortcut you use to open SSMS and go Properties > Open File Location

Once you have found this, you will also find a file called "Ssms.exe.config, open up a Notepad in Administrator Mode, and edit this file

You will then need to find an xml tag called <AppContextSwitchOverrides>, and APPEND (not replace) the following exactly:

;Switch.System.Windows.Interop.MouseInput.OptOutOfMoveToChromedWindowFix=true; Switch.System.Windows.Interop.MouseInput.DoNotOptOutOfMoveToChromedWindowFix=true

And that is it. You will now avoid this nasty crash

https://support.microsoft.com/en-us/topic/february-9-2021-kb4601060-cumulative-update-for-net-framework-3-5-and-4-7-2-for-windows-10-version-1809-and-windows-server-version-2019-b240d07e-639f-d708-98c9-0cbe443176aa
Please sign in to rate this answer.

57 people found this answer helpful.
Erland Sommarskog 101.4K Reputation points MVP

2021-02-15T22:22:09+00:00

Thanks a lot for posting these detailed instructions! But you should convert this to an answer, so that Zoomy can accept it, if he likes.

Zoomy 261 Reputation points

2021-02-15T23:11:36.19+00:00

Hi @Vinnie Amir , thanks a lot for the detailed instructions. I followed your instructions exactly and then retested, and the issue seems to be fixed. I was hesitant to try some of the other answers because they didn't specifically target SSMS even though they were apparently on the right general track. As @Erland Sommarskog said, if you would please convert this to an answer then I will accept it. Thank you very much for taking the time to reply.

Vinnie Amir 376 Reputation points

2021-02-16T02:19:40.237+00:00

Done, sorry, first time using this site, I did this in a rush. It is done, and I am glad I can save other the frustration.

Rrrr 11 Reputation points

2021-02-16T19:47:43.46+00:00

Thanks for this! I know VS2019 Professional was having this issue too, but they already patched it. I was surprised this hasn't been patched yet!

AlexanderK79 11 Reputation points

2021-02-18T06:51:22.337+00:00

Thank you so much! This prevents a lot of annoyance :-)

Alfredo Quimbayo 6 Reputation points

2021-02-18T19:39:47.997+00:00

Thanks a lot

Jake Warren 11 Reputation points

2021-02-22T06:03:46.057+00:00

Thanks, worked for me too.

In my case, this problem came about immediately after I modified the SSMS installation which added components from VS. I didn't realize how much I depend on re-docking SSMS windows until I had this problem.

Thanks again!

SamZen 36 Reputation points

2021-02-22T11:52:56.08+00:00

Thanks It worked. I changed the following file.
C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\ManagementStudio\Ssms.exe
with the following xml tag between the <runtime>.
<runtime>
<AppContextSwitchOverrides value="Switch.System.Windows.Interop.MouseInput.OptOutOfMoveToChromedWindowFix=true; Switch.System.Windows.Interop.MouseInput.DoNotOptOutOfMoveToChromedWindowFix=true" />
</runtime>

GregN 6 Reputation points

2021-02-24T18:45:03.95+00:00

worked great! thanks

Stephen Elmer 11 Reputation points

2021-03-04T15:19:56.003+00:00

thanks for this. my .config file did not even have this element, so i wasn't even sure where it should go. thank you!

Barbara 6 Reputation points

2021-03-08T15:38:37.17+00:00

Thank you so much, this worked for me!!!

Jason Maroney 6 Reputation points

2021-03-10T16:33:36.34+00:00

Thank you soooooo much VinnieAmir. I just recently got a new computer and experienced this issue for the first time. I have been using the latest version of SSMS and never had this issue until now. Was so angry about this because of the crashing and the fact I hated Object Explorer on the left side. You saved my new computer from being angrily destroyed.

Anderson 6 Reputation points

2021-03-24T11:57:36.907+00:00

Thanks a lot.
It worked perfectly here

Ian Sawyer 6 Reputation points

2021-03-29T13:25:44.363+00:00

This also fixed a similar issue I ran into. After a reboot my Object Explorer and Properties boxes opened outside the SSMS window. When I tried to redock either, SSMS crashed and restarted. This was also consistent and easily reproducible until I applied this fix.

me@javier-gideon-m-reyes.com 6 Reputation points

2021-04-06T09:31:22.85+00:00

Vinnie Amir you rock. Thanks for the share. It worked.

grantfitz 6 Reputation points

2021-05-13T21:53:21.587+00:00

Thanks Vinnie. This has been bothering me for months. Every time I'd try to re-dock, I thought to myself, "maybe it'll work this time" and it never did. Updated the config file as you stated and had no issues.

Hong Shen 6 Reputation points

2021-09-29T14:14:40.677+00:00

Saved my day. Thanks.
Sign in to comment

11 additional answers

Erland Sommarskog 101.4K Reputation points MVP

2021-02-09T20:08:42.027+00:00

I got a tip from an MVP colleague that a KB update could be a problem just like Justin suggests. It appears that there are two of them, KB4598299 and KB4598301. I have KB4598299 on two machines, and I see the crash on both. I also get the same crash in Visual Studio 2017 - quite expected, since SSMS uses the VS2017 shell.

I uninstalled KB4598299 on of the machines, and after the uninstall, I don't get the crash, so that appears to be the solution.
Please sign in to rate this answer.

1 person found this answer helpful.
Erland Sommarskog 101.4K Reputation points MVP

2021-02-09T21:06:21.717+00:00

KG4598299 is a preview. Today is patch Tuesday and the "real thing" is available, KB4601050. This update has the same issue. Don't install it if you like to undock and re-dock tabs. (I don't do this myself very often, but I see the point.)
Sign in to comment
Erland Sommarskog 101.4K Reputation points MVP

2021-02-10T22:33:24.607+00:00

I don't know for sure, but I assume that there are different KBs for server OSs.

In any case, it is the .NET update for 2021-02 you want to get rid of. The final one came yesterday, and then there was a preview last week.

I had a little trouble finding these myself, but they are hiding under Other Updates in the View Update History.
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment
Erland Sommarskog 101.4K Reputation points MVP

2021-02-08T23:01:27.29+00:00

I was able to repeat that. On the first attempt.

You can report bugs on https://feedback.azure.com/forums/908035-sql-server.
Please sign in to rate this answer.
Zoomy 261 Reputation points

2021-02-08T23:42:23.657+00:00

Thanks for confirming. I also reported the issue on feedback.azure.com, but have not received a response yet.
Sign in to comment
CathyJi-MSFT 21,096 Reputation points Microsoft Vendor

2021-02-09T05:50:22.84+00:00

Hi @Zoomy ,

It works well in my environment, I am using SSMS 18.8. On the menu bar, select Window, then Reset Window Layout. This will place object explorer to its original position.

Or right click on object explorer, now you can see an option called "Dock", select "Dock". By this object explorer comes to normal position as earlier.

For SQL query windows tab, it also works well in my environment, I can move them back as earlier.

Did you try to use SSMS 17.9.1 or SSMS 18.7.1? you can get them from here.

If I misunderstood your issue, please let me know.

If the response is helpful, please click "Accept Answer", thank you.
Please sign in to rate this answer.
Zoomy 261 Reputation points

2021-02-09T13:59:25.87+00:00

I think you may have misunderstood the issue. In a tabbed window layout, simply try manually clicking-and-dragging one of the docked (its default) tabs away from the main SSMS window (i.e. undocking it). Then release your mouse button, wait a second, then click-and-drag the newly-undocked tab back into the main tab bar (i.e. re-dock it). This is the point at which SSMS routinely crashes for me.

Zambetti,Bruno,ISSY-LES-MOULINEAUX NF,NCE 1 Reputation point

2021-03-25T14:31:00.78+00:00

Yes!

I cannot be admin, then cannot use the solution.
I tried to find the button in Windows tab, but di not find. Thn I customize the menu, I found in french "rétablir la disposition de fenêtre" and click on it, restored the original layout with the object explorer.

very annoying crash, when yo undock the object explorer and want to redock it.

SaintFrag 1 Reputation point

2021-05-21T14:50:28.03+00:00

17.9.1 has the same issue.
Sign in to comment