Roger Sjölander

Better to remove the plugin folders and reinstall your apps using the latest ones.  I'm surprised you didn't see any notifications in Studio that you need to update some apps?  Main culprits that needed to be updated because CU8 broke them were:

Reports Viewer Plus

Transcreation

XLIFF Manager

But if I was you I'd simply delete these folders and reinstall through the integrated appstore:

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

c:\Users\[USERNAME]\AppData\Local\SDL\SDL Trados Studio\16\Plugins

c:\ProgramData\SDL\SDL Trados Studio\16\Plugins

OK, thanks, that worked. And no, I haven't seen any admonitions to upgrade any plugins. I am a bit surprised they can hijack and shut down such a basic function of Studio, though.

Oh well. Onwards and upwards. Until I send in a query about why I cannot (even now) get exported files to any place in the file system but the pre-chosen directory C:\Users\[user]\Documents\Export Files. Slightly annoying but easily worked around.

Roger Sjölander said:

I am a bit surprised they can hijack and shut down such a basic function of Studio, though.

Roger Sjölander

In a simple world I would be too... but this is a lot more complex than you might think. In this case, in CU8, some code that controlled which version of a shared component was used (shared with some plugins that use project related features) had an error in it that caused Trados Studio to take the latest available version it can find instead of the version shipping with Studio.  These plugins mentioned earlier all used an enhanced version which should have been put into CU8 for Trados Studio.  But it wasn't.  So as a result if you have these plugins installed, Studio finds the new component and then attempts to use it... fails... and Studio hangs.  Since Trados Studio isn't tested against every single plugin anyone ever develops the fact the scheduled update of this component in Studio was omitted didn't get found.

It's often things like this... which can get very complicated and difficult to track... which can cause a bug.  In this case planned improvements that didn't get completely finished ended up causing a problem.  So we have "downdated" the plugins since we have more control over this, until the next Studio release and we will ensure these three plugins that share this component always form part of the QA process in future.

Hope that explains the problem for you?

Roger Sjölander said:

I am a bit surprised they can hijack and shut down such a basic function of Studio, though.

Roger Sjölander

In a simple world I would be too... but this is a lot more complex than you might think. In this case, in CU8, some code that controlled which version of a shared component was used (shared with some plugins that use project related features) had an error in it that caused Trados Studio to take the latest available version it can find instead of the version shipping with Studio.  These plugins mentioned earlier all used an enhanced version which should have been put into CU8 for Trados Studio.  But it wasn't.  So as a result if you have these plugins installed, Studio finds the new component and then attempts to use it... fails... and Studio hangs.  Since Trados Studio isn't tested against every single plugin anyone ever develops the fact the scheduled update of this component in Studio was omitted didn't get found.

It's often things like this... which can get very complicated and difficult to track... which can cause a bug.  In this case planned improvements that didn't get completely finished ended up causing a problem.  So we have "downdated" the plugins since we have more control over this, until the next Studio release and we will ensure these three plugins that share this component always form part of the QA process in future.

Hope that explains the problem for you?