Application crashes without any errors in Windows 11 22H2

Question

We are facing problem with our applications under Windows 11 22H2. The application has been compiled in C++ Builder which uses COM to call functions in .NET compiled assembly for generating crystal reports. It was working fine in all the Windows versions until Windows 11 21H2 but the application crashes without any errors in Windows 11 22H2. Even though we have the code in try.. catch, the application crashes without reaching the catch block.

Our DLL library using .NET Framework 4.7.2, but I tried with a little lower versions and also with 4.8 as well, but still the issue persists.

This is what I got from the Event Viewer log when the application crashes, which says the issue is with clr.dll

I will also share the log file which Ig got from the DebugDiag tool when debugging the crash analysis, for your reference.

Tkrsale3__PID__15372__Date__08_02_2023__Time_12_52_38PM__846__Log.txt

Answer 1

Common Language Runtime (CLR) is a critical component of the .NET Framework in Windows.

If you're encountering errors related to "clr.dll," it's likely that there's an issue with the .NET Framework or with an application that relies on it.

Update .NET Framework: Make sure your .NET Framework is up to date. Visit the Microsoft website or use Windows Update to check for and install any available updates for the .NET Framework.

Repair .NET Framework: If you suspect that the .NET Framework installation might be corrupted, you can attempt to repair it:

Repair your .NET Framework install using the .NET Framework Repair Tool

1. Check Application Compatibility: If the error occurs while running a specific application, it's possible that the application itself is causing the issue. Check the application's documentation or support resources to see if there are any known compatibility issues with certain versions of the .NET Framework.
2. Reinstall .NET Framework: You can try uninstalling and then reinstalling the .NET Framework versions that might be causing the issue. However, be cautious, as this process can potentially impact other applications that rely on the .NET Framework.