I might blame other software had the shortcuts not worked everywhere else after the BAM*

*Bug Appearance Moment.

Hi Adrian Komiński

Have you tried running a Windows Repair on Studio via the Control Panel?

It and other reset methods are described here:

Repairing your installation of SDL Trados Studio

If none of the solutions given on the above webpage help, you can then get free help with installation issues that are preventing you from working here:

Thanks for all the notes, but all I can say, having read this:

community.sdl.com/.../20730

is BULLLLLS**IT! Now we know it's a bug on your end, GIVE US A HOTFIX NOW (thinking I'm too demanding? I paid several hundred dollars for this, and we're in capitalism - get used to it)!

No one can work efficiently without basic shortcuts such as ctrl+a and ctrl+z.

I'm deeply disappointed with your attitude, SDL. The guy in the link above reported the issue on Dec 12. Now I'm reporting the same thing. This should have been immediately pointed out to the dev team and the dev team put on alert - if you treat your business seriously. You should have told me it's a known/suspected issue and you're working on it. Instead you're making some vague remarks and suggesting it's my problem (or maybe it was someone unaffiliated suggesting it - nevermind).

Again, I demand an immediate investigation into the problem. This is a serious dealbreaker; it just happened to me once again, and I refuse resetting the app several times a day. The problems with TM errors after SP1 are enough to make one pissed, and your ill-famed reputation for replacing one bugs with others is too well known in the industry for me to just decide living with this like that until maybe someone deals with it some time.

Btw. please be so kind and at least link me a resource with instructions on reverting to pre-SP - if at all possible. If it isn't, it definitely should be, because every single of your SPs have known to be a disaster for many of us.

Just happened again. Guess what helped - re-opening the translated document. Resetting layout doesn't help. What about that reversion to SR0? So far the only positive change I've seen with SR1 is correction of the "While you project" typo I had reported in the "ideas" section - the rest is just new bugs.

The same issue in my case. This never happened for Studio 2011 and 2014 which I also own. In my opinion, Studio 2019 is much more unstable and unpredictible software (not to use more unkind words).
Apart from this issue, I also experience "Search feature" not working for multiple documents in Editor. Search works for the first document opened in Editor only. When I press Ctrl+F in another document, it simply won't open/work. I must close all the other documents to use the search feature in a particular document. Very, very annoying. It worked ok in the previous versions.

Also there are issues with termbase settings window not loading. It never happened in Studio 2011 and 2014.

Finally, there is an issue with using the concordance for the selected/marked text in the source column. When I select a part of a segment and try to do concordance search for it, the concordance will search for the whole segment and not the selected/highlighted part. In order to search for the selected/highlighted part, I must click on the source segment again (and sometimes highlight a fragment/part again because it gets deselected). This is a real nuisance.
You would do us a much better favour, if you shifted some focus from your aggresive marketing to improving the actual code. Thank you.

"You would do us a much better favour, if you shifted some focus from your aggresive marketing to improving the actual code. Thank you."

This! Less conferences, more bughunting. Or how about you finally provide us with an actually working Word preview for which we paid money?

I downloaded the recent update, and duuh - issue persists, obviously. At this stage, what helps every time is switching between documents or windows within Studio. After this, all shortcuts work until some another time when the bug comes up again, for no apparent reason.

I did run Studio repair some month ago, I did try resetting layout, but I didn't post the support ticket yet. You know how it is - you can't afford doing it during working hours, and you REALLY don't feel like it PAST the working hours.

Both me and Łukasz work in the Polish Windows system (apparently), so that might be a hint.

EDIT: Also, the ctrl+n (new project) shortcut started "malfunctioning" recently. It wouldn't work until I hit "n" twice quickly. VERY odd. Works fine after Windows reset.

Looks like it might have something to do with Windows, alas. But that's not our problem. If you have issues with Microsoft, then resolve them. All I can tell is "ctrl+a" works fine elsewhere whenever it fails in Studio.

Adrian Komiński said:

"You would do us a much better favour, if you shifted some focus from your aggresive marketing to improving the actual code. Thank you."

This! Less conferences, more bughunting. Or how about you finally provide us with an actually working Word preview for which we paid money?

Well... we could ask the marketing team to spend their time fixing bugs but I don't think it would be very productive!

The Word preview.  Please log a case for this.  Make the time instead of posting in here.  You already know I can't repro your issues and whilst I don't doubt you are having real problems we're never going to get to the bottom of it unless we can work with you in your system.