Evermore

Good God. You people just are incapable of focusing on the topic at hand. You don't need to know ANYTHING about what was actually detected to respond to my post. I was ONLY commenting on the fact that I shouldn't have to manually enter the path and filename in the field. There is a BROWSE function, so why is it not FUNCTIONAL? Why is it even there if you recommend not using it because the software will not let it work? I'm done with this. It's bad design, it's that simple.

It's detected as a trojan, which it's not. It's just a tool that does something that CAN be used maliciously but is NOT in this case. I don't mind that this type of thing is detected because normally one would not want this to be happening but this is a TOOL that I need to use for legitimate reasons. It's a PowerShell script that just has .txt as a file extension. There is no "existing exclusion". Restoring from quarantine doesn't create an exclusion as I mentioned (that option is grayed out) and I CANNOT CREATE THE EXCLUSION EXCEPT BY MANUALLY TYPING THE PATH AND FILENAME. What are you not getting about this? Stop reciting what's in your response scripts and actually read. My complaint is that I can't just follow the steps to select the file and add an exclusion without MANUALLY TYPING THE PATH AND FILENAME. It's impossible to add an exclusion using the obvious method of selecting the file after browsing for it, the method that ESET's own instructions give, because selecting the file immediately deletes it so I can't press OK to have the file's path and name put into the exclusion path field. It has to be done manually, and claiming that it's a two-step process "for security" is ridiculous and insulting (not to mention it doesn't work the way you said). It takes plenty of effort to even get to the exclusions, and what's the point of even having a "browse" option if you can't actually use it? Why prevent me from simply adding the exclusion in the same step as restoring it from Quarantine? And excluding the entire folder isn't a good idea when it's just a temp folder with a bunch of other unrelated files, and you shouldn't blindly recommend that to users without information about what the folder contains.

The detected "danger" is irrelevant. In the Add exclusion dialog, nothing was "entered" that is relevant. I followed the instructions from ESET and clicked the ..., browsed to the file I wanted to exclude and selected it and clicked Open, which caused it to be instantly detected and quarantined so it could no longer be selected. I had to manually type the path and filename and click OK to enter the exclusion, and restore it from quarantine in order to have the exclusion work. Selecting the file from the dialog to add it to exclusions should not cause the scanner to detect the contents of the file and delete it. It's that simple.

I have a PowerShell script saved as a .txt file which NOD32 suddenly decided needed to be deleted when I did a search with a utility that scans for text inside files, even though the file has existed for 5 months and wasn't detected as bad previously when created or opened. NOD32 decided it's a "trojan downloader", and it does download .cmd script files and I don't expect ESET to have vetted every tool like this, so I'm not upset that it's detected, but excluding it was really difficult and I'm just wondering why it happens this way. I couldn't restore from quarantine and exclude it in one step because the option was grayed out. I went to add an exclusion in settings, and browsed to the file and selected it and clicked Open, and that caused the file to be scanned and sent to quarantine so it couldn't be added to the exclusions because it didn't exist anymore. The only way to add it was manually putting in the path and file name. Why does the program scan a file that you're trying to add as an exclusion and remove it so it can't be excluded? Why can't this file type be restored from quarantine and excluded in one step? Why are any files not allowed to be handled that way? Why does it take digging so far down into the Advanced settings to add an exclusion? (NOD32 has always had a ridiculously complex set of options and steps required to change them.)