Jump to content

User

Members
  • Posts

    228
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by User

  1. Users of Kaspersky had the same problem with these domains and they provided a solution: add the domain names (archive.today / archive.is / ...) in the "Encryted Connections Examination" as "Trusted Addresses" See last posting in this German forum: https://forum.kaspersky.com/topic/probleme-mit-archiveis-oder-archiveph-35965/ So is this not possible in EIS?
  2. Excluding the IP address is not trivial in this case, because the sites use a lot of different IP addresses and once you enter for example archive.today that IP address is forwarded to another IP address. As linked in posting 3: So is it possible to exclude the domain names instead of IP-addresses?
  3. For several weeks now I cannot use the websites archive.today archive.fo archive.is archive.li archive.md archive.ph archive.vn with ESET Internet Security installed. Regardless if I use Firefox, Chrome or Edge on Windows 11, Windows 10 and also Windows 7. The sites just don't load. The sites are fully working if I completely uninstall ESET Internet security. A temporary deactivation of the firewall and/or virus protection in ESET has no effect. What is the solution to this problem?
  4. German version 13.0.22.0 installed: - With pre-release updates enabled: No program update is found - With regular updates enabled: 13.0.24.0 is found
  5. That setting was dectivated by the update to version 12.2.23.0 on my PC and I had to reenable it under Tools -> Notifications.
  6. Update to version 12.2.23.0 is now offered to pre-release customers.
  7. OK, with signature update 19319, I installed Firefox 66.0.5 again, and now it seems to be clean.
  8. After downloading Firefox 65.0.5 German version (windows 64 bit) from https://www.mozilla.org/en-US/firefox/all/ and installing it, Eset Internet Security 12.1.34.0 detects the following trojan: Is this a real threat or false positive?
  9. Internet Security Version 12.0.27.0 is offered as Online-Update since October 16th (German Version and Pre-Release updates).
  10. The problem described in the previous posting from @BrianE is a bug that exists (at least for some users) since version 9. I posted about this problem more than 2 years ago here in this forum Version 9 and 10: scheduler - log maintenance and until today nothing has changed for me.
  11. I tried it again today and it seems that it is working now.
  12. Will this detection now be fixed by ESET?
  13. It is still detected. The simple download of Adsbypasser is no problem. The problem is using Adsbypasser with Tampermonkey in Firefox. Steps to reproduce: Install Tampermonkey in recent Firefox: https://addons.mozilla.org/de/firefox/addon/tampermonkey/ Then install Adsbypasser in Tampermonkey: https://adsbypasser.github.io/ After that you get constant detections of this script when surfing different websites.
  14. This problem still isn't fixed by ESET after more than 2 months. The author of Adsbypasser posted in the github forum that he won't fix this problem in the script, because it is a false positive from ESET: https://github.com/adsbypasser/adsbypasser/issues/1747
  15. After having contacted German customer service and having received 3 answers that were't helpful at all and didn't answer my questions, I will give up and let it as it is. My god, is it so complicated to cancel one licence and extend the other accordingly? It seems that customer service has detoriated massively over the past years.
  16. I switched from pre-release updates to regular updates and there the version is shown. So it is a problem that started with a pre-release update, probably the language module. Lokalisierungsunterstützung 1630 in regular updates and 1633 in pre-release updates.
  17. This seems to be absolutely unlogical to me with the new license manager, because the license manager gives you the clear impression that you can extend your current license with a new code. I have now also written to ESET support via the web formular and requested that the current license is extended for one year after 31.10.2017.
  18. I have now registered my new multi device licence code via the new licence manager and it has went wrong. It activated as separate licence from 05.10.2017 to 05.10.2018, but it should have activated from 01.11.2017 to 31.10.2018 after my current license has expired. Please can someone from ESET look into it and correct this.
  19. Was this also intentionally removed from the log events and the popup in the right bottom corner when the signature was updated or is this a bug? Even if it was intentionally removed it is grammatically incorrect now.
  20. The version number is now no longer shown in the log editor and also no longer in the popup in the right bottom corner when the signature was updated. Maybe this has to do with the update of the German language module to version 1633.
×
×
  • Create New...