3 ms·

If real-time monitoring is running, try adding exceptions for your source and build outputs. It prevents antimalware from watching changes in those folders whic

If real-time monitoring is running, try adding exceptions for your source and build outputs. It prevents antimalware from watching changes in those folders which can really slow down a build or sync.

to3m 9y ago
I've always been a bit wary of doing that, as I've seen infected EXEs committed to version control a number of times because of it :( What I have done - well, what I think I have done! - the UI is appalling - is added SourceTree.exe and git.exe as exclusions. My intention here is that the antimalware service won't then monitor their activity while they're doing stuff, but will still check working copies when it does a routine scan... but sadly this didn't seem to make any difference at all, literally none whatsoever, and SourceTree continued to be what I can only describe as "slow as fuck" - if you'll forgive the technical jargon. The odd thing is, though, which just occurred to me like literally right now, it might actually be safer to add the folder exclusion after all! Because then there's zero risk of the Javascript interpreter springing into action :-| What a time to be alive! (But I still stand by everything I said about POSIX.)
- pitay 9y ago
  The malware protection system running uses a filesystem minifilter so may not matter what executable is running just that files are changed in the NTFS filesystem. So the grandparent post has great advice. It is definitely worth trying even if you may not want it to be the long term solution.
Klathmon 9y ago
I tried that but still saw significantly reduced build times when working on some projects. I think it has something to do with the temp file directory (which I don't want to whitelist for obvious reasons), so I just deal with disabling it when I build. At this point I've memorized the keys to hit to quickly disable and re-enable defender's real time protection (winkey > "defen" > enter > tab > (down to disable, up to enable) > alt + F4)

If real-time monitoring is running, try adding exceptions for your source and build outputs. It prevents antimalware from watching changes in those folders which can really slow down a build or sync.

to3m 9y ago

I've always been a bit wary of doing that, as I've seen infected EXEs committed to version control a number of times because of it :( What I have done - well, what I think I have done! - the UI is appalling - is added SourceTree.exe and git.exe as exclusions. My intention here is that the antimalware service won't then monitor their activity while they're doing stuff, but will still check working copies when it does a routine scan... but sadly this didn't seem to make any difference at all, literally none whatsoever, and SourceTree continued to be what I can only describe as "slow as fuck" - if you'll forgive the technical jargon. The odd thing is, though, which just occurred to me like literally right now, it might actually be safer to add the folder exclusion after all! Because then there's zero risk of the Javascript interpreter springing into action :-| What a time to be alive! (But I still stand by everything I said about POSIX.)

pitay 9y ago
The malware protection system running uses a filesystem minifilter so may not matter what executable is running just that files are changed in the NTFS filesystem. So the grandparent post has great advice. It is definitely worth trying even if you may not want it to be the long term solution.

Klathmon 9y ago

I tried that but still saw significantly reduced build times when working on some projects. I think it has something to do with the temp file directory (which I don't want to whitelist for obvious reasons), so I just deal with disabling it when I build. At this point I've memorized the keys to hit to quickly disable and re-enable defender's real time protection (winkey > "defen" > enter > tab > (down to disable, up to enable) > alt + F4)