Hi Nadja Balogh , I am not sure whether you received my emails sent via the Support case. As mentioned there, this is indeed an issue in the latest versions of Trados Studio (2024 & 2026). We logged it for Development (as CRQ-45016), so it can be fixed in a future update.

The good news is that there is a workaround to get AutoSuggest working again in Studio 2026 as well. You only need to close and reopen the file in the Editor, without making any changes.

Hello Edith,

Thank you for your reply. Unfortunately the problem pops up now even with newly created projects, and closing and reopening the file doesn't necessarily solve the problem either. It's just all very shaky. I'm afraid that I will need to revert back to version 2022 until this issue is properly solved.

Hello Nadja Balogh ,

Can you please provide details via the Support Case in what circumstances reopening the file does not solve the issue? You can revert to Studio 2022 if you like, but please keep in mind that engineering and technical support for this version will end on 31.12.2026.

Hi Edith,

Unfortunately not, it just happened at one point but it is not reproducible and I cannot recognize any patterns. Most of the times it works. It is just a little exhausting to always be on the watch. I'm now thinking of keeping both versions (2026 and 2022) active because even though the AutoSuggest in 2026 is shaky I find that the suggestions generated during the project from the file and the TM (sorry, I don't know what these are called officially) work very well.

Hi Edith,

Unfortunately not, it just happened at one point but it is not reproducible and I cannot recognize any patterns. Most of the times it works. It is just a little exhausting to always be on the watch. I'm now thinking of keeping both versions (2026 and 2022) active because even though the AutoSuggest in 2026 is shaky I find that the suggestions generated during the project from the file and the TM (sorry, I don't know what these are called officially) work very well.

Hi Nadja,

I understand. The issue was logged as a high priority item, so hopefully a fix will be implemented soon, and there will be no need for the workaround.