Hi Michele Bradbury

The 'Remove suite of products' instance is indeed that which it says. It uninstalls SDL Trados Studio 2017 SR1. You can't modify it, only click on 'Uninstall' and it will remove Studio. 

However, as you say, in the list of Apps & Features, the only option for SDL Trados Studio 2017 SR1 entry is ALSO Uninstall, which is not as it should be. I don't know why.

To achieve the full features you should have accessible, type 'Control panel' into your 'Type here to search' window by your Windows start button bottom left of your screen (then if necessary select View by: 'Small icons') then click on 'Programs and Features' and you will see the more traditional version appear...

In this list, a right-click or a look at the top bar will show you that you can, again, uninstall using the 'Remove suite of products' instance but that if you highlight the main instance of SDL Trados Studio 2017 SR1, you also have the option to 'Repair'. This is a very useful feature and should be used now and again, after big Windows updates for example, to make sure that Studio runs smoothly with all its features. 

In fact, it is useful to run this 'Windows Repair' on any complex piece of software that has the facility.

Hope this helps!

All the best,

Alison

Hi Alison,

I did as you suggested and repaired the SDL Trados Studio 2017 R1 instance. I then uninstalled the SDL Trados 2017 R1 - Remove suite of products instance but then both instances disappeared. I re-installed Studio 2017 from the website but both instances still show up. Studio works fine except I cannot open a project from the file itself like I used to, only from Studio using the Open Package option. When I click on the .sldppx file, it opens a new instance of Studio but not the file itself. The .sdlppx, .sdlproj and .sdlprpx file types are associated with Studio 2017 so that does not seem to be the problem. . It is only a minor annoyance but I would like to be able to open the file directly from the file itself if possible. Any advice would be welcome.

Thanks. 

Michele

Hi Michele Bradbury

I'm sorry if I didn't explain clearly enough. Both instances are ALWAYS there and that is correct. The uninstall Studio 2017 entry is the best way to uninstall Studio and the main Studio 2017 entry is to be used for Windows Repair when it is needed. 

The Windows Repair wasn't a suggested solution for the two instances 'problem' as it isn't a problem because that is how the entries always appear, correctly. I was just explaining that you can use a Windows Repair when there IS a problem.

As for your problem with double-clicking a project package file opening a second instance of Studio, I can't reproduce this. It works fine for me. If I have Studio open and I click on a project package in Windows Explorer, then the same instance of Studio opens the Open Package Wizard correctly.

Maybe this time a Windows Repair of Studio (the main instance, not the uninstallation instance) might solve this?

In Control Panel > Programs and features, right click 'SDL Trados Studio 2017 SR1' and select 'Repair' from the dropdown menu that appears. Or click Repair on the toolbar at the top as in your image.

I hope this clarifies things...

All the best,

Ali

Hi Alison.

Thanks for the explanation. I'm happy to hear that seeing two instances of Studio in the list of applications is normal. As for the problem with opening a Studio package from the file itself, I did some searching and came across the following post:

https://community.sdl.com/product-groups/translationproductivity/f/studio/7319/how-to-restore-sdlppx-sdl-trados-studio-project-package-file-association

Paul Filkin mentions a Registry Editing solution because it seemed that HKEY_CLASSES_ROOT\.sdlppx pointed to the wrong version of Studio. In that case, the problem appeared after the user upgraded from Studio 2014 to Studio 2015. In my case, I upgraded from Studio 2015 to Studio 2017. I deleted the old 2015 but it's possible that some registry values may have survived. I checked the registry values and I found .sdlppx pointing to sdlppx_auto_file and further down sdlppx_auto_file with "value not set" under Data (screenshots are attached). At this point I'm wondering whether I should enter something (iSDL.TradosProjectPackage.1?) in the Value data field shown in the screenshot or remove both .sdlppx and sdlppx_auto_file then repair Studio as suggested by Paul.

Any advice? Thanks.

Hi Michele Bradbury 

I would not advise trying to make registry changes if the entries are not as Paul  described, as those instructions were created over 3 years ago and the registry setup for Studio may have changed since then.

Did you try running a Windows Repair again? Try it and see if it clears the problem.

If not, contact Installation Help as they will help you free of charge if re-installation has not solved your problem so that you can work as normal.

You can contact them here:

installation and licensing help

Fill out as many of your details as you can and select 'Installation' from the 'Case type' dropdown menu and explain your problem and what you have tried (Windows Repair and Re-installation).

Most important is to give your correct email address as that is how they will contact you. They usually reply fast.

All the best,

Ali :)

Thanks, Alison. I did as you suggested.

Hi Michele Bradbury 

Did you try a Windows Repair? If so, did it work?

If you contacted Installation Help, let me know what they found as the solution, so it will be here for future users to find if they have the same problem.

All the best,

Ali

Hi Alison,

Installation Help hasn't replied yet but, guess what, I turned on my computer this morning and the Open Package Wizard now appears when I click on the .sdlppx file! Perhaps re-directing HKEY_CLASSES_ROOT\.sdlppx to SDL.TradosProjectPackage.1 worked? In any case, I'm keeping my fingers crossed.

Thanks again for all your help.

Michele

Hi Michele Bradbury

I'm glad to hear that!

You're welcome,

All the best,

Ali