Report Windows Memory Integrity in Malware and Computer Security Posted December 26, 2020 On 6/3/2020 at 8:13 AM, GT500 said: It's been a long time, however I think there's a possibility of the core isolation feature causing crashes in Emsisoft Anti-Malware. I know it used to cause BSoD's, however from what I am seeing that appears to have been fixed at some point, and about a year ago QA confirmed EAM could run with the option enabled. I have just enabled Memory Integrity on both of my home PCs, and can confirm that EAM now works well with this feature enabled. Please keep it this way. 😉 Compatibility with this feature has become a basic necessity anyway, as brand-new PCs from big hardware manufacturers tend to come with this feature enabled by default when Windows comes pre-installed. Back in 2018, when I first tried enabling Memory Integrity, EAM was indeed incompatible and caused a big fat BSoD on each reboot after enabling the feature (i.e. Windows was rendered unbootable). This is no longer the case. Thanks for making EAM compatible. 👍 PS: For those who are confused right now: "Memory Integrity" is a subset of the "Core Isolation" feature in recent Win 10 versions. While "Core Isolation" is automatically enabled by default on PCs that are at least fairly recent, "Memory Integrity" has to be manually switched on. Unless, of course, you buy a brand new PC from a big manufacturer that comes with Windows 10 pre-installed. These PCs must have this feature switched on by default because Microsoft requires this for some logo/certification stuff.