4 ms·
[flagged]
by bdcp 4y ago
[flagged]
- boredumb 4y agoFirefox engineers discovered a Windows Defender bug that causes high CPU usage.
- ape4 4y ago"This problem has two sides: Microsoft was doing a lot of useless computations upon each event; and we are generating a lot of events. The combination is explosive. Now that Microsoft has done their part of the job (comment 82), we need to reduce our dependency to VirtualProtect. Bug 1822650 in particular will help with that."
- nier 4y agoFirefox engineers discovered a bug in Windows Defender that causes high CPU usage.
- dakial1 4y ago[flagged]
- nvrspyx 4y agoIt was also fixed with a definition update in Windows Defender some time last month, so you probably have the update since these happen in the background and don't require any restart. You can check by going to: C:\ProgramData\Microsoft\Windows Defender\Definition Updates\{BUNCH-OF-NUMBERS} Right click `mpengine.dll`, choose Properties, click Details tab, and check to see if Product Version is >= 1.1.20200.3. Mine is 1.1.20200.4 and was updated in mid/late March. If the version is less than 1.1.20200.3, you can manually trigger a definitions update in Windows Defender under Virus & Threat Protection.