If Microsoft Enhanced Mitigation Experience Toolkit v2 (or higher) is installed then it may cause protected applications and our SDK tools (e.g. DinkeyChange) to crash with the BEX exception.

This problem can be solved by removing the Export Address Table Access Filtering (EAF) mitigation and the Export Address Table Access Filtering Plus (EAF+) mitigation from the affected program.

In the case where the protected software is a DLL or Plugin then you need to change the setting for the application that is calling your protected module. For an Access database you will need to change the settings for Access itself.

Note - the Microsoft EMET documentation says of the EAF mitigation: "This mitigation may have compatibility issues with software such as debuggers... or that use anti-debugging techniques." So this incompatibility is not entirely unexpected.

In this Knowledge Base article Microsoft recommend that you do not use EMET to protect software that use anti-debugging techniques (i.e. our runtime protection checking code).