Antonio Contreras Padilla 

You shouldn't have to do anything.  So perhaps start with confirming the exact paths to your projects (just show one if there are fundamentally on the same path); also confirm if you are sharing projects on a shared drive perhaps where the projects.xml could be changed by another user.

Just guessing...

Thank you, Paul. I am not sharing projects or using a shared drive. Paths are correct. They just willl not be shown after closing Studio and restarting the programme. It's strange. Any suggestions to solve the problem? As a workaround, I’m manually selecting the projects to display them again in the main window so I can continue working on the translations.

Thank you

Antonio

Just out of curiosity, why does Studio start "from scratch" everytime I close and reopen it?

Antonio Contreras Padilla 

Good question, and this is exactly the knub of the problem. Trados Studio is designed as a single-user desktop application.  This means it stores user-specific settings, preferences, and resources such as translation memories, termbases, UI customisations, project paths and project templates in directories tied to your individual user profile (typically under AppData\Roaming and AppData\Local).

When Trados Studio is run on a shared environment like a terminal server or virtual desktop with multiple users logging in, particularly with roaming profiles, redirected folders, or user profile virtualisation, these assumptions can break down and Studio could even start assuming you are a new user every time you fire it up.

So if you're not doing anything like that, then here's the sort of thing that could also cause you a problem that surfaces in a similar way.

• Your user profile could be corrupt?
  • Windows occasionally creates a temporary profile if the main one is corrupt.  This would cause Studio to launch as if it were freshly installed.
  • Check if you are logging into a .bak profile or seeing messages about temporary profiles.
• Maybe you have an aggressive security tool?
  • Endpoint management tools (e.g. Ivanti, AppLocker, Windows Defender Application Control) can wipe or sandbox AppData between sessions.
  • You might even have Group Policy settings that redirect or lock down folders like AppData\Roaming.
• Folder redirection or cloud sync (e.g. OneDrive, Dropbox, Redirected Folders)
  • Studio settings stored under AppData might be synced to the cloud or redirected to a network location.  Sync failures or latency can lead to missing or inconsistent configurations.  This is very common these days!
• Third-party backup or cleanup utilities
  • Some cleaning tools (like CCleaner) or backup software might be wiping AppData thinking it's temporary or disposable.
• Antivirus/anti-ransomware interference
  • Real-time protection software might block access to configuration files or delay writes, leading to settings not being saved correctly.
• Running Studio as a different user or with elevated permissions
  • If you sometimes run Trados Studio “as Administrator” or via a different user account, your settings might not persist across those contexts.
• Corrupted or misbehaving Studio installation
  • Can't rule out an incomplete upgrade, broken plugin installations, or corrupt settings files that might also cause Studio to behave inconsistently.
  • Resetting Studio (e.g. by renaming the Trados Studio folder in AppData\Roaming) may resolve it.
• Virtualisation software (e.g. VMware Workstation, Parallels, Sandboxie)
  • If you are running Studio in a virtualised or sandboxed environment without realising the isolation rules, your settings might not persist outside the session.

Maybe something in that list might trigger some awareness of what's happening in your case?  If it doesn't come back and tell us, and I'll log a case for a support engineer to have a look at why you're having this problem.

Antonio Contreras Padilla 

Good question, and this is exactly the knub of the problem. Trados Studio is designed as a single-user desktop application.  This means it stores user-specific settings, preferences, and resources such as translation memories, termbases, UI customisations, project paths and project templates in directories tied to your individual user profile (typically under AppData\Roaming and AppData\Local).

When Trados Studio is run on a shared environment like a terminal server or virtual desktop with multiple users logging in, particularly with roaming profiles, redirected folders, or user profile virtualisation, these assumptions can break down and Studio could even start assuming you are a new user every time you fire it up.

So if you're not doing anything like that, then here's the sort of thing that could also cause you a problem that surfaces in a similar way.

• Your user profile could be corrupt?
  • Windows occasionally creates a temporary profile if the main one is corrupt.  This would cause Studio to launch as if it were freshly installed.
  • Check if you are logging into a .bak profile or seeing messages about temporary profiles.
• Maybe you have an aggressive security tool?
  • Endpoint management tools (e.g. Ivanti, AppLocker, Windows Defender Application Control) can wipe or sandbox AppData between sessions.
  • You might even have Group Policy settings that redirect or lock down folders like AppData\Roaming.
• Folder redirection or cloud sync (e.g. OneDrive, Dropbox, Redirected Folders)
  • Studio settings stored under AppData might be synced to the cloud or redirected to a network location.  Sync failures or latency can lead to missing or inconsistent configurations.  This is very common these days!
• Third-party backup or cleanup utilities
  • Some cleaning tools (like CCleaner) or backup software might be wiping AppData thinking it's temporary or disposable.
• Antivirus/anti-ransomware interference
  • Real-time protection software might block access to configuration files or delay writes, leading to settings not being saved correctly.
• Running Studio as a different user or with elevated permissions
  • If you sometimes run Trados Studio “as Administrator” or via a different user account, your settings might not persist across those contexts.
• Corrupted or misbehaving Studio installation
  • Can't rule out an incomplete upgrade, broken plugin installations, or corrupt settings files that might also cause Studio to behave inconsistently.
  • Resetting Studio (e.g. by renaming the Trados Studio folder in AppData\Roaming) may resolve it.
• Virtualisation software (e.g. VMware Workstation, Parallels, Sandboxie)
  • If you are running Studio in a virtualised or sandboxed environment without realising the isolation rules, your settings might not persist outside the session.

Maybe something in that list might trigger some awareness of what's happening in your case?  If it doesn't come back and tell us, and I'll log a case for a support engineer to have a look at why you're having this problem.

Thank you for your prompt reply, Paul.

Renaming the Trados Studio folder in AppData\Roaming resolved the issue. I see now the projects in the Project window.

Thank you for your support!

Antonio Contreras