Skip to main content
Question

EPM-M Prompt Disappears Within 1–3 Seconds (macOS Tahoe 26.4, EPM-M 26.1)

  • July 9, 2026
  • 1 reply
  • 32 views

 

We are experiencing an issue where the Support Desk (Challenge/Response) prompt disappears within 1–3 seconds, preventing users from entering a response code and elevating applications.

Environment

  • EPM-M Version: 26.1.0.120
  • OS: macOS Tahoe 26.4
  • Users sometimes receive a "Deadline Reached" notification

We reviewed KB0020349, but the issue is documented as fixed in 23.7.1+, and our clients are already on 26.1.0.120.

A comparison between working and affected devices showed no significant differences other than hardware (M2 vs M3 Pro and different Mac models).

BeyondTrust advised that newer macOS versions may limit the prompt display time to approximately 10–14 seconds and suggested Challenge/Response or JIT Application Requests as workarounds. However, in our case, the prompt disappears in only 1–3 seconds, which seems abnormal.

 

 

As soon as message gets disappeared, users get attached message :-

 

BeeKeepers, please let me know :- 

  • Has anyone seen this behavior on EPM-M 26.1 ?
  • Are there any known causes or workarounds?
  • Are there specific logs that capture why the Support Desk prompt is being dismissed?

Any insights would be greatly appreciated.

1 reply

  • BeyondTrust Employee
  • July 13, 2026

Hi ​@PritishSingh, the guidance about newer macOS builds capping notifications display to roughly 10-14 seconds is expected behavior (this deadline is an OS requirement), but I agree a prompt vanishing in 1-3 seconds is definitely abnormal.

I would be curious to know what application or rule you are triggering when you see the deadline being reached so quickly. For a workaround, perhaps leveraging JIT Application Requests would allow for an end-user to submit a request which can be actioned (allow/deny) directly from within PMC. 

That being said, I think your best path forward is going to be working with our support team. For a support case I’d start with grabbing a Capture Config during replication (full system logs).