Jump to content

pic14

Members
  • Posts

    21
  • Joined

  • Last visited

Posts posted by pic14

  1. The problem with the two-minute black screen on log on solved, but still sometimes long computer turns off. When a problem occurs with a long 5 minutes shutdown ( screen goes blank but the computer still works for 5 minutes )  and then when I turn on the computer Windows 10 behave like a reboot.

    It looks like a conflict ESET Smart security with Windows 10.
    I'm using Windows 10 PRO 64 Bit

    What could be the reason?

  2. Probably the best solution is to unistall Eset Smart security and wait for the updates HIPS, because it is a tragedy, what does Eset do with the computer.
    Two-minute black screen with the cursor, long turn off PC preceded by a black screen, not always start meniu welcome Eset and slow entire Windows 10. The same problems apply to Eset Smart Security 10 with HIPS 1242B.
    HIPS 1250 did not cause any of the above-mentioned problems. Please do something with this.

  3.  

    Why did you change "HIPS module 1250" to "HIPS module 1247", what was the reason?

     

    Do you actually have Endpoint v6 installed? It should download HIPS module 1252 while HIPS 1247 is currently available for Endpoint v5.

     

    I use ESET Smart Security 9 and the problem returned after returning to the module HIPS 1247. :(

      HIPS module 1250 did not cause any problems in ESET Smart Securty 9.

  4. Hello guys,

     

    the issue should be fixed in HIPS support module: 1250.

    We will release the module gradually, please check if the issue persists after you receive this update. If yes, please let us know.

    In addition to the two-minute black screen with the cursor Eset causing very long off the computer, that is, the screen turns off and the computer for a few minutes turns off.

    The same problems apply to: ESET Smart Security version 9 and 8, as well as ESET Nod32 version 9

    I hope these two problems will be resolved quickly.

    Regards.

  5.  

    Hello All,

     

    I'm wondering if anyone has come across an issue with ESET Endpoint AV. Basically ever since migrating everyone over to Windows 10 Pro version 1511 from Windows 7 we found that upon occasion when a user logged out they received a black screen with a cursor. If you wait a number of minutes the login screen would return. This is a VERY intermittent issue but always seems to occur at the most inconvenient times of switching user. Obviously this is unusual and unwanted behavior. 

     

    attachicon.gifcap2.png

     

    PCs have latest available Windows Updates from August. I uninstalled and updated to the latest available ESET Endpoint 6.4.2014.0. Still problem persisted.

     

    I started to question my image or 3rd party software contained within I even updated the display drivers to the latest available with no luck.

     

    So to rule that out I created a Virtual Machine (using VMware) from a fresh ISO install of Windows 10 Pro version 1511. Windows Update performed. No other 3rd party software installed apart from VMware Tools and latest version of ESET Endpoint installed and rebooted. Funnily enough the problem still persisted.

     

    After reading a post on the forums about a user having issues with HIPS I turned my attention to this. With self-defense disabled I could not replicate the issue. So turned it back on enabled logging of HIPS and checked the logs. I noticed that some aspect of winlogon was being blocked which raised my suspicion...

     

    attachicon.gifCapture.PNG

     

    And thus I created a rule for the following

     

    Rule Settings:

    Rule Name - Allow Winlogon

    Action - Allow

    Operations affecting: Applications - Ticked

    Enabled - Ticked

     

    Source Applications:

    C:\Windows\System32\csrss.exe

    C:\Windows\System32\svchost.exe

     

    Application Operations:

    Terminated/suspends another application - Ticked

    Modify state of another application - Ticked

     

    Specific Applications:

    C:\Windows\System32\winlogon.exe

     

    Since adding this rule I no longer have this issue anymore. Has anyone else experienced an issue like this? Is this a known bug in ESET Endpoint AV? I suspect that due to the intermittent nature of the problem and the fact that most people don't log out too frequently it is understandable it hasn't been picked up yet. I'm concerned that adding this rule may lower security in some way.

     

    Thanks.

     

    I have the same problem with ESET Smart securty 9 and 8 ver. 2 min. Black Screen at start up

    How I can  created this rule in ESET Smart Security 9 ?

×
×
  • Create New...