Jump to content

Page42

Members
  • Posts

    57
  • Joined

  • Last visited

Posts posted by Page42

  1. 1 hour ago, itman said:

    Appears you're going to have to wait for Eset to fix this.

    As posted on wilderssecurity.com, even a fresh install of 14.0.21 is borking the Win Security Center on select Win installations.

    When I tell Action Center to turn on virus protection, I get this dialog.  And when I select "Yes, I trust the publisher...", nothing changes.  I have also selected the second choice, and that fails to fix the AC problem.  I wanted this to be posted in case it helps  ESET in finding a solution. 

     

    Action Center ESET dialog.JPG

  2. Since updating to Version: 14.0.21.0 on one of my 7x64 machines, I am getting the Windows Action Center telling me that ESET Security is turned off (I run ESET NOD32) and despite selecting the option in AC to turn it on and trust the publisher, the status remains the same... ESET Security is turned off. I can choose to turn off messages about virus protection, but would prefer to get ESET to sync with Action Center. I've experienced this before, and usually updating the program, or a second reboot, makes AC recognize. Anyone else?  Help appreciated!

     

     

    Action Center says ESET turned off.JPG

  3. On 7/17/2019 at 4:01 PM, Page42 said:

    Just downloaded the new Cleaner module 1197 pre-release update.  I'll post back with any info.  TY!

    It's scary how well this new Cleaner module has fixed the problem.  I've been opening and closing browser sessions like crazy, trying to get Sandboxie to throw another  "Could not move the sandbox folder out of the way" error message, but all is well.  Sandboxie is deleting sandboxes like it used to.  :)

  4. 18 hours ago, itman said:

    So far, the Sophos suggested Sandboxie mitigation posted previously: https://forum.eset.com/topic/20056-eset-issue-with-sandboxie-persistent-holding-of-registry-keys/?do=findComment&comment=97716 appears to be working as observed through testing here: https://www.wilderssecurity.com/threads/sandboxie-acquired-by-invincea.357312/page-213#post-2840059

    Appears to be no conflicts with Eset by doing this.

    An edit was made to the above-linked post on Wilders ...

    Quote

    Edit: Regrettably, I must report that I did receive the dreaded "Could not move the sandbox folder out of the way" error message once after having blocked ekrn.exe. I've probably closed a couple dozen browser sessions without any issue, but just now the Sandboxie deletion failure did happen, and I had to reboot to delete. I made note of the numbers, in case we begin to look at the size of the space (or number of files or folders) as a potential trigger. 98 files and 44 folders occupying 45 MB of space. :(

    Back to waiting for ESET's release of new Cleaner module 1197 on pre-release update servers next week. :thumb:

     

  5. 8 hours ago, Marcos said:

    Most likely next week we'll release a new Cleaner module 1197 to pre-release update servers which should address this issue. If you want to get the fix among the first, switch to pre-release updates in the advanced update setup. The module will be released for all users a little bit later.

    That sounds awesome, Marcos.  Looking forward to the new Cleaner module.  😊

  6. 12 hours ago, Marcos said:

    It's not possible to prevent automatic upgrade. Please clarify why would want to stay with 10.1.235 and not upgrade to v11 or newer version in several months or years? We provide protection as a service and do not distinguish between program versions any more; v11 is just an internal version number but it doesn't appear anywhere in the product except in information about installed modules and product version.

    I'll be happy to clarify, although I am immediately surprised that someone like yourself should have to ask that question.

    Why do I want to have the ability to disable auto-installation of ANYTHING on my computers?  Simple answer is in case of bad upgrades pushed out by devs that then go on to cause great damage to the user's system.  Could be a minor incompatibility with another security program, or it could be a major flaw that quality control did not catch and hundreds if not thousands of users are left with hosed operating systems.

    Why does Microsoft allow users to decide if they want to download and install monthly updates?  Why do the vast majority of all security programs provide this option to their users?  Because while a large segment of non-technically inclined users are content with auto-installation of new versions, there is also a segment who want to research change logs and peruse various forums to see if other users are reporting problems with new version releases.

    Again, this answer is so obvious, I am surprised that you would ask for clarification, Marcos.  And it is discouraging to learn from you that there is no simple setting that I can employ to disable these forced upgrades.

  7. On 8/19/2017 at 2:57 PM, beethoven said:

    Page42,  just to clarify and as my pc is running the same combo of Win7/64 bit with sandboxie - you no longer think that there is any issue between the two and that the orginal problem was "just" some corruption during the update process?

    Hello beethoven,

    Sorry for the delay in responding, but I just saw your post.

    Yes, there is no longer any issue.  It most definitely was some corruption during the update process, and I was fortunately able to fix the problem via the Setup Wizard's Repair feature in Control Panel Programs section.

    HTH

    Page42

     

  8. I had success using the Setup Wizard's Repair feature in Control Panel Programs section.  Obviously some corruption somewhere in the initial install.

    6 hours ago, pygocentrus said:

    You can find and download nod32 10.0.390.0 with a google search but not from the Eset web site.   It is at your own risk. 

    The 10.1.219.0 upgrade came via the ESET internal program updater.

  9. I have started encountering email and browser problems immediately after doing an ESET NOD32 program update to 10.1.219.0.

    These issues involve another program, Sandboxie, that has been running on my two Windows 7x64 computers for many years.

    Without going into detail about these issues, I will say that on the 7x64 box which I have NOT upgraded to 10.1.219.0, these browser and email problems do not exist.

    I doubt that there is anything that ESET will do to fix compatibility with SBIE (which, by the way, was fine until this latest upgrade), so I would like advice on how to rollback ESET to v10.0.390.0.

    TYVM

     

  10. I'm curious to know why you'd prefer installing ESET NOD32 Antivirus to ESET Smart Security which also includes Botnet protection.

    I figured someone would want to know why.  Simple answer is options.  I want options.

    I may not like the ESS firewall.  It's my understanding that the FW has to be installed, and can then only be temporarily disabled, or maybe set to allow all traffic.

    Not too sure how well that would fly with another FW, if I wished to continue using Comodo FW, for instance.

    There is a good probability that I will install ESS and like the entire suite.  But now I know I have the option of installing only NOD32 and using the ESS activation code.

    Hope that satisfies everyone's curiosity.

  11.  

    Even though MBAM is designed to co-exist with an AV, its always a good idea and recommended to exclude ESET in MBAM, and MBAM in ESET. Or wich ever AV one happen to use with MBAM.

     

    I never recommend adding exclusions unless inevitable. Every exclusion deteriorates overall protection capabilities of a security product as malware authors could take advantage of exclusions and stay running unnoticed in folders excluded from scanning.

     

    If a user wished to exclude ESET in MBAM, can you tell me which ESET files should be excluded?  I have searched the ESET KB but cannot find that info.  TY!

×
×
  • Create New...