Hello Petrus Inghels 

Try to reset Studio settings as described in this article: https://gateway.sdl.com/apex/communityknowledge?articleName=000001417

Thank you,

Sorin

I am afraid this did not work. 

Petrus Inghels 

Can you confirm which version of Trados Studio you are using, also what your source file is?

It does sound like a keyboard clash somewhere... I wonder if you have been able to note what you might have been pressing when it activates?

Petrus Inghels 

Can you confirm which version of Trados Studio you are using, also what your source file is?

It does sound like a keyboard clash somewhere... I wonder if you have been able to note what you might have been pressing when it activates?

Hi Paul,

I am using SDL Trados Studio 2019 Freelance SR2 15.2.8.3007. 

As far as I can tell this is a randomly occurring thing, I have not been able to make out any particular key combination as the culprit. It only occurs in SDL Trados Studio, not in any other program on my laptop.

I have also tried troubleshooting the keyboard driver using Microsoft inbuilt keyboard troubleshooter to see whether anything is amiss there, but to no avail.

gr.

Peter

Petrus Inghels 

You already tried  renaming this folder and restarting?

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\

If you did, try assigning a shortcut to the preview to ensure there are no hidden defaults triggered by a keystroke combination.

Do you use any other software that might impact here... like AHK or some other keystroke tools?

Hi Paul,

Yes, I renamed c:\Users\%username%\AppData\Roaming\SDL\SDL Trados Studio\15.0.0.0\, but that did not yield a positive result.

However, I am using AHK. If this is the culprit, Trados seems to be the only program affected by it.

I'll investigate some more.

Tx.

Peter

Petrus Inghels 

Petrus Inghels said:

Trados seems to be the only program affected by it.

All programs are different... just because one isn't affected doesn't mean others won't be.  It all depends where a clash might be.  Fastest check would be to suspend AHK from running and then work a while and see if the problem is still there.  If it is then we know it's not AHK... if it isn't then you can investigate each script you're running one at a time to see if you can spot where the clash is coming from.