Microsoft Defender is causing a series of problems with Windows 10 version 20H2

Microsoft Defender for Endpoint seems to be causing a series of major problems for some client systems running on Windows 10 version 20H2.

A report from Borncity says that their team has been observing the problem for nearly a month and discovered many system problems caused by this default security toolkit.

Here is a list of issues allegedly caused by Defender for Endpoint as noted by Borncity:

Memory usage is very high
Black screen issue after login (two minutes or more delay)
Word 2016 (and later versions) fails to open, or takes a long time to open
Windows Event Viewer takes a long time to display events (both remote as well as local)

Of course, not all client systems running on Windows 10 20H2 version will experience the above problems, but the number of recorded cases tends to increase.

As for the high memory usage issue, the cause can be traced back to a memory leak. The problem doesn't seem to be new, and Microsoft fixed it once before. The company says that the problem started with build 1.363.177.0. However, the problem seems to have returned once again, and it looks like Microsoft's previous solution may only be temporary.

High memory usage caused by Defender's "Antimalware Service Executable" (MsMpEng.exe) process is a fairly common error, and sometimes a temporary solution to reduce memory consumption is to disable Real-time Protection .

Microsoft has not yet confirmed the issues mentioned above, but with more and more reported incidents being recorded, that silence certainly won't last long.

Microsoft Defender is causing a series of problems with Windows 10 version 20H2 Picture 1 Microsoft Defender is causing a series of problems with Windows 10 version 20H2 Picture 1

In related news, Microsoft Defender for Endpoint is also experiencing an issue tagging Google Chrome updates (delivered via Google Update) as suspicious activity and can lead to security risks. Responding to this anomaly, a Microsoft representative confirmed that Microsoft Defender warnings for Chrome update files were mistakenly triggered due to errors in suspicious file screening, not due to actual malicious activity. appearance on the system.