Veeam Threat Hunter - force update?

If you read the help here it tells you when Threat Hunter updates which is before a scan and automatically - How Veeam Threat Hunter Works - User Guide for Microsoft Hyper-V

Note

Consider the following: Veeam Threat Hunter checks updates for malware signatures before running the scan, but not more often than every 1 hour. Note that the initial malware signature update may take longer than the subsequent updates.

I am not seeing a manual way to run updates but if it does before it scans a job then that should suffice to me in both cases.

Update on this, I reviewed the logs:

Funfact: The repo server (Windows - from that I screenshotted the log) is able to access the required URL with p443:

Right now I’m waiting for my support case administrator role to open a support ticket.

I have similar problem:

Start signature update
The directory C:\ProgramData\Veeam\Threat Hunter\Engines\{6b069423-129a-4467-87a6-351c3d2e2f5a} is not exist. Create the directory and make a full update.
DB update is started
CVeeamAntivirus_PerformUpdate failed.
Failed to update threat signatures: I/O operation timed out while receiving an HTTP response. Error code -2108

Ticket opened on Monday, but no progress yet, support agent only checks Threat Hunter requirements and limitations.
Mount server is behind company internet proxy, but Veeam License Update Server and Veeam Signature Update Server are accessible.

Start signature update
The directory C:\ProgramData\Veeam\Threat Hunter\Engines\{6b069423-129a-4467-87a6-351c3d2e2f5a} is not exist. Create the directory and make a full update.
DB update is started
CVeeamAntivirus_PerformUpdate failed.
Failed to update threat signatures: I/O operation timed out while receiving an HTTP response. Error code -2108

I would suggest at this point to keep going with the Support ticket you have as that is the best route forward since we are not support in the community.

​@lukas.k I’m guessing if you could use the test scripts to run a remote powershell with an signature update command, as you mention you are using sureback. I've never did that before, but I think that could help you .

AndrePulia wrote:

​@lukas.k I’m guessing if you could use the test scripts to run a remote powershell with an signature update command, as you mention you are using sureback. I've never did that before, but I think that could help you .

 

What test scripts do you mean exactly? I’m not aware of any public ones (and not unofficial ones either).

Update on the support ticket: The support provided some reg keys to skip the certificate revocation check like if seems. The environment on my customer’s site seems to be working now, my lab will be troubleshooted asap.

I will keep you posted!