Subject: Mendix Studio Pro 10.x fails to launch: Fatal Execution Engine Error (0x80131506) in CoreCLR under .NET 10

0
Hi everyone,I’m encountering a blocking issue with a fresh installation of Mendix Studio Pro 10.x (which utilizes the .NET 10 runtime). The application fails to launch entirely—double-clicking the executable results in a silent termination with no Mendix UI or splash screen.Error Logs:Windows Event Viewer (Application Logs) catches the following crash consistently:PlaintextApplication: studiopro.exe CoreCLR Version: 10.0.726.21808 .NET Version: 10.0.7 Description: The process was terminated due to an internal error in the .NET Runtime at IP 0x00007FFFC91A92EE (0x00007FFFC90F0000) with exit code 0x80131506. Analysis & Diagnostic Steps Taken:Exit Code 0x80131506: This points directly to a COR_E_EXECUTIONENGINE (Fatal Execution Engine Error) inside coreclr.dll. It's happening before managed code execution, likely during GC initialization or native heap parsing.Environment: Tested on Windows 11 (Build 22631). Windows SFC and DISM health checks return clean.Security Software: Confirmed no interference from EDR, Windows Defender, or aggressive third-party AV hooks injecting into the process.Workarounds Attempted:Setting DOTNET_gcServer=0 (Workstation GC) does not resolve the crash.Setting DOTNET_GCDynamicAdaptationMode=0 (Disabling DATAS) yields the same crash at the same Instruction Pointer.Given that this is a native crash inside the embedded .NET 10.0.7 engine that Mendix ships with, this looks like a severe edge-case compatibility issue with specific CPU topologies (e.g., Intel hybrid architecture P/E-cores) or an unhandled native memory violation during the Studio Pro bootstrap phase.
asked
1 answers
1

Since the crash is occurring before Studio Pro even starts, this looks more like a .NET runtime/environment issue than a Mendix application issue.


A few things I would check:

  • Verify that your CPU architecture (Intel hybrid P/E cores, if applicable) and BIOS are fully up to date.
  • Ensure you're using the latest supported version of Mendix Studio Pro, as newer patches may include fixes for embedded .NET runtime issues.
  • Try launching Studio Pro with a new Windows user profile to rule out a corrupted user configuration.
  • Check whether Windows has generated any crash dumps (WER or procdump) that could provide more details than the Event Viewer.


Kindly mark this as the accepted answer if it helps.

answered