Hi Anna Gilham

You have a subscription for Trados Freelance - Annual Saver - which includes a support contract, please login to your Account Portal and click on Support and raise a ticket directly with the technical team so they can investigate this.

Best regards,

Anca 

Great, thank you I will do that.

PS: I agree with Anna: ask RWS support! However, I also asked Claude, which I use a lot in my Supervertaler development with Trados, and it said the following (maybe useful):

 ---

A few things to try, roughly in order:

1. Read the actual Trados log (not Event Viewer). Open the newest file in %AppData%\Trados\Trados Studio\Logs\ after a crash and look at the last FATAL/ERROR line – it names the real cause.
2. Turn off 3D acceleration in Parallels. In the VM's settings → Hardware → Graphics, untick 3D acceleration. The "Initializing Views" stage is where Trados renders its UI, and in a VM the virtual GPU is a common cause of crashes there. This is a reversible checkbox on the Mac side – no Windows changes needed.
3. Delete plugincache.xml in the Trados AppData folder – Studio rebuilds it on next launch.
4. Confirm .NET Framework 4.8 is installed (required by Trados 2024).
5. Raise a support ticket – your Freelance Annual Saver subscription includes a support contract, via the Account Portal.

Optional (only if step 2 doesn't help): disable WPF hardware acceleration via the registry. In regedit, set HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics\DisableHWAcceleration to a DWORD of 1, then reboot. Why it's optional and last: it does the same job as step 2 (forces software rendering) but from inside Windows, and it applies to every WPF app under your user account, not just Trados – so it's broader than needed. Step 2 achieves the same fix more surgically and without editing the registry, so try that first. The registry key is fully reversible (set it back to 0 or delete it).

– Claude (Claude Code)

PS: I agree with Anna: ask RWS support! However, I also asked Claude, which I use a lot in my Supervertaler development with Trados, and it said the following (maybe useful):

 ---

A few things to try, roughly in order:

1. Read the actual Trados log (not Event Viewer). Open the newest file in %AppData%\Trados\Trados Studio\Logs\ after a crash and look at the last FATAL/ERROR line – it names the real cause.
2. Turn off 3D acceleration in Parallels. In the VM's settings → Hardware → Graphics, untick 3D acceleration. The "Initializing Views" stage is where Trados renders its UI, and in a VM the virtual GPU is a common cause of crashes there. This is a reversible checkbox on the Mac side – no Windows changes needed.
3. Delete plugincache.xml in the Trados AppData folder – Studio rebuilds it on next launch.
4. Confirm .NET Framework 4.8 is installed (required by Trados 2024).
5. Raise a support ticket – your Freelance Annual Saver subscription includes a support contract, via the Account Portal.

Optional (only if step 2 doesn't help): disable WPF hardware acceleration via the registry. In regedit, set HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics\DisableHWAcceleration to a DWORD of 1, then reboot. Why it's optional and last: it does the same job as step 2 (forces software rendering) but from inside Windows, and it applies to every WPF app under your user account, not just Trados – so it's broader than needed. Step 2 achieves the same fix more surgically and without editing the registry, so try that first. The registry key is fully reversible (set it back to 0 or delete it).

– Claude (Claude Code)