Hi Valérie Gravel

I think a View -> Reset Window Layout might solve this problem for you.  If it doesn't then try resetting Studio.  You could use this app for the reset and this will also explain what you will lose by carrying out a reset before you do it:

appstore.sdl.com/.../

But if you'd rather do this manually then rename this folder (just add _old to the end or something, it's not important what you rename it to) and restart Studio:

c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\15.0.0.0

So the path would become this:

c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\15.0.0.0_old

If you can't find this folder then you need to unhide your hidden files/folders:

www.howtogeek.com/.../

Hello,

thank you Paul. I already did this last week. I did it again this morning and it is not working (same error). It might be the file like Daniel suggested below. Is there a way to know if this kind of file is corrupted?

When I think about it, it's not the file since I can convert it into an xliff and generate target translations. 

When I think about it, it's not the file since I can convert it into an xliff and generate target translations. 

Hello, have you been able to proceed? I still get the message. Re-installed plugin, updated Studio 2019 which incurred the necessary upgrade to Multiterm and .dotnet.  I do not see a final response.

Thanks,  Ron

Hello, no, I was not able to proceed. I have re-installed the plug-in 3 times, I upgraded Studio and Multiterm, Windows update are also done... I still get the error message with the plugin.

Hi Valérie Gravel, Ronald Hewitt

I'd be happy to look at these with you next week if you have time?  Drop me an email and we can set up a call to look together over Skype or Team Viewer - pfilkin@sdl.com

Thanks Paul , I just send you an email.

Valérie

Thanks @Paul Filkin

Sending you an invite.

Ron

Hi Valérie Gravel

Thanks for your patience this afternoon while we tried to figure out why this would not work for you.  I have discussed this with the developer after the call and the problem is because the plugin is not supported on Windows 7 or earlier.  We are using components for the preview that are not supported by W7.

I have updated the wiki and the appstore description to reflect this.

Thanks Paul, I guess we will need to upgrade to W10 soon. 
Valérie

Yes... I believe Microsoft stop supporting W7 from the beginning of next year.  I imagine we will also do the same for all of our products.