JESUS SANCHEZ 

This is solely the problem of your operating system, NOT in any way caused by TS or MT. If you have trouble with this Windows update, restore your previous OS. TS2022 or TS2024 and MultiTerm work perfectly on Windows 22H2 and on Windows 22H3. I do not yet have installed 24H2, so I am warned now not to do so.

You can try to run a repair installation of Trados Studio (same applies to MultiTerm) according to this article: https://gateway.sdl.com/apex/communityknowledge?articleName=000001414

But if that does not help, I'm afraid you'll really be forced to roll back the Windows update.

Thanks for your reply. I rolled back that update and everything works fine, but please note that this is not a solution because Windows 11 forces the user to install the update. In plain words, the users must install the update and there is no option to ignore updates in Windows 11.

Due to the extreme importance of this issue, I would appreciate it if an RWS representative could reply to this thread and provide some insights on what is going on with Trados Studio 2022 and the Windows Update 24H2.

All the affected users need to know when RWS will release a patch or fix to make compatible Trados Studio 2022 with the Windows 11 update 24H2.

JESUS SANCHEZ 

JESUS SANCHEZ said:

I would appreciate it if an RWS representative could reply to this thread and provide some insights on what is going on with Trados Studio 2022 and the Windows Update 24H2.

Tricky for me. I am running W11 on my personal laptop but have not been forced to update to 24H2... I still have 23H2 and don't see any problems with Trados Studio 2022 or 2024.

I do know at least one person I work regularly with and she has W11 H224 installed and doesn't have any problems at all... other than initially installing it since Windows Defender picked it up with 24H2.  We disabled it, installed, re-enabled it and now all is well.

Perhaps it would be worth trying again, but disable Windows Defender or whatever AV solution you have, just in case that played a part in causing you some difficulties?

JESUS SANCHEZ 

Not really. You can switch off updates or simply not install these: learn.microsoft.com/.../how-can-i-permanently-disable-windows-update-servi

Switching off all updates is extremely risky for everyone (individuals and organizations). It opens the door to viruses, trojans, spyware, and all imaginable security issues. It is not advisable to disable all updates, as it can endanger your own computers and all surrounding computers.

Hi Paul,

Could some people at RWS try to install the Windows 11 24H2 update and test Trados Studio 2022/2024 under several environments (laptops, desktop PCs, etc.)? 23H2 works fine; the problem occurs exactly with the 24H2 update.

I have contacted Microsoft and they provided me a registry code to disable the 24H2 update. I will try this during the weekend. However, I am aware that the 24H2 update is causing many problems for various programs, including Trados.

Many hardware and software providers are releasing patches to make their software compatible with the new update (24H2). I am using Windows Defender, but that does not seem to be the issue. This update has changed something in the operating system that is specifically affecting the way Trados loads glossaries. Even MultiTerm is not working. However, translation memories are not affected.

I don’t know how Trados was programmed, but I assume it is using the Microsoft Access database engine, and that is exactly what is affected after this update (24H2).

It is very important that people at RWS start to thoroughly test Trados 2022/2024 under the Windows 11 24H2 update; otherwise, people will begin to experience problems. It is necessary to patch this ASAP.

JESUS SANCHEZ 

JESUS SANCHEZ said:

Could some people at RWS try to install the Windows 11 24H2 update and test Trados Studio 2022/2024 under several environments (laptops, desktop PCs, etc.)? 23H2 works fine; the problem occurs exactly with the 24H2 update.

The QA teams do test with many environments, but I have forwarded your concerns to the appropriate people in our development teams.  Please note what I have already told you and that is we have at least one user in my own team using W11 24H2 without any problems.  So this is not a more general problem affecting every user.  But we will investigate.

JESUS SANCHEZ said:

I assume it is using the Microsoft Access database engine

Trados Studio doesn't use MS Access at all.  MultiTerm does though as a termbase in MultiTerm is essentially an Access database.

Hi Paul,

I guess that Trados grabs the terms from the SDLTB files using a MultiTerm API, and after this update, MultiTerm is not working. In fact, when I open MultiTerm, I get a window with a large message showing incomprehensible text. There is no doubt that this is being caused by 24H2, because when I roll back to 23H2, everything works fine.

For the moment, I will pause this update. If I succeed in doing this, I will post here how to pause this update. I really would appreciate it if you keep me up to date with your investigation on this issue and especially if you find a solution for this problem.

JESUS SANCHEZ 

We have completed our initial investigation this afternoon and the support team found that there is no general issue in accessing terminology when using Trados Studio and MultiTerm Desktop 2024 on Windows 11 24H2.  Terminology works in both Studio and MT Desktop 2024 on Windows 11 24H2.

In MultiTerm:

In Trados Studio:

This would be in line with my initial finding from the users I have worked with who are also on this version of Windows.  So, I will log a support case on your behalf so that a support engineer can have a look at your setup and see if we can determine what is driving this issue for you.

JESUS SANCHEZ We will be pleased to help you with this problem so have logged a support case on your behalf. We do prioritise customers who have a support contract so please keep in mind it could take up to 48 hours, especially over a weekend, but rest assured we will contact you as soon as we can. You will be contacted at the email address used for this Community. Support Case Id : 00874676 .