I am encountering similar issues of conflict between Windows Defender and ESET lately, since a recent Windows update which I believe made Defender more intrusive/difficult to disable permanently...
https://www.techradar.com/news/microsoft-explains-why-it-wont-let-you-disable-this-annoying-windows-10-feature-any-more
Windows Security Center often showing Defender is enabled and ESET is disabled, even though ESET is properly active.
VanBuran, you should run "msconfig" and see if Defender is launching at startup, then uncheck it. It seems to be the root of the problem.
It seemed to have fixed the issues for me for the last few days, but today, it happened again even though Defender was disabled from startup. It's becoming very annoying, I hope the ESET will look into this.