Jump to content

stackz

ESET Insiders
  • Posts

    408
  • Joined

  • Last visited

  • Days Won

    19

Everything posted by stackz

  1. Open the GUI and press Setup -> Computer protection -> Gamer mode
  2. I first used Nod32 back in about 2003. I remember clearly AMON, DMON and perhaps YEAHMON.
  3. I suspect that the website was temporarily having a problem and redirecting to an error page, that for some reason your browser was trying to open/save as an attachment. BTW if you viewed that badcountry page, you'd see it was plain text and said "gangnam style!"
  4. @itman I can confirm all your findings. Tested on Edge-Chromium, Firefox and Internet Explorer.
  5. From help and support select 'Details for Technical Support' then toggle Advanced logging.
  6. It should work if you change your specific files path to C:\Users\BALTAGY\Desktop\*.*
  7. I solved it. The EsetOPPFirefoxProfile in "C:\ProgramData\ESET\ESET Security\OPP" was corrupt and had to be rebuilt.
  8. Detection names are no longer a part of the information about engine updates. ref prior discussion: https://forum.eset.com/topic/20969-virusradar-signature-database-unclickable/?_fromLogin=1
  9. Win7 x64 EIS 13.0.22.0 Firefox 70.0/70.0.1 Banking modules tested 1165/1166 When trying to open a secured browser, Firefox gets stuck on the Opening the secured browser page and after a while the Close Firefox message appears. Pressing the Close Firefox button has no effect. Launching B&PP from a shortcut results in the Close Firefox message.
  10. FYI, the last TCPView pic shows explorer.exe connected to Microsoft - 40.67.254.36
  11. Yes, Win 7x64 Sorry, I thought the module would be the same as released in regular pre-release update.
  12. B&PP Module 1161 Firefox 69.0.3 displays "The secured browser could not be started" with error code 0x847694e3 IE11 just gets stuck on the "Opening the secured browser" page note: I'm on the beta so I can't revert to regular release modules.
  13. It seems that your issues stem from you having two anti-virus installed, AVG and Eset. You need to uninstall one or the other in order to avoid conflict.
  14. That particular rule is checked in my installation. Seeing as it's a built in rule, I'd expect it to be checked by default. Edit: I just reset all rules to default and that rule is definitely checked.
  15. There's a discussion at CodeProject re 7g6njejx.com linking the popup to ExpressVPN. refer to: https://www.codeproject.com/Messages/5666747/Re-Hacked-by-Amazon.aspx
  16. I was just pointing out that a later version from your clean link has a similar number of coin miner detections including Kaspersky.
  17. Because as Marcos post indicates, it is only presently available in the early access download section https://forum.eset.com/files/category/3-early-access/ as it is has not been officially released.
  18. Here's the VT report for Setup_TheFastestMouseClicker_2_1_5_1.exe from sourceforge: https://www.virustotal.com/gui/file/cbfdd4037e9f01eb0219c52e36a1e1f4c5988a91ee32df9b7951da25e7aa9218/detection Sourceforge download from https://sourceforge.net/projects/fast-mouse-clicker-pro/files/ Seems like a false positive to me.
  19. It's related to AMD Catalyst. There's a prior discussion at https://forum.eset.com/topic/19961-eset-blocking-systemrequirementslab-in-amd-catalyst/
  20. From looking at the picture in the initial post, EIS v12.2.23.0 should not have the directory branch "C:\ProgramData\ESET\ESET Smart Security". The correct branch is "C:\ProgramData\ESET\ESET Security". It seems you may have leftovers from a much older installation.
  21. You'll now find it in Advanced setup under Tools -> Notifications -> BASIC -> Display notification about successful update
  22. I had the same problem as you some time back. A complete uninstall and install from scratch resolved it.
  23. I've finally got everything up and running. There was an old epfwlwf driver package in the driverstore's file repository. Once this package was removed, EIS installed successfully.
  24. I tried that and I'm back where I started with no firewall. Personal firewall: An error occurred during installation of the epfwlwf driver.
  25. It would seem from my findings that it is Ekrn that initiates the loading of epfwlwf.sys and not the Service Control Manager. If I remove the directory tree that I created - "C:\Program Files\ESET\ESET Smart Security\Drivers\epfwlwf\EpfwLwf.sys" then epfwlwf is never loaded.
×
×
  • Create New...