• State Verified Answer
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 429 subscribers
  • Views 507 views
  • Users 0 members are here
Options
Related

Trados Studio 2024 crashes at “Initializing Views” on Parallels (Mac VM) – no crash log available

Anna Gilham

Hi everyone,

I’m experiencing a consistent startup crash with Trados Studio 2024 running in a Windows 11 virtual machine via Parallels on macOS.

Trados launches normally, shows the splash screen, reaches “Initializing Views”, and then immediately closes without any error message or crash dialog.

Environment

  • Trados Studio 2024
  • Windows 11 (Parallels Desktop on Mac)
  • Fully updated Parallels Tools installed
  • Windows fully updated

What I’ve tried so far

  • Reset Trados user profile by renaming %AppData%\Trados\Trados Studio\18
  • Confirmed a fresh 18 folder is recreated on launch
  • Checked Windows Event Viewer (Application logs)
    • No relevant Application Error / .NET Runtime / SDLTradosStudio.exe crash entries found
    • Only unrelated Windows activation error (0x803F7001)
  • Reinstalled Parallels Tools
  • Verified Windows itself is stable and other apps run normally
  • Tried launching via command line switches, but Trados closes before any arguments take effect

Behaviour

The crash is always reproducible and always occurs at “Initializing Views”.

Question

Has anyone seen this behaviour in Trados Studio 2024 specifically in a Parallels environment?

At this point I’m trying to determine whether this is likely:

  • a corrupted Trados installation or shared SDL components
  • a .NET/WPF rendering issue inside the VM
  • or a Parallels graphics / virtualization compatibility problem

Any guidance or known fixes would be greatly appreciated.

Removed AI Suggestion
[edited by: Anna Gilham at 10:36 AM (GMT 1) on 30 Jun 2026]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Hello,

    It seems like you're encountering a challenging issue with Trados Studio 2024 on a Parallels virtual machine. Let me guide you through some steps to help resolve this problem:

    ### Step 1: Verify Windows Updates

    - Ensure that your Windows 11 virtual machine is fully updated. Go to **Settings > Update & Security > Windows Update** and click **Check for updates**. Install all available updates and restart the VM. Repeat this process until no further updates are available.

    ### Step 2: Repair Trados Studio Installation

    - Open the **Control Panel** in Windows.

    - Navigate to **Programs > Programs and Features**.

    - Locate **Trados Studio 2024** in the list, right-click, and select **Repair**.

    - Restart the VM after the repair process is complete.

    ### Step 3: Check .NET Framework

    - Confirm that .NET Framework 4.8 (or later) is installed:

     - Open **Control Panel > Programs > Turn Windows features on or off**.

     - Ensure that **.NET Framework 4.8** is checked. If not, enable it and restart the VM.

    - If .NET Framework is already enabled, refresh it:
    emoji
Reply
  • 0

    Hello,

    It seems like you're encountering a challenging issue with Trados Studio 2024 on a Parallels virtual machine. Let me guide you through some steps to help resolve this problem:

    ### Step 1: Verify Windows Updates

    - Ensure that your Windows 11 virtual machine is fully updated. Go to **Settings > Update & Security > Windows Update** and click **Check for updates**. Install all available updates and restart the VM. Repeat this process until no further updates are available.

    ### Step 2: Repair Trados Studio Installation

    - Open the **Control Panel** in Windows.

    - Navigate to **Programs > Programs and Features**.

    - Locate **Trados Studio 2024** in the list, right-click, and select **Repair**.

    - Restart the VM after the repair process is complete.

    ### Step 3: Check .NET Framework

    - Confirm that .NET Framework 4.8 (or later) is installed:

     - Open **Control Panel > Programs > Turn Windows features on or off**.

     - Ensure that **.NET Framework 4.8** is checked. If not, enable it and restart the VM.

    - If .NET Framework is already enabled, refresh it:
    emoji
Children
No Data