Everything (by voidtools) is prevented from working

[DreamAlive 1]

Hello,

It seems the latest version of Everything (1.4.1.1026) is being prevented from working. Not the first time this occurs. I understand that a very recent version can cause false positive issues, but it's annoying that there isn't a quick and easy way to exclude it and just make the program work for an individual user.

I've tried restoring it from Quarantine, reporting it to LiveGrid and VirusTotal but nothing seems to work. It keeps getting blocked. I guess it'll probably work if I disable protection entirely but that seems way too nuclear an option. Haven't tried yet manually adding specific file/folder exclusions, but that also doesn't sound ideal and there's no quick way of doing it, either.

Can't we have a quick way to bypass such issues and allow programs with similar issues, please?

EIS 17.2.7.0, Windows 10
https://www.voidtools.com

 

 

Edited August 2 by DreamAlive

[itman 1,756]

First, the Eset detection;

Quote

Time;Scanner;Object type;Object;Detection;Action;User;Information;Hash;First seen here
8/2/2024 8:55:54 AM;Real-time file system protection;file;C:\Users\xxxxxx\Downloads\everything.exe;Suspicious Object;cleaned by deleting;xxxxxxxxx;Event occurred during an attempt to access the file by the application: C:\Windows\explorer.exe (F2B5E530B453A69CF23F2166E48BCF5749A9429A).;B0458BFC15492416E15F3A8F77F9FBBAC856F261;8/2/2024 8:54:33 AM

1. Create an Eset real-time hash exclusion for the above hash value (shown in bold text);

2. Restore everything.exe from Eset Quarantine file.

Disclaimer: Note that if the file does contain any malware, Eset won't detect it.

Edited August 2 by itman

[Marcos 5,293]

This was a false positive, the file has been unblocked in LiveGrid. Try rebooting the machine if the file is still blocked or temporarily create a detection exclusion as shown above (ideally also with the detection name set to make it more secure).

[itman 1,756]

7 minutes ago, Marcos said:

ideally also with the detection name set to make it more secure).

Tried that using "Suspicious Object" detection along with hash value and it didn't work.

What was strange here is that when the .exe was originally detected by LiveGrid, I received what appeared to be the actual detection name from LiveGrid in Eset log format as a popup, but it was never created in the Eset Detection log. I couldn't duplicate this in subsequent testing of this .exe.

[DreamAlive 1]

It now works, since you've unblocked it. I'd still prefer to have a handy "Allow this program" option with immediate results.

I'm guessing you might think this could be a risky option, leading users to allow things uncontrollably. Perhaps its activation could be hidden somewhere deep in Advanced setup and it could even be made to have temporary effect, i.e. until LiveGrid sorts it out, one way or the other.

Edited August 2 by DreamAlive