Hi @Anonymous ,
It seems to be more about .NET and windows aspect, I just can give you some suggestion, perhaps you should check the error log to see the exact error description and specific fault module name.
Please open CMD, using “sfc /scannow” to check/repair system files, and here is a .NET framework repair tool: https://support.microsoft.com/en-us/topic/microsoft-net-framework-repair-tool-is-available-942a01e3-5b8b-7abb-c166-c34a2f4b612a
The CLR has been fatally corrupted, this is most often caused by data corruption
https://learn.microsoft.com/en-us/dotnet/framework/debug-trace-profile/fatalexecutionengineerror-mda
a single version of the CLR typically has multiple versions of the .NET Framework that it works with. With regards to SQLCLR code, SQL Server only works with a single version of the CLR, and the specific version depends upon the version of SQL Server.
So you might consider whether there is a problem in terms of version compatibility.
https://stackoverflow.com/questions/41114147/which-version-of-net-framework-sql-server-supports