rambo919

Browsing the main site I noticed that all suites are marked as having linux protection but there are no downloads for linux.... also the legacy AV for Linux has download greyed out. A mistake somewhere or is the website being updated? I saw no announcements anywhere that the suites can now run on linux.

Sorry by the time I made this topic I had already uninstalled and was in the process of Installing EIS so the ESET logs might be as clean as the rest of the settings. Neva heard of ELC before, had to gogle that now. Neva had a problem remotely like this with ESET before so was unaware... for the moment it seems like everything is stable. Had to remove the windows registry as it made the files WAY too large for upload. eis_logs(filtered binary)noreg.zip eis_logs(original from disk)noreg.zip

Yesterday my ESS got a "client update please restart" notification..... after that restart the whole PC went haywire. Mostly my internet connection kept dying (this actually started before the actual restart). And I was unable to disable and re-enable the adapter in "network connection".... it just plain did not respond. If I try this and log off I get a error message telling me it cannot be disabled (forget the actual message). BUT then the PC hangs on restart forcing me to use the reset switch. Then I started noticing that after ESS loads half my apps refuse to either start or end, even using task manager to kill something does not work. And eventually even my start menu stopped working. Eventually I booted into safe mode and uninstalled ESS and rebooted..... No problems whatsoever. from event viewer at the time of uninstall "Windows Installer requires a system restart. Product Name: ESET Smart Security. Product Version: 10.1.219.0. Product Language: 1033. Manufacturer: ESET, spol. s r.o.. Type of System Restart: 1. Reason for Restart: 0." Looking at the forums I see that EIS supplanted ESS (having received absolutely no notification of this it was a complete surprise). Is this exclusively a ESS problem? PC: win7sp1

oh ffs, it was set to normal cleaning in startup scan.... Having to set it independently in 4 (hopefully not more) places instead of a universal toggle is what caused the problem. I'm fine with being able to set it separately but such settings should logically be treated more as settings exclusions because of how easy it is to miss. And no sharing the logs would be missing the point, I HAVE to set it to no cleaning because I have files that can be false positives around all the time and I cannot afford to loose them. My personal problem is that it should be up to ME not the AV to decide what is a false positive or not.... and yes I probably over reacted slightly in the OP. I will not be forced into a pathetic paranoid "the world is out to get me please someone protect me" state regarding my system no matter how well meaning the protector might be. The GUI not running when a threat is detected would be of no consequence as long as the default action (as it seems to be) is to simply block the process from being accessed/run until a action is decided upon.

As the title says. It finds a file it does not like and just cleans it then brags to you about it as if it did a good thing. I can live with the annoying big brother attitude that only a small minority of false positives can be dynamically added to the exclusions list, as patronizing as it already is. But this is the last straw, either fix it or I and my already short by this time temper am walking.