The system cannot find message text for message number 0x%1 in the message file for %2

Question

I got a number of error message while working in the latest Trads Studio 2022 revision and those errors, while not crashing my work, are puzzling me as I was not trying to save any bilingual. 
 Note than the second message related to the bilingual file popped up over the first one a minute later while I was looking for documentation

Louis LaBonté · Answer

Thanks for the update, Paul . I always appreciate your straightforwardness, even when the news are not especially good. 
 I managed to have the 22H2 update removed half an hour ago by tech support (with admin rights) through a Windows roll-back (or &ldquo;retour en arri&egrave;re&rdquo;, in French). Contrary to what Walter Blaser mentioned yesterday, the time limit is 30 days (not 10), so I had three days left before it ceased to be an option. 
 I'll let you know if it solves the issue. If so, it would be a good idea to update the article at https://gateway.sdl.com/apex/communityknowledge?articleName=000019760 . 
 Also, for people whose time limit expired for the rollback, it think it would be a good idea to further explore the Known Issue Rollback (KIR) option, which seems to be a different thing, possibly available for a longer period. Some information about that (including for computer ruled by a corporate group policy) can be found at learn.microsoft.com/.../status-windows-11-22h2.

Louis LaBonté · Answer

Paul 
 For now, the roll-back cancelling Windows update 22H2 works with no issue. 
 So, considering that it's a non-critical update and that it has caused numerous problems to various applications, I would recommend to anyone having the &ldquo;0x%1&rdquo; issue to go for the roll-back (or ask someone in their organization with admin rights to do so), and to avoid reinstalling it at least until Microsoft corrects its flaws. 
 The sooner the better, since the rollback option has a 30-day time limit. Otherwise, maybe the Known Issue Rollback (KIR) would be an option (including for iorganizations with a group policy), but that would remain to be confirmed. To find information about it, type 22H2 and " Known Issue Rollback" in a search engine, and you should easily find it (the links don't seem to work when I post them on this forum).

Louis LaBonté · Answer

NEW UPDATE &ndash; POSSIBLE SOLUTION: 
 For those who would like to try (unfortunately, I can't, since I have no control over my employer's group policy), it should be possible to uninstall the Windows update 22H2, as explained here: https://www.askvg.com/windows-11-2022-update-22h2-known-issues-and-workarounds/ 
 And if, like me, your computer ir ruled by an corporate group policy, you may ask your organization to use the &ldquo;Known Issue Rollback (KIR)&rdquo; based on the instructions on the same page: The group policy download in question is here: https://download.microsoft.com/download/8/e/f/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/Windows%2011%2022H2%20KB5018427%20221029_091533%20Known%20Issue%20Rollback.msi 
 Please let us all informed if you try that solution and it works: that would be such a relief to so many people!

Louis LaBonté · Answer

Some people in my organization also have the Windows 11 22H2 version without experiencing the bug, but as far as I know, ALL people who experience it have the 22H2 version. 
 On my end, since the rollback to version 21H2, I have not experienced the bug a single time, while, before the rollback, it happened almost every time I confirmed a segment. 
 So, at least in my case, the 22H2 version of Windows 11 Enterprise was clearly the culprit. For reference, here are the exact current specifications of my system (in French), on which I DO NOT have the bug anymore (since the rollback):

Trados Studio > 2. Trados Studio

The system cannot find message text for message number 0x%1 in the message file for %2

Top Replies