• State Verified Answer
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 22 replies
  • Answers 4 answers
  • Subscribers 435 subscribers
  • Views 2282 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

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

JESUS SANCHEZ

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.


[locked by: Paul at 8:50 PM (GMT 0) on 23 Nov 2024]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0 in reply to Paul

      

    One other thing... please drop me an email to pfilkin at sdl dotcom with the email address you use for your account.  The support team cannot help you until we can verify you have a paid version of the product as you are using this community with an email that has no product attached to it.

    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
  • 0 in reply to Paul

    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
  • 0 in reply to Paul

    Thanks for being so kind in opening a support ticket. The problem here is that I have urgent deadlines, and if I do not meet them, I can lose my clients. So, I cannot now install 24H2 again, experience the problem, stop my translations, and try to apply solutions with Trados stopped. This could take days, and in the meantime, my projects are halted. In this business, this is unacceptable for LSP.

    I was expecting that you would test Trados 2022, identify the problem, and create a patch for the affected users. However, you tested version 2024 and not the 2022 version (which seems to be the one failing with the 24H2 update). So the only solution I see here is:

    1) Deal with Microsoft to pause the Windows 11 24H2 update.

    2) Wait for the 24H2 update to be deployed to many of your clients.

    3) Wait for your clients to start complaining and opening support tickets on this issue.

    4) Finally, release a patch or post a solution for those clients.

    5) In the meantime, I can continue working without stopping my activity.

    6) I just wanted to avoid headaches and problems for all affected users, but it seems that’s not possible since you haven’t tested the 2022 version.
    emoji
  • 0 in reply to JESUS SANCHEZ

    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
  • 0 in reply to Renate Radziwill-Rall

     

    Could I kindly ask that we keep this thread focused on the original topic? It appears that the issue you’re describing may be specific to your computer setup, as you mentioned in this thread, rather than directly related to Trados. For clarity and to help others who might have similar queries, it might be best to discuss this there. Thank you for understanding!

     Unable to Transfer 2021 Trados Licence and TM Data to New PC – Forced Upgrade to Trados 2024 

    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
  • 0 in reply to JESUS SANCHEZ

     

    JESUS SANCHEZ said:
    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 just want to clarify that I haven’t claimed to have conducted the extensive testing you suggested. My point was simply that this doesn’t appear to be a general issue, as our initial investigation would have been impacted if it were. We’ve taken your concern seriously, and while we continue to look into it, so far, yours is the only report of this nature among thousands of users. Naturally, that doesn’t raise the same level of concern.

    Our teams are also testing older versions to ensure coverage, though our priority is to maintain the stability of current versions first. I also requested your email address to confirm your licence details and provide further assistance, which we haven’t received.

    I’m here to help and am committed to investigating this, but it’s important to stay constructive. Sometimes, issues that seem significant turn out to be isolated to a particular setup, so we’ll continue examining all possibilities on our side.

    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
  • 0 in reply to JESUS SANCHEZ

      

    JESUS SANCHEZ said:
    I was expecting that you would test Trados 2022, identify the problem, and create a patch for the affected users.

    So far you are the only user we are aware of.  I also note the following page which doesn't paint the picture you have painted in this thread:

    https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-24h2

    JESUS SANCHEZ said:
    Thanks for being so kind in opening a support ticket.

    You're welcome.  Please drop me an email to pfilkin at sdl dotcom with the email address you use for your account.  The support team cannot help you until we can verify you have a paid version of the product as you are using this community with an email that has no product attached to it.

    JESUS SANCHEZ said:
    The problem here is that I have urgent deadlines, and if I do not meet them, I can lose my clients.

    Fair enough.  At the moment we are treating this as an isolated problem on your machine.  We're willing to help you when you're ready.

    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
  • +1 in reply to Paul

     

    Paul said:
    Our teams are also testing older versions to ensure coverage, though our priority is to maintain the stability of current versions first. I also requested your email address to confirm your licence details and provide further assistance, which we haven’t received.

    The support teams have now finished testing 24H2 with Trados Studio 2022, and we are unable to replicate the problems you have reported there either.  Given we have no other reports of this, and given the Microsoft report I shared earlier also has no mention of the problems you mentioned, we are going to consider this closed.

    However, once you provide your proper email address to me, we are still willing to have a look at this with you on your machine.  This is entirely your call.

    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
  • 0 in reply to Paul

    Thanks for your reply. Unfortunately, I cannot stop my current projects. You have not provided details about the compilation tested for Trados 2022, the machines where it was tested, or the previous Windows 11 updates of those machines. I really don't know how or where you are testing this, to conclude that there is 'no problem' and that it is something from my machine, but the problem is real and it is happening. You will very likely start to receive complaints from clients as soon as they experience the problem. It is necessary to wait for the 24H2 update to be completely deployed. In the meantime, I will try to offer a solution to hide and avoid the automatic install of the 24H2 update. I am in touch with Microsoft and they are assisting me with this.
    emoji
  • 0 in reply to Paul

    I did not react yesterday because I had other things to do. I will later tonight test everything you and ChatGPT suggested ,and then come back to you.
    emoji