AGH1965

@Marcos Are you saying that detections from a sceduled scan will never appear in the Detections log? ESET Online Help says: "This log offers detailed information about detections and infiltrations detected by ESET Internet Security." No sign of distiction between scanners. Therefore I expect the Detections log to show all detections. Besides, what is the benefit of hiding some of the detections? Please try to keep the GUI logical!

This week EIS 12.1.31.0 discovered two trojans while scanning. Although I interupted the scan and didn't give EIS a chance to get rid of the trojans, I was surprised that Log files - Detections didn't show any detections at all. I assumed that it was caused by the interruption. Therefore I let EIS scan the folder containing the trojans again and when they were found again, I let EIS remove them. However, even after that, Log files - Detections didn't show any detections. On the other hand, Log files - Computer scans clearly showed that there were detections. It seems to me that Log files - Detections is no longer functioning in EIS 12.1.31.0.

A few days ago I experienced something similar with version 12.1.31.0 as @Rohit reported here above. When the system tray icon showed that EIS was busy doing something, I hovered my mouse over it and it showed that EIS was busy updating. A few minutes later I noticed that EIS was still busy and the icon suggested that EIS was still busy updating. Because I didn't believe that, I opened the EIS window. That showed that a scan was running. During the whole scan, which lasted several hours, the icon suggested that EIS was busy updating. It is just an assumption, but I have the impression that the tray icon gets "confused" when the scheduler starts multiple actions at the same time. For some odd reason the scheduler of 12.1.31.0 doesn't have any patience. It even starts another scan when there is already a scan running, even though running two scans sequenctially is probably much more efficient than running two scans at the same time.

It is very simple. Use SetThreadExecutionState. See: link to Microsoft Windows Dev Center.

Description: Prevent sleep during scan. Detail: Windows can put the computer to sleep before the scan is finished. That is very annoying. There should be an option to prevent that from happening. Oops, it's a coincidence that @zeromido asked someting similar here right above. Before I started typing, I first searched the forum for "scan prevent sleep".

Oops, I forgot to mention the good news: Except for the first scheduled scan with "as soon as possible" setting, which is replaced by a scan directly after configuring it, all other scheduled scans are either carried out at the scheduled time or carried out later if the system was offline at the scheduled time. So the "as soon as possible" option of the scheduler has defenitely been improved! Thanks ESET! However, missed scans with as soon as possible" setting are not really carried as soon as possible. Yesterday, after turning on my pc, I was waiting for EIS to start a scan it missed the day before. I waited for about 10 to 15 minutes, but EIS didn't start the scan. Then I turned off my pc and turned it back on again about an hour later. Then almost directly after booting into Windows EIS started the scan. Of course it's great that EIS started the missed scan, but why didn't it do that an hour earlier?

The scheduler not only starts a scheduled scan with "as soon as possible" option immediately after adding or modifying it, it also skips the first scheduled moment. As if it thinks: "You got one scan that you didn't ask for, but you won't get more scans than you ask for." Very strange.

Today first test done with v12.1.31.0. The modification has a strange side effect. Every time a scheduled scan with active "as soon as possible" option is added or edited, the scheduler seems to think that the scan was missed and starts it, even when it wasn't missed at all. That is rather annoying.

A cleanup option for firewall rules when using the interactive mode, that deletes all rules that are pointing to applications that no longer exist on the computer, would be very helpful indeed. (I fully agree with JoMos here above.) Especially now more and more applications move to a new folder with every update, the number of useless firewall rules grows rapidly. Deleting them manually isn't a pleasant job and keeping them might slow the firewall after some time.

Marcos, I will surely do that. Does your reply mean that v12.1 has an updated scheduler? That would be fantastic!

Even when someone uses an ESET forum to explain an alternative for an ESET tool, ESET remains silent. I'm disappointed.

Time for an update. About two weeks ago a configured the scheduler of EIS as shown in KB3207, except I configured a daily scan at 18:00 and I restricted it to operating memory and boot sectors/UEFI. The results are very quite disappointing. In all those days, the scan was only run twice and that was when the pc was on at 18:00. This clearly demonstrates that the scheduler completely ignores missed tasks. The "Immediately, if the time since the last run exceeds a specified value" combined with "24 hours" as shown in KB3207 isn't working at all. ESET, please fix this!

The remarks of itman about resuming from sleep made me realise something. I'm having this scheduler problem in both Windows 7 and Windows 10, but in both Windows versions I disabled hibernation. In Windows 10 I even disabled the fast startup option. So every startup of my systems is a complete fresh boot. Could this be of influence for the scheduler problem? Does the scheduler of EIS perhaps rely on hibernation?

OK, I will try the 24 hours setting, but remember that my original approach, i.e. using the "as soon as possible" option, didn't work either. So I think that the options for missed scheduler tasks are only present in the gui but not in the software underneath.

@COStark26: The comparison with MBAM doesn't make sense to me. In case of EIS it is not "time since last miss", but it is "time since last run". So if EIS misses a dayly scan, then the time since the last run is always more than 24 hours.

It is more than a week later now. The scheduler is still configured to perform a dayly scan at 18:00 and if that scan was missed, then it shall be done immediately if the time since the last run exceeds more than 1 hour. Each day the PC has been used for several hours, but never at 18:00. The result of this all is that the scheduler didn't run any scan at all. Tools > More tools > Log files confirms this. It would be nice if ESET would fix the scheduler, because what is the use of a scheduler if you have to remember yourself to turn on the PC on a certain time?

IE11 may be preferred by ESET, but banks find IE11 outdated. A few weeks ago the website of my bank suddenly showed a message saying that banking would still be possible with IE11, but only with restricted functionality. To continue banking as usual, switching to Chrome or Firefox was advised. (I can't remember if Edge was mentioned as well.)

@puff-m-d: Thanks for the advice! So the tool is better than expected. Thanks ESET. However, why is the default to show only TCP connections? Why give the impression that you can barely crawl if you are able to run?

That TCPView only shows TCP connections is logical if you look at the name. I agree. The EIS tool is called "Network connections". That name suggests that all network connections are shown.

I tried using the option "Immediately, if the time since the last run exceeds a specified value" with "Time since last run" set to 1 hour. Also with this option selected the Scheduler keeps ignoring missed scans.

Well, that is exactly what I expect from this option, but it doesn't work that way in EIS 12.0.31.0, neither on WIndows 7 nor on Windows 10. The Scheduler simply doesn't care about missed tasks, but that is nothing new. When I started using the Scheduler years ago in ESS 7.0.302.26 on Windows 7, the "As soon as possible" option already didn't work. Could it be of influence that both EIS (and previously ESS) and Windows are Dutch versions or that the user who turns on the PC after a missed task doesn't have administrator rights?

I use the Scheduler of EIS to run a scan on every Monday at 18:00. This works fine if the system is up and running at the scheduled time. If that is not the case, then the Scheduler completely ignores that I selected the "As soon as possible" option. The scan isn't executed at all. This week I tried something similar on another pc, but now I scheduled a daily scan at 18:00, although I know that this pc is almost never up and running at 18:00. On this second pc I get the same result: the Scheduler ignores that I selected the "As soon as possible" option. Is it normal that the Scheduler ignores the "As soon as possible" option?

Marcos, why initially show only three tools when all eleven tools fit easily in the window? Are you suggesting that some users prefer a clean, empty gui instead of a usable one?

Well, here another user who started with ESS 4 and I fully agree with Freesolo. His example concerning the Tools is spot on. It's absolutely ridiculous to show only three tools.

itman, apparently you don't use Windows 10. What you wrote, is not correct. Microsoft does not change the name of these apps with every update! No, Microsoft stores every update in a new folder. That is why "Application Modification Detection" does not recognize these updates as modifications.