Mateusz Fatek 

This is not the first time, that someone with Polish Windows is reporting massive problems with various versions of Studio. I have seen many such claims on Facebook before I left the corresponding groups. As a really heavy user of Studio I nearly never could reproduce such behavior on my various machines over the years. And I use German Windows since ever... Same for the Studio 2022 now. Even the betas do behave, although these do crash more often than production versions (as they are beta and I am testing them to help make them more robust). Of course Studio produces more error messages than for example Word. But the TO3000 version 11 (not 3D) crashes more frequently here (sometimes several times per day), so following the usual trend I'd suppose this software is worse than Studio. There are also other programs crashing, but TBH I do not experience big problems with any software used here.

I think it's interesting that you consider that resolution to be normal or acceptable 

Here's what Studio 2021 looks like with the "Change Scaling Behaviour" add-in:

This is what out-of-the-box 4k scaling look like, in EVERY other program I've ever encountered EXCEPT Trados Studio. "Change Scaling Behaviour" has not yet been updated for 2022, and Trados itself has NEVER fixed this issue in its own code. Rather ridiculous, considering that 4k has been standard for nearly 10 years and that seemingly every other software company on earth has managed to cope.

So Mateusz is right to find this unacceptable. There are a LOT of bugs that just get carried forward from version to version and never get fixed, like the inability to count words properly after merging or splitting segments. Or the general instability of the program that Mateusz refers to: I have the very latest/fastest laptop on the market with maximum RAM, and the program still crashes unexpectedly for no apparent reason. (Periodically, the common shortcut CTRL+C triggers a crash!)

That Ctrl+C has actually just crashed my computer! I agree with everything you wrote. Even an Intel i9, 64GB RAM and a quick SSD don't help - Trados is always slow and eager to crash unexpectedly. Three times today (so far) - with random errors. The latest was an error writing to a TM (a GS one at that). After opening the software again, however, the segment turned out to be correctly saved. So Trados crashed without a good reason.

I have some experience in software development (as a project lead), so I know what this could mean. It could mean that (and most probably does) that you are aware of this problem, but you decided not to address it. And not because it is rare, but rather because it lies deep within the core of your system and correcting this issue could possibly shatter the whole software, and you just cannot afford that (either you would be working on new patches and 2023 edition, or repairing the 2022). So you rely on third-party software to address such issues or just ignore them altogether, since the software otherwise works. And I really, REALLY, know this is standard practice for many companies—even the largest ones (I really, REALLY know that from personal experience). And it is a shame, since this is an industry-standard software, priced at a high level, with dozens of thousands of licenses sold globally, so one would surmise you could afford to finally make the switch to 64 bits and make the system more stable at least...

Michael Schubert 

This is how Outlook and Word look like on the same machine:

Outlook is even worse than Studio, as the possibilities to adapt fonts are really limited...

Mateusz Fatek 

Please check how current your Studio is. From what I remember there was a bug with shortcuts way ago...

Thank you but this is not a shortcut issue. I use this shortcut all day long in Studio, but just now - it crashed while i was using this exact shortcut. Studio just seems so ... wobbly lately. Unstable. I never seem to know what might set it off - as if it had moods of its own and crashed just for fun "because it can". Sometimes it feels that way :).

Also, currently I am using the newly-installed SR1. It is mere hours old :).

Wow—this works! I changed my Windows settings as you described and disabled the third-party "Change Scaling Behaviour" add-in, and the effect is the same: proper 4k scaling! Mateusz, you should be working for Trados Support, since you're smarter than anyone I've ever encountered there!

I'll try once again to upgrade (finally) to 2022 with the hopes that this will work there as well.

For anyone else following this thread, here are the English-language Windows dialog boxes. Right-click on Studio/MultiTerm icon, select Properties, then configure as follows:

Then click the Change high DPI settings box near the bottom and configure as follows:

Confirm and reboot.

Michael Schubert Mateusz Fatek 

Just for my understanding: you use high-resolution screens in Windows, but the Windows scaling is NOT set to 100%? Just to understand what is happening here.

For my built-in 13" laptop monitor, my scaling is set to 250% with a resolution of 3840x2400 (=4k).

For my external 27" monitor, my scaling is 125% with a resolution of 2560x1440.

For each display, these are the Windows-recommended resolutions, though I have personalized the scaling, (Windows recommends 300% and 100%, respectively.)

And it's important to note that I tried all manner of settings, but Trados always scaled wrong. It's the ONLY program that has this problem. All Microsoft programs and all other third-party programs were fine.

Michael Schubert 

Thanks. Now I understand where your problem is coming from. I do not use scaling. I buy a 4k monitor and like to use every pixel. Using scaling does not make any sense for me. If you scale 4k to 200%, you can as well buy a full HD screen to have the same effect.

Just my personal view, no offence.