Anita Seehof 

If repairing Trados Studio 2022 doesn't fix it then I would suggest working a different way.  Open the files from Trados Studio instead.  Working your way can lead to problems as you may be creating projects within projects every time you double click on a file... unless of course it's only the sdlproj you are double-clicking?

The safest way to work is to open projects from the projects view in Trados.  Open new packages from the Open Package menu.

Thank you for your answer, Paul! I’m not sure what you mean by “repaiging Trados Studio 2022” in this case. How would I do that?

But yes, that’s what I’ve been doing: opening Trados file from within Trados Studio. It is however much more time-consuming than just opening files via double-click. I’ve always done the double-click method with every Trados Studio version I’ve used and I’ve never had any issues with it. Sure, I can use this alternative method – and I have since I upgraded to the 2022 version. But my question was about how to assign the file types properly, so that I can open them via double-click as well. Just like with MS Word or Excel etc., you can open files from within the program or by doulbe-clicking. And I would like to have those same options back with Trados Studio.

Anita Seehof 

Left alone the possibility to open a sdlxliff file in Studio by double clicking it, would you please explain me the purpose of doing so? Usually there should be NO single SDLXLIFF file without a corresponding project. So opening such a file alone makes to me really no sense. Why should this be done?

 Jerzy Czopik  Because that is what Trados Studio is supposed to be able to do. It is not the purpose of my post to discuss why I need or want this feature. I just want my program to work as intended.

As mentioned above several times, I can work around it. And I have. But want to be able to assign SDLXLIFF files properly.

Anita Seehof 

I already agreed with you, that it should work. However, I do not see the purpose in it and the sense for the time lost to make this work. Not more than this.

BTW, I assume you restarted your PC in the meantime?

Jerzy Czopik  Yes, I restarted my computer after the update.

Well, I don’t have daily uses for opening SDLXIFF files via double-click. But sometimes, clients only send those instead of an SDLPPX. And I also save different versions of the same translation in different folders. Opening those, if I want to check something for example, is quicker via double-click than copying them to the project folder and opening them inside the original project.

Anita Seehof 

Thank you for the explanation. Even then I would simply use the "Open" command from within Studio, as it is available via keyboard shortcut (default: CTRL+SHITF+O, easy to configure as CTRL+O). All the necessary paths can be copied from Windows Explorer for example. But let us forget about that here.

Do you still have S2019 installed on your PC? If so, run the repair installation of this program. This should associate all file types with it. Even the sdlxliff should then behave as expected. If that helped, uninstall S2022, restart the PC and install S2022 using the latest downloaded installer (CU2 from today from Download folder) as admin. This might help to resolve your problem.

No, as mentioned above, I upgraded from 2017 to 2022 and uninstalled 2017 right after installing 2022.

Do you think uninstalling and reinstalling 2022 would be different than the reinstallation from the original .exe installer that you suggested above. Because the latter didn’t change my issue.

Anita Seehof said:

It is not the purpose of my post to discuss why I need or want this feature. I just want my program to work as intended.

And the intended behavior is the one I described, the file does not open directly in the Editor but it opens the settings dialogue. 
I guess that what you call 'intended' is not what is intended by the SW but what you would like it to do, which is not the same.

Anita Seehof

Reinstalling Studio 2022 alone will not help, as it did not help yet. The only way I could now think of would be uninstalling S2022, then restarting the PC. After that install 2017 and check, if all files are properly register. If so, simply install S2022 on top as admin.

Walter Blaser said:

And the intended behavior is the one I described, the file does not open directly in the Editor but it opens the settings dialogue. 
I guess that what you call 'intended' is not what is intended by the SW but what you would like it to do, which is not the same.

Walter Blaser  By “intended behavior” I meant indeed what you described and provided a screenshot for. I was simplifying the problem so as to not write a novel …

Jerzy Czopik  Thank you! I will try that on the weekend and report back – hopefully with good news.

Jerzy Czopik  Thank you! I will try that on the weekend and report back – hopefully with good news.

Anita Seehof 

Really sorry for no better ideas, but your problem is indeed strange. I remember log time ago having a similar issue, which was obviously connected to switching between many Studio versions on my PC with memoQ installed in parallel. After installing a completely new version the issue was then solved, but I must admit I did not actively done antyhing to change that, it happened just "by accident".