Thank you for posting the details, can you please a screenshot? We usually add information about the affected extension, so fill event details and a screenshot would help a lot to understand the issue.

Thank you for posting the details, can you please a screenshot? We usually add information about the affected extension, so fill event details and a screenshot would help a lot to understand the issue.
Hello Jason,
Code: Select all
*.oxr
*.dop
*.afd
*.ttt
*.wiki
*.fixed
Stay tuned, I've asked QA team to reproduce the issue. Possibly it's related to email reporting and not to the detection engine itself.
Dima, see below. There isn't any detail in the History > Malware Detection > Malware Event logging in the GUI. I also do not have any suspicious_files log files in C:\ProgramData\Veeam\Backup\Malware_Detection_Logs that are on the same date as the detections noted in my screenshot.
everyones opinion is going to vary, but if we are supposed to investigate a potential issue i know i personally would need the entire list. I think at the moment we are all not dealing with a large number of log entries. Mostly because none of us are responding to a real incident. So the idea that not logging these because it could be too big seems to be overly cautious.
I've asked support team to reach you and help to collect the logs, looks like we still need those. They will reach you out via your forum's email address.This is a home lab with NFR license. Can I raise a support case? The company that I work for is a ProPartner with Veeam but I'm out in the field and this lab is for personal, educational use.
cgsm,
Adding to this: what about a flag in the preferences so that we can toggle the logging of all suspicious files, default is disabled and can be enabled when an in-depth analysis is required.
Users browsing this forum: Google [Bot] and 65 guests