Jump to content

AGH1965

Members
  • Content Count

    82
  • Joined

  • Last visited

  • Days Won

    2

AGH1965 last won the day on May 28

AGH1965 had the most liked content!

Profile Information

  • Location
    Netherlands

Recent Profile Visitors

760 profile views
  1. @Sammo Why do you think it is protected after renaming?
  2. As soon as possible may mean as soon as possible for ESET, but certainly not for EIS. So now ESET knows what to do: Make as soon as possible also mean as soon as possible for EIS by removing the unwanted thresholds (23 hours for daily tasks and 6 days and 23 hours for weekly tasks) from the scheduler. I'm looking forward to version 12.2...
  3. Indeed, I think that this is exactly what ESET intended with the scheduler. So weekly is considered much more important than the configured day and time. It would be nice if our ESET representative would confirm that. So the main thing that is wrong is naming the option "as soon as possible", because that is certainly not what it does.
  4. Support ticket? Why? What is the use of this forum if you don't use it as input for improving your products? Both itman and I gave enough information for any decent software tester to find out what is wrong. Besides, some of the behavior seems very deliberate. (For example the 23 hours or the 6 days and 23 hours.) Personally I think the scheduler does what was intented by the programmers. So probably it is no bug but a misunderstood feature. This forum could be very helpful explaining customers why the product behaves the way it does and what the intentions of the programmers were. Why don't you do that?
  5. Here some more results: If consecutive scheduled daily scans can't run at the scheduled time, then the scan will only be done as soon as possible if the previous scan was at least 23 hours ago. If that is not the case yet, then EIS will wait until it is. If consecutive scheduled weekly scans can't run at the scheduled time, then the scan will only be done as soon as possible if the previous scan was at least 6 days and 23 hours ago. If that is not the case yet, then EIS will wait until it is. In my opinion this is not how it should be! For example: A scan is scheduled to run every Monday at 00:00:00, but it doesn't get the chance to run at that time. The computer isn't booted any earlier than Wednesday 20:00:00, but almost directly after booting the missed scan is executed. The next week again there is no chance to run the scan at the scheduled time, but now the computer is booted on Monday at 08:00:00. I would expect the scan to run then almost directly after booting, because it is scheduled to run every Monday at 00:00:00 and in this case 08:00:00 is as soon as possible, but instead EIS decides to wait until Wednesday 19:00:00, which is 6 days and 23 hours after the previous scan. In other words, if there is never a chance to run the scan at the scheduled time, then it will take many weeks to get the scan running on Monday again, because the time will only be advanced 1 hour a week.
  6. Also in my case this solved the problem. Thanks! It is quite a coincidence though, that both TomFace's computer scan log and mine stopped working in the beginning of April.
  7. Aren't the rules checked from top to bottom until one is applicable?
  8. Isn't all outgoing traffic allowed in automatic mode? Can I simply add a rule or do I have to put it above the predefined rules? The order of the rules is important, isn't it? I do want the app; I just don't want it calling home.
  9. Many years I used the firewall's interactive mode, but now Windows 10 apps keep moving to new folders with every update, that became too much hassle to continue. Therefore I switched to automatic mode. However, I would like to block network traffic of a specific app. Is that possible in automatic mode?
  10. In my case every entry in the log corresponds with one file in C:\ProgramData\ESET\ESET Security\Logs\eScan. So scheduled scans that ran but did not appear in the log, don't have a file in C:\ProgramData\ESET\ESET Security\Logs\eScan.
  11. Same issue. Of course missed scans will never appear in the log file. Scans that run at the wrong time, shall appear though, but since the beginning of April that is no longer the case.
  12. For me the problem appeared a few days earlier. I reported it here.
  13. A few weeks ago I had a similar issue with 12.1.34.0 and I use interactive mode. Since the issue occurred only once, I didn't pay much attention to it, but this is what I remember: I was editing a firewall rule and at that moment another program without firewall rule tried to access the internet. The dialog popped up to ask if I wanted to create a rule and I tried to do that, but it could not be saved. After that all firewall rules I tried to edit, could not be saved either. After a reboot everything was back to normal.
  14. @Marcos Why do you want EIS to have an inconsistent user interface? A user without administrator rights can edit a scheduled scan if he knows the administrator password, but when such a scheduled scan is running, then that same user can't interrupt it. That is very inconsistent. It doesn't make sense. Nowadays most administrators use an unpriviledged account for normal work and make use of UAC to do things that require administrator rights. Please support that, ESET.
  15. Indeed! What is the use of adding features to a product when these don't work? Customers remember failures better than successes. Therefore, either get rid of features that don't work or fix them.
×
×
  • Create New...