Activity overview
Latest activity by mike.hodgson
I have the same issue as everyone else. While troubleshooting I came across this thread that reiterates that Microsoft updated the Microsoft.Data.SqlClient library that SSMS v22.3.0 now uses: https://www.sqlservercentral.com/forums/topic/ssms-22-latest-update-crashing I also sent some troubleshooting info to Claude (Anthropic) and it came back with: -------------- The Real Problem: SSMS v22.3.0 upgraded its internal Microsoft.Data.SqlClient assemblies to a newer version. Your Redgate SQL Toolbelt extension was compiled against the old assembly versions, so when Object Explorer loads (which triggers extension initialization), the extension can't find the assemblies it expects → crash. The "ClientRights" error is likely a red herring - it's just the last thing in the call stack before the assembly binding failure causes everything to unwind. Solutions (in order of preference): 1. Wait for Redgate to release a compatible update
Check Redgate's website/support for a v22.3-compatible SQL Toolbelt update
You mentioned you already updated Thursday, but there may be a newer hotfix by now
2. Disable the Redgate extension temporarily:
Tools → Extensions and Updates (or Manage Extensions)
Disable SQL Toolbelt/SQL Search extensions
Restart SSMS
You'll lose the Redgate functionality but SSMS will work
3. Rollback to SSMS v21.x or v22.2:
Uninstall SSMS 22.3.0
Install previous version from Microsoft's download archive
This is the fastest way to get back to full functionality with Redgate
--------- I'm going to just use SSMS v20.2 (which I still have on my SQL jump box) until Redgate recompile/release an update for SQL Toolbelt that is compatible with the newer version of Microsoft.Data.SqlClient. I'm sure Redgate are already working on that. / comments
I have the same issue as everyone else. While troubleshooting I came across this thread that reiterates that Microsoft updated the Microsoft.Data.SqlClient library that SSMS v22.3.0 now uses:https...