#1 Global Leader in Data Resilience

How to Add Exclusions to Veeam Threat Hunter Scan

KB ID: 4688
Published: 2024-12-03
Last Modified: 2024-12-03
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Purpose

This article documents how to exclude files and folders from the Veeam Threat Hunter scan.

Solution

To exclude files or folders from Veeam Threat Hunter Scane, create the following registry value on the Veeam Backup Server:

Key Location: HKLM\SOFTWARE\Veeam\Veeam Threat Hunter\
Value Name: VTHScanExclusions
Value Type: Multi-String Value (REG_MULTI_SZ)
Value Data: (See notes below)

Value Data Notes:

  • One exclusion string per line.
  • Strings specify both file and folder names that will be excluded.
  • Wildcards may be used before, within, or after the string.
  • A wildcard can be anything within the path, so great care must be used when placing a wildcard in the middle of an exclusion string.
    Example: '\foo1*\foo2*\*' could be any number of folders deep (e.g., \foo113\folder\subfolder\foo212\ )
  • A wildcard and a folder separator are automatically prepended to each exclusion entry.
    Example:  'Documents*' will be handled as '*\Documents*'
  • Any included drive letter will be converted to a wildcard.
    Example: 'C:\Users\*\Documents*' will be handled as '*\Users\*\Documents*'
  • The exclusion string must be at minimum three (3) characters long.

Examples

The exclusion function looks at the entire file path of each file and checks if anything in that path matches an exclusion entry. Think of the exclusion string as a simplified form of regex.

  • '*.foo' would be handled as if it read '*\*.foo' and match any file path that ends in .foo because there is no wildcard after the value.
  • 'foo*' would be handled as if read '*\foo*' and match any file path containing a folder or file name starting with "foo" and their subfolders.
  • '\foo\*' would be handled as '*\foo\*' and match only folders that are named precisely "foo".
  • '\foo1*\foo2*\*' would be handled as '*\foo1*\foo2*\*' and match only to contents of a folder beginning with 'foo2' that is contained within a folder path that has a parent folder whose name begins with 'foo1' (e.g. \foo113\folder\subfolder\foo212\ ).
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.