Hi Bruce,

This is what I do, but this isn't a recommended method via support or anywhere else.  But I install/reinstall a lot for testing and it works for me.  First I uninstall Studio from the Windows Control Panel and then I run a batch file with the following commands:

Unknown said:

rd /s /q "%USERPROFILE%\AppData\Local\SDL\SDL Trados Studio\12\"
rd /s /q "%USERPROFILE%\AppData\Local\SDL\SDL Trados Studio\12.0.0.0"
rd /s /q "%USERPROFILE%\AppData\Roaming\SDL\SDL Trados Studio\12"
rd /s /q "%USERPROFILE%\AppData\Roaming\SDL\SDL Trados Studio\12.0.0.0"

rd /s /q "%USERPROFILE%\Documents\Studio 2015\Project Templates"

DEL "%USERPROFILE%\AppData\Roaming\SDL International\Sdl.Enterprise.CredentialProvider.xml"
DEL "%USERPROFILE%\AppData\Roaming\SDL International\Sdl.Enterprise.ServerConnectionManager.xml"
DEL "%USERPROFILE%\AppData\Roaming\SDL International\Sdl.ProjectApi.CustomCredentialProvider.xml"
DEL "%USERPROFILE%\AppData\Local\SDL International\Sdl.Enterprise.ServerConnectionManager.xml"

rd /s /q "c:\Program Files (x86)\SDL\SDL Trados Studio\Studio4\"

This doesn't remove my data files, so projects and TMs and termbases etc are all left intact.  It will remove my project templates however, so be aware of this.  However it does a pretty good job of ensuring I have a clean install again.  There are no warnings with this script, so be sure you want to do it before running it.  You could remove the /q and you should get a warning for each folder before deletion.

If you want to retain old settings, and this is probably not recommended since there's a good chance you'll just bring any problem you were trying to resolve back in again, then don't remove this one - AppData\Roaming\SDL\SDL Trados Studio\12.0.0.0

You could also leave the Studio\12 folder too if you like as this contains plugins from the OpenExchange and it'll save you having to reinstall them all again.

So, don't necessarily take this as gospel, this is just what I do and I don't use the software for production.  But it quickly allows me to do as clean an installation as possible based on my requirements.

Regards

Paul

Hi Bruce,

This is what I do, but this isn't a recommended method via support or anywhere else.  But I install/reinstall a lot for testing and it works for me.  First I uninstall Studio from the Windows Control Panel and then I run a batch file with the following commands:

Unknown said:

rd /s /q "%USERPROFILE%\AppData\Local\SDL\SDL Trados Studio\12\"
rd /s /q "%USERPROFILE%\AppData\Local\SDL\SDL Trados Studio\12.0.0.0"
rd /s /q "%USERPROFILE%\AppData\Roaming\SDL\SDL Trados Studio\12"
rd /s /q "%USERPROFILE%\AppData\Roaming\SDL\SDL Trados Studio\12.0.0.0"

rd /s /q "%USERPROFILE%\Documents\Studio 2015\Project Templates"

DEL "%USERPROFILE%\AppData\Roaming\SDL International\Sdl.Enterprise.CredentialProvider.xml"
DEL "%USERPROFILE%\AppData\Roaming\SDL International\Sdl.Enterprise.ServerConnectionManager.xml"
DEL "%USERPROFILE%\AppData\Roaming\SDL International\Sdl.ProjectApi.CustomCredentialProvider.xml"
DEL "%USERPROFILE%\AppData\Local\SDL International\Sdl.Enterprise.ServerConnectionManager.xml"

rd /s /q "c:\Program Files (x86)\SDL\SDL Trados Studio\Studio4\"

This doesn't remove my data files, so projects and TMs and termbases etc are all left intact.  It will remove my project templates however, so be aware of this.  However it does a pretty good job of ensuring I have a clean install again.  There are no warnings with this script, so be sure you want to do it before running it.  You could remove the /q and you should get a warning for each folder before deletion.

If you want to retain old settings, and this is probably not recommended since there's a good chance you'll just bring any problem you were trying to resolve back in again, then don't remove this one - AppData\Roaming\SDL\SDL Trados Studio\12.0.0.0

You could also leave the Studio\12 folder too if you like as this contains plugins from the OpenExchange and it'll save you having to reinstall them all again.

So, don't necessarily take this as gospel, this is just what I do and I don't use the software for production.  But it quickly allows me to do as clean an installation as possible based on my requirements.

Regards

Paul