Worth checking if you installed the application as administrator. If you didn't then just install again over top, but right-click and select "Run as administrator" when you install. If that doesn't help then try a reset. 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

If that still won't help then I'd recommend you log a support case. For licensing or installation issues that prevent you from working we have a route for all customers to get help. This can be achieved really quickly using this link:

gateway.sdl.com/liveagentlicensing

You have two options:

1. Submit a case using a webform

2. Use live chat to get a licence reset

You want to use the first option.

Above text copied from a previous post by Paul...

Hope it helps!

All the best,

Alison

Unknown said:

Worth checking if you installed the application as administrator. If you didn't then just install again over top, but right-click and select "Run as administrator" when you install.

This suggestion, repeated all over the Internet, is actually pointless.
If an installer requires to be run as administrator (and is built correctly), this information is present inside the executable file and the installer automatically asks for administrative level when launched.
So it's pointless to "Run as administrator" as it won't change anything, it will behave exactly the same way as if run normally.

This is an example of the information inside the executable:

  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <requestedExecutionLevel level="requireAdministrator" uiAccess="false"></requestedExecutionLevel>
      </requestedPrivileges>
    </security>
  </trustInfo>

Unknown said:

Worth checking if you installed the application as administrator. If you didn't then just install again over top, but right-click and select "Run as administrator" when you install.

This suggestion, repeated all over the Internet, is actually pointless.
If an installer requires to be run as administrator (and is built correctly), this information is present inside the executable file and the installer automatically asks for administrative level when launched.
So it's pointless to "Run as administrator" as it won't change anything, it will behave exactly the same way as if run normally.

This is an example of the information inside the executable:

  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <requestedExecutionLevel level="requireAdministrator" uiAccess="false"></requestedExecutionLevel>
      </requestedPrivileges>
    </security>
  </trustInfo>

...though the rest of my suggestion is still worth following through with, E. Macki

All the best,

Ali :)

(edited because I couldn't add the link correctly via my mobile)

Unknown said:

I'm looking forward to seeing if anyone can confirm this...

Anyone with a knowledge how Windows applications, User Accounts Control (UAC) and rights elevation work, Ali ;-)