Hello Barsam,

I'm sorry to hear about the issue you're experiencing. It seems like you've already tried a number of solutions, including resetting the window layout and reinstalling Trados Studio, but the problem persists.

Here's another method you can try:

Step 1: Close Trados Studio if it's currently open.

Step 2: Navigate to the following folder on your computer: C:\Users\[Your Username]\AppData\Roaming\SDL\SDL Trados Studio\15.0.0.0\BaseSettings.xml. Please replace [Your Username] with your actual username on your computer.

Step 3: Rename the BaseSettings.xml file to something like BaseSettings_old.xml. This is to create a backup of your current settings.

Step 4: Open Trados Studio. The software will create a new BaseSettings.xml file with the default settings.

Step 5: Try to open your file again and see if the issue persists.

If this doesn't resolve the issue, it might be related to the recent Windows updates you installed. While you've tried uninstalling some of them, the Servicing Stack update could be causing the problem. Unfortunately, as you've found, this update can't be uninstalled. In this case, you might need to wait for a new update from Microsoft that resolves the issue.

Please note that these steps are a workaround and may not resolve the root cause of the issue. If the problem persists, it might be best to contact a local IT professional who can take a closer look at your system.

Best regards,

RWS Community AI

Already tried the suggested workaround. It seems like this error has been around for years w/o a good solution.

Also, what would you suggest me do until Microsoft solves this issue (if the issue is indeed with Microsoft)?

Barsam Marasli 

Barsam Marasli said:

It seems like this error has been around for years w/o a good solution.

You're using 2019 which is not supported.  So if this is a problem with Studio a solution would have hopefully been added to 2021 or 2022.  But I'm not familiar with this issue so have no idea how long it's been round.  It certainly won't ever be fixed in 2019.

Barsam Marasli said:

Also, what would you suggest me do until Microsoft solves this issue (if the issue is indeed with Microsoft)?

If it's with Microsoft there is nothing we can do... you could try the trial version of 2022 and see if that's any better?

But I suggest you do a proper reset first just in case it is something you can resolve yourself.  

To do this just close Trados Studio and then rename this folder:

c:\Users\%username%\AppData\Roaming\SDL\SDL Trados Studio\15.0.0.0\

to c:\Users\%username%\AppData\Roaming\SDL\SDL Trados Studio\15.0.0.0_old\

Then restart Trados Studio and see if that helped.

Barsam Marasli 

Barsam Marasli said:

It seems like this error has been around for years w/o a good solution.

You're using 2019 which is not supported.  So if this is a problem with Studio a solution would have hopefully been added to 2021 or 2022.  But I'm not familiar with this issue so have no idea how long it's been round.  It certainly won't ever be fixed in 2019.

Barsam Marasli said:

Also, what would you suggest me do until Microsoft solves this issue (if the issue is indeed with Microsoft)?

If it's with Microsoft there is nothing we can do... you could try the trial version of 2022 and see if that's any better?

But I suggest you do a proper reset first just in case it is something you can resolve yourself.  

To do this just close Trados Studio and then rename this folder:

c:\Users\%username%\AppData\Roaming\SDL\SDL Trados Studio\15.0.0.0\

to c:\Users\%username%\AppData\Roaming\SDL\SDL Trados Studio\15.0.0.0_old\

Then restart Trados Studio and see if that helped.

Thank you Paul. After so many tries (including complete uninstall and install) I finally recovered some functionality that I can live with for the moment. I will try renaming 15.0.0.0 again after I deliver the job that is overdue. It seems like it is time to try v2022.

BTW, there are messages going back to 2011 (https://www.proz.com/forum/trados_support/192119-error_%22selectedtab_cannot_be_set_before_the_pane_has_been_added_to_a_panes_collection.html)

Barsam Marasli 

Barsam Marasli said:

there are messages going back to 2011

All in all... for 12 years not too many.  I really don't think this is specifically a Studio issue and for the volume we are seeing probably something better dealt with using a simple reset.  Users often see a message and because the main heading looks like something they've seen before they'll assume it's the same thing.  It may be... but it could just as easily be caused by something else altogether.  So even in that post the cause could be different for them all.