There's a contradiction in your statement. First you say that you cannot run egui.exe but at the same time you see it among running processes but cannot kill it. Due to self-defense, once it's running it cannot be killed which is expected. However, starting it via the Start menu should always work, even if no icon is display in the tray menu.
I understand what you are getting at. The problem exists that the GUI for eset will not load. when i do run the program (and don't force a shutdown of my user) it always gives me a "blue screen of death". The latest one gave me a file association at least ... edevmon.sys (one of the driver files)
I also understand what you mean by its own self defence mechanism. As a point, if I use the start menu to load up egui.exe once I access that program i can no longer access anything on the start menu. Nothing is able to be selected or scrolled through.
Often times I have to force a log off (ctrl+alt+del) and if I don't do that I get blue screened.