Mox

Thanks Peter. The *.* wildcard seems to have done the trick. I added both of the exclusions you suggested, and re-installed GDFS. This configuration works fine. I then went back and removed the exclusion that specifies my username rather than using a variable. It still worked fine. For reference, here's the exclusion set that I'm currently using: /Volumes/GoogleDrive/* /Volumes/GoogleDrive/*.* /Users/%user%/Library/Application Support/Google/DriveFS/* /Users/%user%/Library/Application Support/Google/DriveFS/*.* /Users/%USER%/Library/Application Support/Google/DriveFS/* /Users/%USER%/Library/Application Support/Google/DriveFS/*.* So far, it's working fine with GDFS. I'm sure some of these rules are redundant... with more testing I'll probably be able to remove two or more.

Thanks Marcos. Excluding /Users/%user%/Library/Application Support/Google/DriveFS/* did not help. Even with that exclusion added, ESET still makes a Mac unusable when Google Drive File Stream is running.

Hello, We are evaluating ESET Endpoint Protection 6.5.600.1 on macOS High Sierra. We've discovered that ESET Endpoint Protection brings our Macs almost to a complete halt when Google Drive File Stream (GDFS) is running. GDFS becomes unresponsive, and all system activity becomes so sluggish as to make the system unuseable. We have tried excluding /Volumes/GoogleDrive/* (using Application Preferences > Protection > General > Exclusions > File System) but this did not seem to help. When users quit GDFS, the system performance returns to normal. Is there any other setting I can use to exclude GDFS in a way that will allow ESET Endpoint Protection to work with it?