Can you make one of the affected persons try running this before they start eclipse?
"%programfiles%\Windows Defender\mpcmdrun" -scan -file "full_path_to_eclipse_installation" If that helps, we could potentially add this to the installer (but not the ZIPs, of course), in the hope Defender afterwards remembers it already scanned the installation. However, I have no experience with the above, I just googled around for cmd line interaction with defender. There are also more options (like different scan types), not sure if that makes an additional difference. Another potential issue to check: Windows marks downloaded files automatically as "unsafe". See https://www.howtogeek.com/70012/what-causes-the-file-downloaded-from-the-internet-warning-and-how-can-i-easily-remove-it/ for an instruction of how to remove that marker from many files. I'm not sure if this really has any relation with Windows defender scans, I think it only triggers the "Do you really want to..." popup. That all being said, at our company we have given up to find something better than filters as workaround. With TrendMicro Antivirus on access scanning being active, every git operation inside eclipse is about 10 times slower than with eclipse filtered from the scan. Ciao, Michael _______________________________________________ platform-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
