- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
Why is there no block message from Idira EPM when a .bat script is blocked?
Idira Endpoint Privilege Manager (EPM) can apply block actions based on two types of events: FILEOPEN and PROCSTART. However, customers may notice that when a .bat script is blocked, no block dialog appears. This behavior is expected and stems from how the operating system interacts with EPM and how EPM is designed to handle these events.
EPM can enforce block on both FILEOPEN and PROCSTART events. However, the logic for displaying block dialogs differs between the two.
Whether a block is applied—and whether a dialog is shown—depends on how EPM policies are configured and prioritized. Some policies may block silently without user notification.
FILEOPEN actions when attempting to launch a script.FILEOPEN attempts is unpredictable and can be excessive.FILEOPEN events during a single user action (e.g., double-clicking a .bat file).FILEOPEN events.
The absence of a block dialog when a .bat script is blocked is a result of EPM’s design to balance security enforcement with user experience.