Windows 11 update 24H2 destroy Trados Studio 2022 and the glossaries do not work. Also Multiterm 2022 do not work as well.

Hello,

This is an urgent problem.

Yesterday I have applied the latest update for my operating system, the Windows 11 24H2 and this morning I am surprised that glossaries, just simply do not work. They never load. Additionally, Multiterm is showing a strange behaviour with a big windows showing a strange error.

Basically, the Windows 11 24H2 update destroy Trados Studio 2022 and the glossaries never load. Multiterm is also giving a lot of problems.

This is happening since yesterday.

I really would appreciate someone from RWS tell me how to solve this ASAP or if may download a fix or patch to fix this and continue using the glossaries.

Without the glossaries I cannot work, so basically, I would lose my clients and this, will damage me considerably.

Thanks in advance.

emoji
Parents Reply Children
  • 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.

    emoji
  •  

    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?

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
  • 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.

    emoji
  • 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.

    emoji
  •  

    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.

    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.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
  • 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.

    emoji
  •  

    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:

    Screenshot of SDL MultiTerm 2024 software with a list of terms in various languages, and an 'About MultiTerm' window in the foreground. An 'About Windows' window shows Windows 11 Version 24H2 details.

    In Trados Studio:

    Screenshot of Trados Studio translation results with highlighted term recognition, and an 'About Windows' window displaying Windows 11 Version 24H2 information.

    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.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji


    Generated Image Alt-Text
    [edited by: RWS Community AI at 1:58 PM (GMT 0) on 28 Oct 2024]
  • Have you tested Trados Studio 2022 and Multiterm 2022?

    I reported this problem for the 2022 version, and the screenshots you posted are from Trados 2024. It’s evident that Trados 2024 works fine with the Windows Update 24H2, but the 2022 version fails for some reason. I’m quite surprised, really, that the investigation of such a serious issue concluded so quickly (less than 24 hours).

    In this extremely short period, you claim to have tested several Trados compilations and various Windows 11 versions on multiple computers (desktops, laptops, etc.). Or perhaps you just concluded that the software is working because you did a few installs and those installs worked (this is my suspicion).

    I also suspect you have only tested Trados 2024 (I've seen the screenshot) and not Trados 2022.

    Well, that investigation doesn’t offer a solution for the users of the 2022 version, just purchasing the 2024 version or updating to it. So, at least now I know how this is going to end—no free patch, and purchase the 2024 version. Okay...

    At least now, all the affected users of the 2022 version know what they must do.

    emoji
  • Dear Jesus, you should read my posts here. Buying 2024 will not help at all. My problems are still not solved, my memories are lost. Decades of work. None of the proposed posts work. I spent hours with my technician this afternoon to no avail. And now I learned that they will not help rapidly since I have no maintenance contract. Don't ask me what I think of that.  

    emoji