• State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 431 subscribers
  • Views 3274 views
  • Users 0 members are here
Options
Related

Windows Defender exclusions for Studio

Bruce Campbell

I currently have the following folders excluded in Windows Defender:

C:\Program Files (x86)\Common Files\SDL

C:\Program Files (x86)\SDL

I thought that excluding these folders would prevent Windows Defender from monitoring Studio, but the MsMpEng.exe process jumps to around 5% to 10% of my CPU when I do heavy processing in Studio. (Otherwise, it is generally around 0%.)

Have I missed something?

Regards,
Bruce Campbell
ASAP Language Services
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hi Bruce,

    I'm not familiar with problems here but I know we usually advise customers to exclude this:

    C:\Program Files (x86)\SDL\SDL Trados Studio\Studio5\SDLTradosStudio.exe

    Perhaps you have a mechanism for being more specific even though the top level you already excluded seems as though it should do the trick.

    Regards

    Paul

    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

  • 0 in reply to Paul

    Hi Paul,

    Interestingly enough, excluding files and folders does not work as I had expected.

    While I was playing around with the exclusions, I noticed that Defender was mainly focusing on the Telemetrics service. If I turned the service off, MsMpEng.exe used far less CPU.

    I found a discussion on the Internet about Defender chewing up CPU because a program was accessing a large number of log files. It appears that this is by design, as Defender has to determine whether the files should be scanned or not -- even though it ends up not scanning them. Excluding the program as a process was suggested.

    Perhaps the SDL Telemetrics service does something similar.

    Anyway, I specifically excluded the Studio program and SDL Telemetrics service as *processes* (including the complete path to the files), and the MsMpEng.exe process now uses 0% CPU.

    Live and learn...

    Best regards,
    Bruce Campbell
    ASAP Language Services
Reply
  • 0 in reply to Paul

    Hi Paul,

    Interestingly enough, excluding files and folders does not work as I had expected.

    While I was playing around with the exclusions, I noticed that Defender was mainly focusing on the Telemetrics service. If I turned the service off, MsMpEng.exe used far less CPU.

    I found a discussion on the Internet about Defender chewing up CPU because a program was accessing a large number of log files. It appears that this is by design, as Defender has to determine whether the files should be scanned or not -- even though it ends up not scanning them. Excluding the program as a process was suggested.

    Perhaps the SDL Telemetrics service does something similar.

    Anyway, I specifically excluded the Studio program and SDL Telemetrics service as *processes* (including the complete path to the files), and the MsMpEng.exe process now uses 0% CPU.

    Live and learn...

    Best regards,
    Bruce Campbell
    ASAP Language Services
Children