Why didn't AutoElevate prompt for a request?
Common reasons why AutoElevate may not prompt.
Written by Daniel Rivera
Updated at August 21st, 2026
Table of Contents
If AutoElevate is not prompting for an elevation request, there are several common causes that should be checked before opening a support case.
Check the Agent Elevation Mode
Verify that the endpoint is configured for Live mode.
AutoElevate only responds to elevation requests when the agent is operating in Live mode. If the endpoint is set to Audit or another mode, requests may not generate prompts or approval notifications.
For additional information, see:
Verify User Account Control (UAC) Settings
AutoElevate relies on Windows User Account Control (UAC) events to detect elevation requests.
If UAC is disabled or configured with incompatible settings, Windows may not generate the elevation prompt that AutoElevate requires to intercept and process the request.
For detailed guidance, see:
Confirm the Application Actually Triggers UAC
Not every installer or application generates a UAC prompt.
Some applications install only within the current user's profile and do not require administrative privileges. In these cases, Windows may never trigger a UAC event, which means AutoElevate will not display an approval request.
If the application installs successfully without requiring administrator access, this behavior is expected.
Verify Firewall and Network Whitelisting
AutoElevate requires outbound HTTPS (TCP 443) connectivity to multiple cloud services. If required endpoints are blocked by a firewall, proxy, web filter, SSL inspection appliance, or certificate interception solution, elevation requests and notifications may not be delivered correctly. The required endpoints are documented in the Firewall Whitelisting article.
Network-related issues can sometimes appear as though AutoElevate is simply not generating requests, when the underlying issue is that the agent cannot successfully communicate with AutoElevate services.
A common indicator of a connectivity or certificate trust issue is the following error message:
"Could not establish trust relationship for the SSL/TLS secure channel."
If you encounter this error, verify:
- Required AutoElevate endpoints are allowlisted.
- Outbound HTTPS (TCP 443) traffic is permitted.
- SSL inspection, HTTPS decryption, certificate rewriting, or proxy solutions are not interfering with AutoElevate communications.
- The device trusts the certificates presented during outbound connections.
- Security products are not blocking or modifying AutoElevate traffic.
For detailed endpoint requirements and hostname allowlists, see:
Note: The AutoElevate agent, admin portal, and related services may communicate with multiple cloud-hosted endpoints. Allowlisting only part of the required infrastructure can result in intermittent behavior, delayed notifications, or requests that never appear for approval.
Still Not Receiving Requests?
If all of the above items have been verified and requests are still not appearing:
- Confirm the AutoElevate agent is installed and communicating normally.
- Test with an application that is known to generate a UAC prompt.
- Review the endpoint for security software, SSL inspection, or network controls that may interfere with AutoElevate communications.
- Contact CyberFOX Support and provide any error messages, screenshots, and relevant AutoElevate logs.