clipper87

If I restart egui.exe then the icon will show. Sometimes it will disappear after some time but it is difficult to say when. When rebooting most of the time it does not show up at all. It gives me kind of unprotected feeling; I want it to be in my systray all the time without exception. My trial is expiring in 4 days; I'll probably have to revert to Bitdefender :-( unless I can get an extended trial key to sort this issue out.

egui.exe is running but the icon does not show. I don't understand why Eset say in their KB article that on 64 bit systems it needs to run from the wow6432node if it does not make a difference ?

After a reboot the icon is missing every time. It turns out that egui.exe runs from the wrong registry key. The proposed solution in hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN532 does not work; registry editor refuses to create a string value "egui" because obviously it already exists (and cannot be deleted/renamed) in HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/CurrentVersion/Run whereas it should be located in HKEY_LOCAL_MACHINE/SOFTWARE/Wow6432Node/Microsoft/Windows/CurrentVersion/Run Any suggestions on how to create that registry entry ?

This has been an ongoing issue for years now & ESET does not seem to bother about it. I switched to BitDefender but I'd like to come back & ready to pay (because I like the Eset firewall better) if they fix the problem. I installed a trial about 10 days ago; worked ok but indeed reboots cause the icon to appear yes or no

Hmmm... Installing works perfectly well but the activation fails; you only get 1 option (username & pw) instead of 3 and activation using a username & pw fails (error 0008) Here's how to replicate the issue: create a folder "ESET" in c:\Program files & c:\Programdata execute "mklink /J ESET d:\pf\eset" in c:\program files execute "mklink /J ESET d:\pd\eset" in c:\programdata run the live installer see how activation only offers 1 option (username & pw) & try to activate: it will fail Using the offline installer all works well and I do not need junctions Thx

I tested with both a junction (MKLINK /J) & symbolic link (MKLINK /D) both resulting in the same problem I will test with the offline installer; I was not aware of it. Thx

I'm trying to install ESS into redirected folders on a different drive; the install works fine but I cannot activate the product. I created a junction for "c:\program files\ESET" to "D:\pf\ESET" & a junction for "c:\programdata\ESET" to "D:\pd\ESET". it appears that the junction of the ESET folder in Program files is causing the issue. I also tried with symbolic links to no avail. How could this be solved ? Thx