andrewek

Hello! I want to say that I have Windows Core Isolation enabled on two computers for over a year. At the same time, there are no problems with the work of EAM.

Hello! I want to say that today the problem with the integration of the EAM into the Windows Security Center has been completely resolved! Thanks a lot to the developers!

Hello! That is, it is not related to the type of processors, updating versions of Windows? I, not a specialist, do not quite understand about the report to the Security Center, but most importantly, apparently the problem has been resolved. This is very nice, thanks again!

Hello! It seems that the changes in the December version actually solved the integration issue! In any case, within a day and several starts of the computer, the problem is no longer there! Thanks! You can find out what was the reason?

Hi! Thank you for not forgetting about us😌 However, these changes will obviously be implemented in the stable version in December?...

Yes it is! Only we don't understand why ...

On a laptop where there is this problem, the primary version is 1903 with an update to 1909. On a desktop computer, 1909 is preinstalled without subsequent updates to the versions of Windows. On a stationary, this problem is not!

Hello! I can say that I have Windows 10 1909 without upgrading to 2004 and beyond, and the integration problem persists. But only on a laptop. In principle, I have already got used to it, 2-3 times a week, that is, it has become much less frequent than before. But still)

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 comput

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😌