Jump to content

Malaque

Members
  • Posts

    27
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Malaque

  1.  

     

    [Malaque]   Disabling Self-Defense... problemas gone. Thanks

     

    You shouldn't do this! Instead try it with a new HIPS rule, manually entered, see the screenshots (#4: you select 'winlogon.exe', of course). This way the 'winlogon.exe' crash (?) should go away. (In Win7 my HIPS log is full of the same entries as you have, but there's no crashing because of that. And there's no HIPS rule for 'winlogon.exe'. On the other hand I never log out and choose another user login: starting PC, restricted user login, PC shutdown, that's all...)

     

    The pictured new HIPS rule should be 100% safe anyway, and don't forget to reenable ESET Self Defense! (But I doubt, that indeed ESET V9 in combination with Win10 has to be blamed for the described crash.)

     

    Try it and report back. Thanks.

     

    HTH

     

     

    Thanks for your reply. Really i still create a rule, similar as yours, but problem back again. Even i delete one of the suspitious users accounts and create it again, but it not solves the issue. I'm not a patient man (i'm very busy), so finally i've uninstalled Nod32 in my desktop PC, and installed this license in my laptop (single user) and not problems. In my desktop PC i've installed KIS 2016 and it's running fine. Thanks again for your support.

  2. Randomly, not always, when i log out of an user session, Windows 10 crashes with this message:

    hxxp://i.imgur.com/RpmXrJQ.jpg

    In log HIPS, i've seen this event many times:

    35]17/02/2016 15:41:03

    35]C:\Windows\System32\svchost.exe

    35]Obtener acceso a otra aplicación

    35]C:\Windows\System32\winlogon.exe

    35]acceso parcial bloqueado

    35]Autodefensa: No permitir la modificación de procesos del sistema

    35]Terminar/suspender otra aplicación

    35]Now i set HIPS in Learning Mode and see if the crash back again. Maybe disabling Self-defense or creating a HIPs rule could help...

  3.   Hello. I'm still having some issues with Nod32, especially with logout session in user accounts of Windows 10

     

    https://forum.eset.com/topic/7345-is-eset-crashing-my-windows-10/

     

    I've enabled HIPS register and i've seen that the HIPS is blocking Winlogon process (selfdefense). I wonder how could I create a Rule exception for unblock Winlogon in HIPS module. 

     

     Thanks

  4.  Hello. I've done a fresh W10 installation, create four local accounts (1 administrator, 3 standard), installed lastest ESET Smart Security 9 version, and i have a problem switching between users. I copy/paste from another link, because it's exactly my issue and my english is not good:

     

    hxxp://answers.microsoft.com/en-us/windows/forum/windows_10-performance/interactive-sign-in-process-initialisation-has/613c2111-58d6-4eac-9c7f-ace729f70979

     

      " (...)when logging out of one account occasionally, but not always, , I get a black screen with the message:

     

    "Interactive Sign-In process initialisation has failed. Please Check the event log for details" with an OK button

     

    The mouse is locked out and pressing Enter does nothing, I used to have to reboot the computer but I found that pressing ALT+TAB switched focus to the Dialog Box and then pressing enter dismisses the message, and then the windows 10 sign in screen appears where I can enter my pin to log on etc. all fine. (...) When I checked the event log the error every time is:

    "The Windows log-on process has unexpectedly terminated.

    Source: Winlogon

    Event ID: 4005

    Level: Error"

     
    This is the black screen:
     
     
    I thought it was a Windows 10 problem, but when i uninstalled ESET, problem is gone! I've left Windows Defender a few days as the only antivirus in my system and all runs fine. After, i've installed Emsisoft Antimalware and no problems. Yesterday, i uninstalled Emsisoft and installed again ESET Smart Security 9 (settings by default, HIPS Smart Mode), and problem is back. 
     
    Any suggestion? 
     
    Thanks in advance
  5. https://www.wilderssecurity.com/threads/emsisoft-anti-malware-emsisoft-internet-security-10-available.376071/#post-2489771

     

    The Emsisoft method seems good. I reckon it's better and safer to wait a couple of minutes to make sure it works for all users, than the product tries to update immediately which may result in a failed update for some, and wait another 59min or so for the next automatic update check. 

    (Unless the user perform a manual update right after the failed update.)

    Though that is at boot, not sure how they do it at "wake from sleep" but I guess it's similar.

     

     I absolutely agree. The solution is so simple.... Maybe 15-20 seconds would be enough.

  6. I really can't believe nothing has been done about this. I have Windows 8.1 on desktop with SSD, and my laptop hdd, Eset fails with Fastboot enabled almost everytime.

    Desktop starts in 4 seconds but the lappy doesn't in fact the wifi signal comes on full strength before the Eset logo and it database update failed ! mark.

    I tried again with the latest build that doesn't seem any different to the previous.

    I have over a year subs left and have used Defender without issue or infection since Windows 8 was launched

    Which annoys me a little.

     

    Well, i've found a partial solution (under testing)

     

    - Create an update schedule task, named Logon Update

    - Put that event trigger task should be "User logon" with interval 1 hour

    - Next step, "Run the task as soon as possible"

     

    It's better if you close session before your computer sleeps.

     

    Also i've modified some parameters from task "Regular automatic update" as time (28 min. instead 1 hour), and if the task did not run "Run task as soon as possible"   

  7.  

     

     I suggest to include a new schedule task that update inmediately virusdatabase if there is some error or adding some delay to update process. 

     

    These have been implemented a long time ago. If establishing a connection takes too long, ekrn cannot wait forever. Of course, we'd like to make some improvements in this regard in future versions.

     

     

    perhaps you could make ekrn test every couple of minutes if connection to a specified address is feasible and then start a new check for signature update if it could successfully connect to that address.

    that way it won't have to wait for another 60 minutes.

     

     

      I agree, It seems a nice idea.

  8.  

     I suggest to include a new schedule task that update inmediately virusdatabase if there is some error or adding some delay to update process. 

     

    These have been implemented a long time ago. If establishing a connection takes too long, ekrn cannot wait forever. Of course, we'd like to make some improvements in this regard in future versions.

     

     

     

    Thanks. I don't thinks that establishing my connection takes too long. In fact, i never had problems with Emsisoft or Kaspersky... 

  9. hxxp://www.wilderssecurity.com/threads/updating-failed-when-pc-is-sleeping.336958/ Curiously, i've found a post of mine, three years ago (ESET 5) with the same problem....

     

     I suggest to include a new schedule task that update inmediately virusdatabase if there is some error or adding some delay to update process. 

     

     Thanks (i hope that i haven't to wait 3 years more  :D )

×
×
  • Create New...