Since upgrading to a new laptop with Windows 11 24H1 I am having difficulties running Studio without the application getting blocked by Smart App Control as the publisher Studio seemingly cannot be verified. As Smart App Control seems a pretty important security feature which cannot be re-activated upon de-activation without completely re-installing windows, I am rather hesitant to de-activate it. Any suggestions otherwise? Maybe this is something Trados should urgently remedy?
Smart App Control seems a pretty important security feature which cannot be re-activated upon de-activation without completely re-installing windows
It's not a mainstream security feature that most people are likely to rely on daily. It’s off by default for most users and only auto-enables itself on clean installs of Windows 11. It’s more experimental than critical, and even Microsoft presents it as an advanced security feature for “extra peace of mind,” not essential system protection.
It's also an unusual concern I think. SAC is either On, Evaluation, or Off, and once set to Off, it cannot be turned back on without a clean Windows install. But the number of users for whom that would be a make-or-break issue is most likely small.
Maybe this is something Trados should urgently remedy?
If Trados Studio hadn’t signed some binary properly or was bundling components with broken or unverifiable signatures, then yes it should absolutely be fixed. But if the application is correctly signed and trusted (which it should be), this points more to SAC being too aggressive or misconfigured.
David Watson maybe you have some thoughts on this?
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Smart App Control seems a pretty important security feature which cannot be re-activated upon de-activation without completely re-installing windows
It's not a mainstream security feature that most people are likely to rely on daily. It’s off by default for most users and only auto-enables itself on clean installs of Windows 11. It’s more experimental than critical, and even Microsoft presents it as an advanced security feature for “extra peace of mind,” not essential system protection.
It's also an unusual concern I think. SAC is either On, Evaluation, or Off, and once set to Off, it cannot be turned back on without a clean Windows install. But the number of users for whom that would be a make-or-break issue is most likely small.
Maybe this is something Trados should urgently remedy?
If Trados Studio hadn’t signed some binary properly or was bundling components with broken or unverifiable signatures, then yes it should absolutely be fixed. But if the application is correctly signed and trusted (which it should be), this points more to SAC being too aggressive or misconfigured.
David Watson maybe you have some thoughts on this?
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Translate
