Jump to content

FRiC

Members
  • Posts

    83
  • Joined

  • Last visited

Posts posted by FRiC

  1. 24 minutes ago, Hpoonis said:

    If you are still using them then they ARE worth the money to upgrade. Logically, if you are using systems that perform a specific task and that task is a business-critical thing then the driving software should be updated. If it is not possible to do this then the policy that these systems operate from is outdated and needs correcting.

    Yeah, logically that's true, but it's all about the money. Oh, I forgot to mention the single task for the XP computers is to virtualize Win 98. The business programs are running in Win 98 since they don't work correctly in XP. Of course, I can upgrade to newer computers with better OS, and then they'll still be used to run Windows 98.

  2. Does the Endpoint license cover all versions? i.e. can I install 6.5 on XP and 7 on Win7/10?

    This said, I didn't realize that EES 7 isn't supported on XP and I have it installed on quite a few XP machines at work. These are really old computers that are used for a single task, they're over 10 years old and have 1 GB RAM and 80 GB hard drives. Not really worth the money to upgrade.

     

  3. 7 hours ago, itman said:

    Why in the world would you want to prevent Eset from detecting malicious activity on the web site?

    Even if the website actually has malicious content, if a user reports a problem with accessing a site, it's up to me to check it out. The website may very well have legimitimate content and I could probably notify the website owner if I find a problem, or it could be a false positive. I can't just tell the user that it's blocked for her own good when it had been working fine previously. The issue is ESET / Windows crashing and not about what's in the website.

    Right now the issue that affects me was fixed somewhere and my users can access the websites, but I don't know if the underlying issue has been fixed or not. (Probably not if MrNobody96 still has issues.) What if I have another legitimate website that actually needs to be whitelisted in the future, and all ESET does is crash?

  4. 1 hour ago, MrNobody96 said:

    Again; the above is the same for me. Including the settings in the screenshots.  As long as I don't try to allow the site, I can visit the url, it is blocked (with the above explanation), and nothing happens. I had tried allowing the site 3 or 4 times, each resulting in a crash (like described above). I haven't tried again since, since I don't want to cause anymore crashes.

    Just noticed the websites are no longer blocked by default so there's no need to whitelist them and no more issues with crashing. I noticed there are several other similar threads on this issue so I guess something somewhere got fixed.

  5. 1 hour ago, Kieran Barry said:

    Hi Both,

    When you open the URL Address Management > Address List window, is there a category that you can edit called "List of allowed addresses"? 

    What happens if you add the URL to there and remove it from the "List of addresses excluded from checking"?

    Let me know if this helps!

    Adding the URL to List of allowed doesn't work, still can't open the site at all. Only adding to List of address excluded from checking, or turning off Web access protection entirely works. "Works" as in the URL can be opened, but then Windows crashes.

  6. The URL is blocked, going to the site shows "This web page contains potentially dangerous content. Threat: JS/Adware.Agent.AC application. Access to it has been blocked. Your computer is safe."

    Open EES,  go into advanced setup, Web access protection, URL address management, Edit address list, add the URL to list of addresses excluded from checking.

    Open the URL using Chrome causes Chrome and Windows 10 to stop responding. Trying to enter another URL or click on a bookmark just makes Chrome say reading cache ... (lower left corner), but nothing happens, sometimes the tab will crash (aw snap) and sometimes ESET will restart (splash screen). But the only way to recover is to hold down power button to force a shutdown. After rebooting and restarting Chrome complains that ESET should be removed.

    IE and Edge work as expected.

    EES log attached. Thanks!

    P.S. I realize the website should be blocked permanently, but it's a user request, and whitelisting it causes ESET to crash, so it's still a problem for me...

    ees_logs.zip

  7. We just bought EES at work and it's blocking some websites that upper management "needs". However, excluding these websites from checking either causes Windows 10 to freeze if I those URL's are accessed using Chrome (IE seems to work fine) or causes ESET to restart (ESET splash screen appears) This is similar to the problem described in this post. After Windows / Chrome recovers from the crash it warns that ESET should be removed.

    During the trial period we used EEA without the web filtering and everything worked nicely and upper management approved the purchase and now they're not happy. Any thoughts?

×
×
  • Create New...