I have just started having the same problem with the DeepL plugin. Any suggestions for a fix?

Afrim Hyseni John Fry Jeff Staflund 

First thing is to review the release notes as the advice in there is to uninstall all your plugins completely before updating.  Then only install plugins that you can see are available for you in the integrated appstore as many have not been updated yet.

This post sheds a little more light on it...  RE: TexTra plugin causes error after latest update to Trados Studio 2022 

But in relation to the ones mentioned in this thread DeepL is fine if you use the correct version, ModernMT almost certainly needs to be updated to support SR1 and MT Enhanced is best replaced with the separate Google and Microsoft plugins as these have been rewritten and will be maintained to support anything new that is available from these providers going forward.  You can find them here:

https://appstore.rws.com/Plugin/174

https://appstore.rws.com/Plugin/179

I'm having the same issue with the DeepL plugin as Jeff. I removed the old plugin and re-installed, but no luck. I looked at the post you linked to Paul, but let's be honest, translation software shouldn't be this difficult (remember how a while ago we all had to switch to some private version of the RWS App store? Whatever happened with that??)

I'm not a programmer. So how do I get the DeepL plugin to work again? 

Replying to myself because I got it to work just now by going to Add-ins->Plugins, deselecting the DeepLMTProvider tick box, re-launching, then reselecting it, and relaunching again.

Katherine Holly Kirby 

Katherine Holly Kirby said:

translation software shouldn't be this difficult

I agree... and believe me we don't do it on purpose!!  You have no idea how much work this is for us.

Katherine Holly Kirby said:

remember how a while ago we all had to switch to some private version of the RWS App store? Whatever happened with that??

This was needed because we lost the old appstore from one day to the next and so we solved it by using the Private AppStore concept that we added to the software.  Then, we worked on rebuilding the appstore until we had got it to a stage that we could put back the default AppStore and not require the Private AppStore any more.  We are now nearing completion of the next stage to be able to start allowing 3rd party developers to have access to manage their own plugins again.  It's a lot of work behind the scenes and it's not simple, but we are almost in a situation now that will make it possible for us to do whatever we want with this solution and that means all the things users asked for in the past with the old solution but we were simply unable to do it.

I can't really tell you more than that... we're doing our best with a very complicated situation.

Katherine Holly Kirby said:

I'm not a programmer. So how do I get the DeepL plugin to work again? 

You don't have to be a developer, you just have to follow the instructions which are not that difficult.  Delete everything you have in these folders:

%APPDATA%\Trados\Trados Studio\17\Plugins

%LOCALAPPDATA%\Trados\Trados Studio\17\Plugins

c:\ProgramData\Trados\Trados Studio\17\Plugins

Then restart Studio and reinstall them via the integrated AppStore in Trados Studio. This way you will only install the ones that will actually work with SR1. If your apps are not in the list yet then contact the developer via the support link at https://appstore.rws.com/ for the app in question (every developer has some form of contact details) and ask them to update their apps for SR1.

The DeepL app was one of the first to be updated so you really should not be experiencing any problems if you followed the instructions in the release notes... the ones we spend ages compiling and nobody ever reads ;-)

Hey Paul,

Thank you for the quick reply. I definitely appreciate your availability to help out with this stuff. I used to work in operations at a digital music distribution start-up in San Francisco, and I worked closely with the dev team. It's a lot of work integrating all the different specs and bits and bobs, for sure.

You're right, we don't read the release notes, we're busy working at 11 pm! lol

I did as you instructed, uninstalled the Microsoft/Google plug-in and installed the new Google Translate plug-in, but it only works when I save the file I'm translating as a project (and choose Google Translate in the project settings). However, when I simply open a file for translation without saving it, and click on Google Translate on the translation memory pop-up page, it says that the API key is already being used, and I'm not able to use the plug-in from there. Any ideas?

Hi Paul,

Another one guilty of not reading the release notes and getting myself into a mess with DeepL plugin here, apologies.

I tried Katherine's quick fix. But that didn't work, still the same error message. 

So I tried following your instruction above, but I am having difficulty finding these folders. The only Studio 17 plugin folder I found was at: C:\Program Files (x86)\Trados\Trados Studio\Studio17\Plugins - there were over 1,000 files in there, which I deleted, but then Studio would not even start up. So I swiftly recovered the deleted files, it then restarted. Am I looking at the wrong folder?

I have tried uninstalling the DeepL plugin and then installing the new version compatible with S1, but it still doesn't work. Please can you help? Can I uninstall the apps and then uninstall Studio altogether and then reinstall it without losing my data? Would that work?

Thanks for any help

Same issue here with many plugins. I've downloaded the Intento plugin for the first time after the latest studio update and it doesn't work. Suppose I need to wait until the developer updates that plugin right? Is there anything I can do as a user? 

Utku Tavsel 

Utku Tavsel said:

Is there anything I can do as a user? 

Contact the developer.

I did. Do you have any updates on Studio Subtitling? It's Trados' own plugin

Utku Tavsel 

Trados does not have any plugins.  We have a team that develops them and provides them... partially to support 3rd party developers as we opensource most of what we do, and partially to help create interesting solutions for things users want.  But I would not say they are Trados in a way that suggests we have to support them!  We don't!

Utku Tavsel said:

Do you have any updates on Studio Subtitling?

This one is actually tricky because it's very tightly integrated with the Studio Editor and the SR1 release contains substantial changes under the hood.  Some of these changes relate to an almost completely replaced Editor.  So we are still working on this one, but it may take a while as it's a very complex plugin.

We are prioritising it as best we can as we know it's a well used plugin.  So it will be available when it's ready.  I don't have timescales for this yet.

Utku Tavsel 

Trados does not have any plugins.  We have a team that develops them and provides them... partially to support 3rd party developers as we opensource most of what we do, and partially to help create interesting solutions for things users want.  But I would not say they are Trados in a way that suggests we have to support them!  We don't!

Utku Tavsel said:

Do you have any updates on Studio Subtitling?

This one is actually tricky because it's very tightly integrated with the Studio Editor and the SR1 release contains substantial changes under the hood.  Some of these changes relate to an almost completely replaced Editor.  So we are still working on this one, but it may take a while as it's a very complex plugin.

We are prioritising it as best we can as we know it's a well used plugin.  So it will be available when it's ready.  I don't have timescales for this yet.

Yes, it's extremely useful. Hope it's completed soon. Thanks!