This is long term problem starting with version 16. Last known working version from my own testing is 15.x. I am not one of those people ditching any piece of my long term used and also fav software for any bugs if it at least seems that the developers care about the issue. However, in this particular case I am starting to believe these exuses are not in place. This might seem like a harmless visual bug but the problems with eset are slowly starting to stack up with non-correctly working firewall especially in interactive mode - asking for the same processes upon each restart e.g. NvidiaContainer, windows system process host etc. Externally provided UI engine is ok but you need not only to investigate but push your provider to FIX the issue. This is not a freeware soft and when you consider it can't handle even some basic functionality now througout multiple versions updates maybe it is time to move on.