When Memory Protection or Script Control is enabled on some systems, it can sometimes cause a conflict with other applications running on the device(s). This conflict is usually due to Advanced Threat Prevention injecting into certain processes that are being called by other applications on the device. Depending on the environment and the application, this can sometimes be resolved by adding in specific process exclusions to the device policy. However, if exclusions are not effective, it is recommended to disable Memory Protection and Script Control to restore normal system functionality.

Note: Memory Protection and Script Control use the same core functionality. If you are disabling features while troubleshooting, make sure both Memory Protection and Script Control are disabled.

The software applications below have been known to cause conflict when Memory Protection or Script Control is enabled. The associated CHP tickets indicate that the issues are currently being investigated by the Advanced Threat Prevention team. As the issues are addressed and fixed in future releases, Advanced Threat Prevention team will notify all users via release notes.

Possible workaround: Uninstall the Citrix Offline Plugin (The file we've seen causing conflicts is RADEAPHOOK64.dll usually located in C:\Program Files (x86)\Citrix\System32) . Second alternative is to rename RADEAPHOOK64.dll once you are in the system

VMware ThinApp

Possible workaround: exclude the path location for VMware ThinApp as well as \windows\SysWOW64\rundll32.exe