We migrated ticketing systems!

If you would like to check on the status of a ticket, please visit huntress.zendesk.com.

For the time being, our documentation will stay the same, we will make a hard cutover when all the documentation is ready. The Huntress Support site will continue to be support.huntress.io, it will just come with a new look and feel.

Click here to check the status of a ticket


Are Huntress exclusions necessary in third-party AV?

Typically Huntress does not need to be whitelisted within third-party Antivirus. Since the Agent isn't making any changes and is operating in read-only mode it usually does not get flagged. That being said, there are occasions where a third-party AV is present with alert settings on high, resulting in the Huntress Agent being flagged. 

Note on some "Next-gen" AVs: The Huntress Agent scans auto-runs in read-only mode and hashes the files. This tips off some NGAV products, please create exclusions if you are experiencing network slow-down, CPU spikes, etc. related to the Huntress Agent. 

We have observed unintended behavior when the Huntress Agent is not whitelisted from the following products: 

  • SentinelOne
  • ESET
  • BitDefender

You can choose to whitelist the entire folder C:\Program Files\Huntress, or the executable file paths. 

C:\Program Files\Huntress\HuntressUpdater.exe

C:\Program Files\Huntress\HuntressAgent.exe

C:\Program Files\Huntress\wyUpdate.exe