Why is there no block message from Idira EPM when a .bat script is blocked?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Endpoint Privilege Manager (EPM) Articles
2 min read
L0 Member
No ratings

Question

Why is there no block message from Idira EPM when a .bat script is blocked?

Answer

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.

 

  • The operating system often performs multiple FILEOPEN actions when attempting to launch a script.
  • The number of FILEOPEN attempts is unpredictable and can be excessive.
  • Applications like Windows Explorer may trigger many FILEOPEN events during a single user action (e.g., double-clicking a .bat file).
  • To avoid overwhelming users with multiple dialogs, EPM limits dialog display for 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. 

Rate this article:
  • 504 Views
  • 0 comments
  • 0 Likes
Article Dashboard
Version history
Last Updated:
‎11-05-2026 11:50 AM
Updated by: