andrewek

Hello! No mistakes? This makes me happy! I only have MBAM as a scanner on demand! No mutual exclusions are configured. I can - 1) add to exclusions in EAM, 2) remove this scanner completely! I completely removed MBAM, with a lot of traces in the registry, service and drivers! It wasn't easy ... However, unfortunately, the problem with the integration persists ... Here are the laptop logs without MBAM. Addition.txt FRST.txt

p.s. And here are the logs from a desktop computer, on which the problem arises, but much less often, once a week. Addition.txt FRST.txt

Hello! Thank you very much for your willingness to help! Here are the logs (laptop on which the integration problem occurs every day) FRST.txt Addition.txt

Hello! I don't think the integration issue is related to CPU power. I have similar systems, Intel processors. Desktop computer - 1 screen. There is practically no problem on it. Laptop (screen 2) - here's the problem on it - every day ... Indeed, manipulations with disabling the integration, rebooting and re-enabling the integration do not help much ... I also want to say that when you enable extended logging in EAM, the problem disappears, EAM is perfectly integrated into the Windows Security Center every time the computer starts! Disabling logging leads to another problem with integration! That's bad luck, it's impossible to get logs with a problem ...😌

Hello! Unfortunately, the problem persists for the fourth month!😌 Of course, this is not critical, but still! I am writing here so that developers remember the problem of integration into the Windows Security Center. Can't it be solved?🙄 After all, there was no such problem until June 2020!

And this is what the Security Service looks like on another computer. It can be seen that EAM is not integrated, Windows Defender is disabled, and a message about the management of parameters by my organization (that is, by me) At the same time, the changes in the Group Policy Editor are completely identical!

Hello! To be honest, I haven't tried this reverse. I did not turn Windows Defender back on. Do you think this should be done? p.s. This is how everything looks in the editor of group policies and on one computer, where EAM is adequately integrated into the Windows Security Center. The screens are in Russian, but I suppose everything is clear😌

Hello all! I also join this topic! Unfortunately, the new, August version did not solve the problem with the integration ... What is curious is that I have 2 computers from Hewlett Packard. Both - Windows 10 Pro (1909) x64. On both, Windows Defender is disabled through the Group Policy Editor. So - on one computer - the integration into the Windows Security Center is effective, but on the other - EAM is not integrated into any! Windows message - action required! That the parameters are managed by my organization (well, that's understandable why). I followed the recommendations with disabling the integration, rebooting, enabling, restarting the computer again! No effect! In reality, EAM is working absolutely fine, all services and components are running. But Windows stubbornly DOES NOT SEE the antivirus! These messages from the Security Center every time you start your computer are just annoying! Of course, you can ignore this!😉 However - probably the developers need to do something? And why is there such a different reaction of the Windows Security Center on two completely identical systems with all Windows updates?

Hello! If you are interested in how I changed the settings of AdGuard, then here is the recommendation for technical support. That's exactly what I did!

Hello! This is without any cynicism or grin, Jeremy! I am really pleased that the developers heard the users and fixed the problems I described here earlier (with the crash of the program and non-saving of the interface) And what else? It's enough! I have no other problems with the work of EAM😌

Hello! Obviously, a small one has been fixed - but the problem with maintaining the window size of the program (interface). In any case, I observed during the day - the program does not change the window size after restarting the computer! Well, bravo, Emsisoft!👍

Hello! It seems that the new version (2020.7.0.) Fixed the problem with notifications! In any case, I turned on notifications and everything is in order - there is no problem with the a2guard.exe crash!

Hello! I apologize - I suppose all this applies to real-time MBAM? I have MBAM in my system, but only as a scanner on demand. However - the system has a service and driver from this program. I have not configured any mutual exclusions. I hope this is not necessary?

Hello! Thank! I want to add - this small problem with the interface - only on a laptop. On a desktop computer there is no such problem! Although the operating system, its settings, the list of installed programs are completely identical. Of course, I understand that it all depends on the specific configuration of the system — although they are as close as possible to me.

Hello! Thank you, I really hope for a fix! Another small problem, it appeared at the beginning of the month, when EAM was updated to version 2006 and a2guard.exe crashed: the program window sizes I have selected are not saved! At the next start of the computer - the window size (UI) is reset to "default". This can be seen on the screenshots. Of course, this is completely uncritical - but still😏 This was not the case with version 2005...