avielc

@Peter Randziak - Couldn't find which you were talking about (RootKit Detection didn't sound right) So I pasted everything from my local client. (EEA 6.5.2107.1) Let me know if you need anything else, or what's next.

Following this topic.

@MikeD, @Peter Randziak, @TomasP Hi All, For some reason, even after a clean install, I still get that message on startup, and the message doesn't disappear from the Windows maintenance window on 1703: attaching screenshot Any advice on the matter? Thanks guys.

That is fresh Unfortunately, it's not a working day for me, so only Sunday it'll be in affect (which means more time for it sit well in the repo, and catch some clients' feedback Thanks for the update!

Thanks Peter, This is a little off the Wednesday schedule, but understandable. I assume I'll be seeing it next week and be able to test deployments + start to fully deploy organization-wide.

Thank you @foneil - looking forward to see it on eset repo.

Thanks Richard, these are great news. Looking forward to install them once they hit the repo.

Thanks for the Update Michal, I'll keep an eye for it on the ERA repo, I prefer to test the deployment directly from the repo as it will be the only procedure I'd like to have in work, so even if the version is a fix to the issue, I'd like to see it work through the usual procedure of installing via ERA Console. Thanks again.

Hi @MichalJ Any update on the release? I'd like to know how soon I can test\deploy it in my organization to fix this issue. Thanks

Hi @Mike I have some issues with ESET on mac in the past, but lately it's been a bliss on 6.4.246 I suggest checking some configuration\policy in the web console, some of the issues can be resolved due to proper policy corrections (e.g. disable web control, add to the list of exclude application: all sorts of applications like firefox,chrome,etc) I would be happy to share my policy with ya (at least what's generic and allowed to be shared )

I can only suggest to work with the latest as it took away most of the problems (I don't hear anyone complain anymore, so it might be that, or might be the policy that stops everyone from closing their EEA) :->

Joining rkok on that. It's Wednesday already, and I haven't heard of an update\hotfix on the matter. Thank you.

Thanks for the comment Marcos, However I don't think, business-wise, Microsoft would do such a step as to block all AV software from being able to work together with Defender, or alternatively, require users to disable defender via group policy as a solution. From my perspective it'll have to be a more fluent solution, either it can co-exist OR when the system detects a verified source of AV software it'll disable the built in AV. Tell me what you think about it. I've never seen or heard about Microsoft's announcements before, but i'll keep an eye open for that now. Thanks to your info (if you could also give me the name of the presentation they usually display, that would be great Thanks again for all your help.

Thanks, Please correct a minor sentence there - (My personal opinion) I do not believe asking clients to disable Windows Defender is a smart or good recommendation. I would prefer waiting for a hotfix that will be released, this issue doesn't seem to disable ESET from running, just disables the ability of the gui to load with windows startup.

Thank you very much Peter, Really appreciate the gesture, the offer. This would be exceptionally helpful in the worst case scenario the hotfix wouldn't correct this issue. Aside of that, I'm afraid I wouldn't know why egui.exe doesn't automatically start on itself. I can see ekrn.exe running after system reboot, but not the egui. It does however loads with no issue if i just pick EEAV from the start menu-eset. What I don't understand is that "update your Antivirus" alert I receive on the security and maintenance.. really puzzle me, and why it doesn't disappear once i "trust" ESET's app. Anyways. We will be wiser and more set on a solution after trying the hotfix. Looking forward, and will be in touch to let you know whether it worked or not. (hopefully not for latter) Thanks again, both you and Marcos.

Thanks Peter, I'll continue the chat on the other thread. But I will mention here That these are great news, Glad to know there is an ETA, and looking forward to receive it.

Thanks for that Marcos, I hope it'll be this way. I'll let you know if I still find users closing the AV

Ah, Thanks for clarifying. Does that include disabling their ability to force quitting ESET Endpoint AV through activity monitor on Mac?

Don't Think I follow what you say here. I don't define users in the ESET console or anywhere. They do however have administrator privileges on their Mac so they use it as they see fit.

Hi everyone, I'm having a small issue with some users in our company who decide on their own to close the ESET Endpoint Antivirus themselves and not turn it back on. I'm looking for a solution to make either the Agent or the app EEA itself be able to either avoid it or restart itself within a certain period of time. I think on Windows\PC it's impossible to turn it off due to permission authority. BUT Mac is a different story. user can force quit the app from activity monitor and that's it. I will need to reinstall the app remotely (that's the method I only had until now) By policy I can right now disable the icons completely so they don't know its there, but I would prefer knowingly there is AV available. both for me and for them. I was hoping for some solution via Policy on ERA Web Console, If anyone can point me at the right direction. Thanks.

*update* I've tried to look it up as well. Looks like that under "security and maintenance" on windows, under security section there is a request to "update your antivirus" and You need to verify the publisher - aka eset. When trying to confirm it. there is a quick popup of a command prompt box that tries to run "ecmd.exe" but it's too quick to notice what it is trying to run. can you provide me with some way to debug it? perhaps I can provide some helpful info in that direction?

@Peter Randziak - I've been messing for 2 days with the installations of new computers all due to that issue. and i've been breaking my head trying to figure it out. Currently it looks like the "egui" doesn't run on computer restarts. This is a MAJOR issue for us, I'm sure it'll be a bigger issue when more clients will notice it. Worth double checking with the Dev Team. ( provided more info on the other thread) All related to clean install + web console agent and then AV installation to the latest. Please do look it up, as it is a serious matter. @Marcos - If its just a matter of realtime protection I can look it up. Though I would prefer making sure it can be enabled automatically in case ESET isn't present on the machine. And I need to put more weight on this line "This didn't happen on previous updates of Windows. Thus disabling WD was never a recommendation in the first place, and shouldn't become one. Either an application works natively with the platform, or it doesn't. If things have changed due to latest update they need to be addressed or Terms of Agreement needs to be updated." Understand my point? (I really do believe when something breaks, instead of asking to disable an existing feature of another system, especially when you don't know how it'll affect who-knows how many computers. Looking forward to hear back from you. Thanks guys for being so supportive and responsive.

I was referring to the hotfix @Marcos, is there an ETA for that? I would look that option up. but I prefer not shut down such option to computer that might not be protected\BYOD

@jimwillsher Beta doesn't help in production environment, I can't put such product on employees computer and "hope" there won't be any bugs. @Marcos - is there an estimate please, I don't need to be precise on timing, but telling me: a week from now\month from now, is also good just to be able and report it onward in the organization. Thank you for noticing and working on a fix. <- this goes without saying. But I still think it's important to say it out loud.

Hi @Peter Randziak I'll have to bump this topic. Upon upgrading an old WIndows 10 Pro computer from 1511 to 1703 or 1607 (WIth only ESET remote admin agent installed on version 6.3.XXX upgrading the agent required uninstalling it and reinstalling it from the web console. installing ESET Endpoint AV at the latest version (6.5.2094) caused the windows to freeze for long period. when it was finished the following issues occured: 1. ESET wasn't reported in the add remove programs. 2. didn't work automatically and was reported by windows if i "trust this application\vendor" Which everytime I confirmed, the message remained and didn't get dismissed. 3 After trying a full fresh install of windows 10 (something didn't go well with reinstalling no matter how many I tried.) I see ESET on add remove programs, but that allow publisher keeps popping + the tray icon doesn't appear. *update* Looks like there is such issue at hand already and a hotfix is being at work Linking second thread relevant and updated more than this one: