Due to essential maintenance, access to Trados cloud will be unavailable on Saturday 30 August from 00:00 to 12:00 UTC.

.NET Runtime error (Windows 11) in Trados 2024

Hi there!

Trados 2024 crashes without prompt when modifying a segment. I got the following from Window's Event Viewer:

Nombre de la aplicación con errores: SDLTradosStudio.exe, versión: 18.0.0.1013, marca de tiempo: 0xcb8f4f20
Nombre del módulo con errores: KERNELBASE.dll, versión: 10.0.22621.4036, marca de tiempo: 0x818ebd7b
Código de excepción: 0xc000041d
Desplazamiento de errores: 0x0014a942
Identificador del proceso con errores: 0x0xB18
Hora de inicio de la aplicación con errores: 0x0x1DAF52DBC8956B3
Ruta de acceso de la aplicación con errores: C:\Program Files (x86)\Trados\Trados Studio\Studio18\SDLTradosStudio.exe
Ruta de acceso del módulo con errores: C:\Windows\System32\KERNELBASE.dll
Identificador del informe: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Nombre completo del paquete con errores:
Identificador de aplicación relativa del paquete con errores:

And it's a ".NET Runtime" error. I used to have these errors (they looked the same) with Studio Trados 2019.

Is this going to happen every so often from now?

My Windows is up to date, is there anything I can do to avoid my program from crashing?

Thanks, David

emoji
  •  

    Since the error is related to the `.NET Runtime`, it might help to repair or reinstall the .NET Framework on your system. This can often resolve issues stemming from corrupted framework installations.

    Make sure all your device drivers, particularly those related to graphics and system management, are up-to-date.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
  • Could be, and I will certainly try your workaround. However, it begs the question of why does it happen in the first place. The context: a recently bought PC with Windows 11 Pro. 

    I am just surprised this happened all over again in a completely different system (hardware and software).

    Thanks, David

    emoji