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)

Answer accepted by question author

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 128.7K Reputation points MVP Volunteer Moderator

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.

Javier Gideon "Vince" M Reyes 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.

Anonymous

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

Saved my day. Thanks.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

11 additional answers

VladyslavQA 1 Reputation point

2021-02-09T14:10:50.26+00:00

I got the same problem, reinstall VS reset the settings, log out of the account, nothing helps. Cannot move tabs, test window tab cannot be docked to program window
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Justin G 1 Reputation point

2021-02-09T19:04:47.76+00:00

Hi @Zoomy , this is also started suddenly happening to me in VS2017, which lead me to believe a windows update was to blame rather than the software itself.

Please see: https://developercommunity.visualstudio.com/content/problem/1323017/unexpected-vs-crash-when-docking-or-splitting-wind.html

MS has identified KB4598301 as the root cause and offers some work arounds for VS, which may also apply to SMSS.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Zoomy 261 Reputation points

2021-02-10T14:34:12.52+00:00

Thanks for the answers. I suspected it might be the result of a recent Windows Update, as you've suggested. Unfortunately, I don't see any of the exact KB* updates you mention on my machine. I'm running Windows Server 2019 Standard, Version 10.0.17763 Build 17763, if that helps. Are the update numbers different for Windows Server? Regardless, I did another update just now hoping that a patch might have made it into the latest package of updates, but to no avail - SSMS still crashes when I manually un-dock and then attempt to re-dock a tab.
Please sign in to rate this answer.
VladyslavQA 1 Reputation point

2021-02-10T14:37:23.253+00:00

Try to make the changes indicated in this thread, my problem was solved

https://developercommunity.visualstudio.com/content/problem/1323017/unexpected-vs-crash-when-docking-or-splitting-wind.html

Find the file "devenv.exe.config" and add the value - ";Switch.System.Windows.Interop.MouseInput.OptOutOfMoveToChromedWindowFix=true;Switch.System.Windows.Interop.MouseInput.DoNotOptOutOfMoveToChromedWindowFix=true"
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Zoomy 261 Reputation points

2021-02-15T23:13:40.773+00:00

Thanks also to @Erland Sommarskog and @VladyslavQA for their replies. It's quite possible that your suggestions would've also fixed the issue, now that I've had a chance to read the entire thread. Your help is greatly appreciated.
Please sign in to rate this answer.
Erland Sommarskog 128.7K Reputation points MVP Volunteer Moderator

2021-02-16T21:55:52.587+00:00

I think Vinnie's solution is the best one. Uninstalling the KB means that you probably lose on some other fixes. Plus I suspect that Windows would nag us about this update again and again.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

SSMS 18.8 crashes when re-docking tabs

11 additional answers

Your answer