Why is avast! detecting component of this program without quarantining the component? It’s just deleting it directly so I can’t even bloody report it as false positive or restore it with exclusion. So freaking annoying. Please fix it.
It’s actually detecting the component within it, not the installer itself… It all goes off during installation so I don’t even know what’s the file exactly…
I rather doubt RejZoR requires help - since he is a long term forum member and avast user (over 11 years) - I believe he is simply bring this anomaly to avasts attention, not to delete in this way.
Yeah he is a long term avast user and I was just trying to get answers from him. If I someday install that program I may come up with issues and problems. Also just trying to help him out
It happened once before that avast! was just deleting a file even though it is set to quarantine files. I don’t understand why it makes such exceptions for some files. It adds unnecessary problems finding things out, especially since there is no central log, but you have to dig out text log files from user profile which is further annoying.
Hello,
maybe you don’t have enough space in chest – check settings. How big space is reserved for chest and how many space is occupied by files in chest and how big is the file, which should be moved to chest.
I just wonder if it exceeds the max file size to send to the chest, given that the detection was within an installation file, does it exceed the 16MB max file size to send to the chest ?
There used to be a nondescript/confusing error message before about insufficient space, most thought it related to space on the hard drive and not the default sizes for the chest.