Jump to content

Gui keep opening in boot


Recommended Posts

Eset Nod 32 antivirus gui keeping opening on boot, i managed to reproduce the issue on 3 different pc.

 

How to re-reproduce it open the gui and shutdown or restart the pc with the gui open and from now on the gui will open it self of boot after you get that issue it's seem to be no way to resolved it.

Edited by Razza
Link to post
Share on other sites
  • Administrators

I was unable to reproduce it. Please provide a Process monitor boot log as well as ELC logs as per the instructions linked in my signature.

Link to post
Share on other sites

I will post the  ELC  in the next 24 hours as the only system i got Eset on are at home, before i left home i did install NoVirusThanks Process Logger Service to see what was launching Eset gui the only Eset listing in the process logging was

 

Quote

Process: [4656] C:\Program Files\ESET\ESET Security\egui.exe
CommandLine: "C:\Program Files\ESET\ESET Security\egui.exe" /hide
Parent: [1504] C:\Program Files\ESET\ESET Security\ekrn.exe


 

Which is normal as i already known Eset is started via ekrn.exe

Edited by Razza
fixed quote
Link to post
Share on other sites

I did try to do a full reinstall of Eset, it made the issue worse as my pc keep bsod on boot lucky i had a image of disk i could restore.

 

I fixed the issue on my side by writing a little script in autoit set to run on boot to close Eset gui it work's fine i only see the Eset gui for less than a sec now.

Source code

WinWait("ESET NOD32 Antivirus", "", 20)
Sleep(100)
WinClose("ESET NOD32 Antivirus")
Exit 0

  

Link to post
Share on other sites

@simplicissimus  i just read your post, did your issue only happen after a system restore via a image as i only started to get this issue after system restore too i did one on the same day as Eset startred playing up.

Link to post
Share on other sites
4 hours ago, Razza said:

@simplicissimus  i just read your post, did your issue only happen after a system restore via a image as i only started to get this issue after system restore too i did one on the same day as Eset startred playing up.

I suppose that it does not deal with the image or restore.
I still suspect an update because in my case the problem appeared with the update 15517.

This problem only happened with my 32-bit Windows 7 (not with 64-bit).

Link to post
Share on other sites
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...