AMbit

If they are being used for personal use and not business, then it shouldn't matter. One license should cover all VMs on the same machine as a licensed host computer.

And that was my thought exactly. It seems wrong to charge for two machines in this context.

I understand, but that's unfortunate, as the two use cases are very different. I guess I will have to find a different solution than using ESET. Thank you.

I know that ESET sells licenses for cases where multiple virtual machines are being used as actual separate functioning machines (e.g. server farm). However, for the case where a non-business user has a single virtual machine on the same computer ESET is installed on, where the VM is simply used for occasional testing, can the same ESET license work on that virtual machine? Or does ESET force you to buy another license for that use case?

Thank you, Marcos. That's exactly the information I needed!

Thank you. You're right that I probably did not have that section expanded. Although I would not expect anything to be copied to quarantine if they weren't actually modified or deleted. If you're right, then this setting is being applied even when the action is to Ignore a threat - which is unusual, and I would argue should not be how ESET behaves under these circumstances.

Right. However, those are On-Demand profiles. And since the scheduled scans I'm referring to all have a specific Profile specified as part of their configuration, I would expect that the profile settings (which includes the Threatsense Parameters configured for that profile) would apply. This understanding seems to be confirmed though the ESET documentation here, under the blue Note, where it says: Suppose that you want to create your own scan profile and the Scan your computer configuration is partially suitable, but you do not want to scan runtime packers or potentially unsafe applications and you also want to apply Strict cleaning. Enter the name of your new profile in the Profile manager window and click Add. Select your new profile from the Selected profile drop-down menu and adjust the remaining parameters to meet your requirements, and then click OK to save your new profile. To me, that part of the documentation indicates that the Cleaning section of the Threatsense Parameters configured for a given On-Demand profile will be honored when a scan is run using that profile. If that assumption is correct, then when I configure those profiles for "No cleaning", should it not behave the same as if I use the "Scan without cleaning" checkbox?

How is that the case, given that that setting exists under the configuration options for On-Demand scans?

I appreciate that you're going to look into it. However, how is the "Scan without cleaning" checkbox different then choosing "No cleaning" under the scan's Threatsense parameters? Wouldn't they both accomplish the same thing? The desired behavior is that I do want an alert to come up after the scan finishes that lets me choose what to do. What I don't want is for ESET to clean/delete anything automatically, nor do I want a silent scan where there is no post-scan alert and I wouldn't even know about any detections unless I manually checked the log afterwards.

I'm running v13.0.22.0, and I'm getting some odd behavior. So, here's the preliminary information: I have all scans set to "No cleaning". A scheduled scan ran and a post-scan alert came up showing me the detections it found (all in archives). I chose "No Action" for all of them. So far, so good. However, then I noticed this: Under the "Computer Scan" tab, the log entry shows "Scan completed: All detections cleaned". The Quarantine shows all of the files where detections occurred. The above items would indicate that ESET cleaned files that I explicitly told it not to touch. For ESET to modify/delete files I told it to leave alone, that would be bad. And yet, as far as I can tell, all of the files still exist in the file system and haven't been deleted. This is very confusing to me. If ESET correctly did as I instructed and ignored the detections, then I would expect that the log entry would show that detections were ignored, not cleaned. In addition, I would not expect anything to be added to the Quarantine. And yet, if ESET *did* clean all the files, then why are they still in the file system? Can anyone explain this odd behavior?