Use this article if Ranorex Studio, Ranorex Agent, or Ranorex test execution does not work as expected and security software may be preventing Ranorex components from running or communicating.
Symptoms
Security software can interfere with Ranorex in different ways.
You may experience one or more of the following:
- Ranorex Studio or another Ranorex component does not start.
- Ranorex Spy cannot interact with an application.
- Application instrumentation does not work correctly.
- A Ranorex process closes unexpectedly.
- Test execution fails without a clear error.
- Communication with Ranorex Agent or another Ranorex component fails.
- Executable files generated by a Ranorex test are blocked.
- Ranorex files or processes are quarantined by endpoint security software.
- A test works on one machine but fails on another machine with different security policies.
Cause
Antivirus, endpoint detection and response (EDR), application-control, firewall, or other security software can prevent Ranorex components from performing actions required for UI automation.
Depending on the security product and policy, it may block:
- Process injection
- Inter-process communication
- Application instrumentation
- Network communication
- Execution of generated test files
- Access to application processes
- Ranorex services or agents
- Changes performed during application or browser instrumentation.
Corporate security policies may also prevent users from changing the applicable settings.
Diagnose the issue
Review your antivirus or endpoint-security application for:
- Blocked applications
- Quarantined files
- Security alerts
- Application-control events
- Exploit-protection events
- Firewall events
Look for entries related to Ranorex components or the executable generated by your Ranorex test solution.
Compare another environment
If possible, run the same test on another machine with the same:
- Ranorex Studio version.
- Application version.
- Test solution.
- Operating system configuration.
If the issue only occurs on a machine with a different security configuration, security software may be involved.
Contact your system administrator
In managed environments, security settings may be controlled centrally.
Provide your system or security administrator with:
- The affected Ranorex executable or process.
- The time the problem occurred.
- Relevant security-software events.
- The Ranorex version.
- A description of the action that was blocked.
This information can help determine which security rule is responsible.
Resolution
If security software is blocking a legitimate Ranorex component, configure an appropriate exception or allow-list rule according to your organization's security policies.
The exact configuration depends on the security product.
Important: Do not permanently disable antivirus, endpoint protection, or other organizational security controls as a troubleshooting solution. Work with your system administrator to create the minimum exception required for Ranorex.
After changing the security configuration:
- Restart the affected Ranorex component.
- Restart the application under test if applicable.
- Repeat the action that previously failed.
- Confirm that the security software no longer blocks the Ranorex process.
If the issue continues
If the problem remains after your administrator confirms that Ranorex is not being blocked, investigate other possible causes such as:
- Application instrumentation.
- Windows privileges.
- Unsupported technologies or versions.
- Missing prerequisites.
- Network configuration.
- Runtime environment configuration.
If necessary, contact Ranorex Support and include the relevant Ranorex logs and security-software event information.