avielc

Members
  • Content count

    133
  • Joined

  • Last visited

  • Days Won

    3

avielc last won the day on June 8

avielc had the most liked content!

About avielc

  • Rank
    N/A

Profile Information

  • Gender
    Male

Recent Profile Visitors

289 profile views
  1. @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.
  2. 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!
  3. 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.
  4. Thank you @foneil - looking forward to see it on eset repo.
  5. Thanks Richard, these are great news. Looking forward to install them once they hit the repo.
  6. 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.
  7. 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
  8. 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 )
  9. 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) :->
  10. Joining rkok on that. It's Wednesday already, and I haven't heard of an update\hotfix on the matter. Thank you.
  11. 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.
  12. 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.
  13. 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.
  14. 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.