Hi,

Similar issue for me on Studio 2022/Windows 11: double-clicking on a package opens Studio, but doesn't open the package.

In my case, it isn't linked to any previous versions of Studio: I deleted any previous versions before installing Studio 2022.

Repairing Studio/Resetting the default parameters didn't work; all workarounds given in both this article (Repairing your installation of Trados Studio) and this article (Resetting Trados Studio to default state) have been tried. In vain.

Please note: I suspect it also prevents me from installing the Antidote Verifier plugin, which is critically important for the quality of my work.

My current system and software:

- Windows 11: build 22000.978, Administrator account

- Trados Studio 2022 (17.0.3.11695)

Many thanks in advance for your help!

Samuel

Hi Samuel Deleuze ;

Does the old Windows way work?

1. On Windows Explorer, right click on your package.
2. Select Open with… option.
3. Select More apps and browse to your 2022 folder and select the exe: C:\Program Files (x86)\Trados\Trados Studio\Studio17\SDLTradosStudio.exe
4. Tick Always use this app […] check box or click on the Always button (depending on your Windows version).

Does double-clicking work now?

Hi Jesús Prieto ,

Thanks for this first reply. Yes, I've already defined Studio 2022 as default app for SDLPPX files, so Studio 2022 does open when double-clicking the package.

The issue is that nothing happens next. No window opens to proceed to actually opening the package.

Best,

Samuel

Hi Samuel Deleuze ,

If you feel comfortable running the Windows Registry (regedit), please check if this 2 keys have the default value shown below the key:

HKEY_CLASSES_ROOT\SDL.TradosProjectPackage.1\shell\open\command
"C:\Program Files (x86)\Trados\Trados Studio\Studio17\SDLTradosStudio.exe" /openPackage "%1"

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\*\shell\Sdl Trados Studio\command
"C:\Program Files (x86)\Trados\Trados Studio\Studio17\Sdl.TranslationStudio.ShellLauncher.exe" "%1"

I believe you have different values (probably the 1st key is missing the /openpackage part). If so, and you are careful and know what you are doing, create a backup of your registry (just in case something goes wrong) and only then edit the key(s). Paste the full line, including quotation marks.

Hi Jesús Prieto ,

Many thanks again for your help.

Unfortunately, both keys are correct. I still tried to copy-paste them as you said, in case I was missing something, and it still doesn't work.

Could it possibly come from the following key?

\HKEY_CLASSES_ROOT\sdlppx_auto_file\shell\open\command

It doesn't have the /openPackage element in it.

As for the plugin issue (double-clicking the plugin installation file opens Studio but doesn't install the plugin), could it come from the following key?

\HKEY_CLASSES_ROOT\sdlplugin_auto_file\shell\open\command

Thanks in advance,

Samuel

Interesting! I haven't got any of those 2 keys (sdlppx_auto_file, sdlplugin_auto_file):

And they were not there either in a machine with an old Trados Studio 2019…

Are you sure the path is correct?

I have Windows 10, but I think there shouldn't be different than your Windows 11.

Yes, I copy-pasted the paths.

Now, I've just found some info about my exact issue on this article:
https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0037673

And it does mention sdlppx_auto_file. Several pieces of information I'm not sure about, though:

- "Verify if it points to SDL.TradosProjectPackage.1 " => How can I see where it points?

- "In some cases, it was changed to sdlppx_auto_file and you have to correct it to point to SDL.TradosProjectPackage.1 and sdlproj_auto_file to SDL.StudioProject.1." => What was changed to "sdlppx_auto_file" and how to make the correction?

I like to think you will understand the article. Would it be possible to translate it as a step-by-step procedure to follow?

Many thanks in advance!

Samuel

Hi Samuel Deleuze ,

Samuel Deleuze said:

- "Verify if it points to SDL.TradosProjectPackage.1 " => How can I see where it points?

You can check the 1st value in the key named Default on the right pane (screen-shot from my machine):

This has to be the meaning of pointing in that article. I agree it's a bit cryptic…

Similar thing for the other key Computer\HKEY_CLASSES_ROOT\.sdlrpx (although a slightly different value: SDL.TradosReturnPackage.1).

I believe yours is different and is causing your issue, otherwise, you'd have seen the key Defaul on the right pane with the value mentioned in that article.

Hope it helps!

It so, you can check other file types, such as sdltm…

Hi Jesús Prieto ,

I sense we're moving in the right direction but we're not quite there yet.

- My .sdlppx entry has a sub-entry, which had no value in the "Data" column. As shown below, I've added the "SDL.TradosProjectPackage.1" value:

- The .sdlppx entry itself has the value "sdlppx_auto_file" in the "Données" (= Data) field. I'm not sure whether I should also change this one to "SDL.TradosProjectPackage.1", or if I should change the value in the "sdlppx_auto_file" entry...

-The "sdlppx_auto_file" entry has the following:

Maybe that's the one that should be corrected. If so how?

Thanks again for all your help!

Samuel

(I should add that the issue is still there in the current state of things.)

Hi Samuel Deleuze

Samuel Deleuze said:

I sense we're moving in the right direction but we're not quite there yet.

Yeah, I think the same...

IMPORTANT: I don't know when changes implemented in the Windows Registry take effect. Sometimes changes take effect immediately; sometimes a restart of the PC or the application is needed. And I don't really know in this case, sorry. I'd restart now your PC, to confirm that so far the issue is still there.

Samuel Deleuze said:

My .sdlppx entry has a sub-entry, which had no value in the "Data" column. As shown below, I've added the "SDL.TradosProjectPackage.1" value:

As you can see from my screen-shot, the Default key on the right pane is in the root key (.sdlppx). I think you have added it to OpenWithProgids, a key I don't have.

Samuel Deleuze said:

-The "sdlppx_auto_file" entry has the following:

Maybe that's the one that should be corrected. If so how?

I don't have this sdlppx_auto_file key, but you can try… If it doesn't work, you can revert it.

How to do it: double click on the ab icon, and edit the only field you can edit (Value data).

I've read a bit more through your link. I've added a couple of items, just in case it helps you:

I don't have any SDL extensions here:
HKEY_USERS\S-1-5-21-XXX-XXX-XXX\SOFTWARE\Classes - here, the number after 1-5-21 will most probably differ from one user to another.
XX are mine

And my screen-shot from this location (also in your link):
\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\ApplicationAssociationToasts

If nothing works and no other ideas from peers, I'd uninstall Trados Studio and re-install it again.

Hi Jesús Prieto ,

Still doesn't work, unfortunately...

Please note:

- Uninstalling and reinstalling Studio  is one of the first things I tried. Didn't work. Now, I just tried again, and it didn't work again.

- I also tried to reset Studio to factory settings. Didn't work either.

- I do have SDL extensions in the HKEY_USERS\S-1-5-21-XXX-XXX-XXX\SOFTWARE\Classes folder, but they seem to be the same as those in the CLASSES_ROOT folder.

- Things seem fine in the ApplicationAssociationToasts folder.

I do have a colleague who has both Studio 2022 and Windows 11, I'll further investigate with him next week and compare our configurations if I can, but I'm more than ever at a loss for solutions.

OTHER IMPORTANT NOTE: Being unable to open packages by double-clicking is actually my minor issue, here, since I can open them with the Open package option from within Studio. The main issue, which I suspect has a similar origin, is plugin installation: I can't install the Antidote plugin, which is a powerful spellcheck tool, and therefore critical to the quality of my work.

Best,

Samuel

Hi Jesús Prieto ,

Still doesn't work, unfortunately...

Please note:

- Uninstalling and reinstalling Studio  is one of the first things I tried. Didn't work. Now, I just tried again, and it didn't work again.

- I also tried to reset Studio to factory settings. Didn't work either.

- I do have SDL extensions in the HKEY_USERS\S-1-5-21-XXX-XXX-XXX\SOFTWARE\Classes folder, but they seem to be the same as those in the CLASSES_ROOT folder.

- Things seem fine in the ApplicationAssociationToasts folder.

I do have a colleague who has both Studio 2022 and Windows 11, I'll further investigate with him next week and compare our configurations if I can, but I'm more than ever at a loss for solutions.

OTHER IMPORTANT NOTE: Being unable to open packages by double-clicking is actually my minor issue, here, since I can open them with the Open package option from within Studio. The main issue, which I suspect has a similar origin, is plugin installation: I can't install the Antidote plugin, which is a powerful spellcheck tool, and therefore critical to the quality of my work.

Best,

Samuel

Hi Samuel Deleuze ,

Sorry, 'm running out of ideas...

Re. your plugin problem, I've managed to install Antidote  and I see the buttons in the Review ribbon:

but these buttons disappear after 30 seconds or so, probably because I haven't got an Antidote license. Buttons are back after restarting Trados Studio (then disappear again). I think you have an issue installing the plugin, but i shared my experience just in case.

Hi Jesús Prieto ,

The plugin issue is now solved. I've compared the registry keys with a colleague for whom it was working, and it turned out that my \Computer\HKEY_CLASSES_ROOT\.sdlplugin had "sdlplugin_auto_file" as a value, and his had "Sdl Plugin Installer".

I changed it accordingly, and double-clicking the plugin file opened a window that allowed me to open it with the plugin installer module instead of opening Studio.

The plugin is now installed and working correctly.

(Config: Studio 2022, Antidote 11 and Windows 11.)

I won't look much further to solve the package issue, which is less of a problem.

Thanks again for your help and time!

Samuel