Leapwork Trial - Frequently Asked Questions
Leapwork Trial - Frequently Asked Questions
Leapwork is asking me for license key during installation. Where can I find it?
This indicates that you have accidentally installed more components than what is required. The Leapwork installation package includes all three components of Leapwork i.e. Studio, Controller and Agent. However, for the Leapwork Cloud Trial version you only need to install only Leapwork Studio component.
The installation of only Leapwork Studio will not require the license key. For details of how to successfully do the installation, see “Do I need to install all three components of Leapwork?”.
Do I need to install all three components of Leapwork?
Leapwork installation package includes all three components of Leapwork i.e. studio, controller and agent. However, for the Leapwork Cloud Trial version you only need to install Leapwork Studio.
To install and configure Leapwork Studio, see the video in the guide or follow the steps below:
- Download the Leapwork release provided to you.
- Make sure that only the Leapwork Studio option is checked during setup. Other components are not needed and should be left unchecked.
- Click Next at each step without changing any other settings, as the installation is preconfigured.
- Open Leapwork Studio.
- In the Select Controller window, add the following details provided by Leapwork:
- Controller Address: trial-plz-02.leapwork.cloud?authtoken=trial-8f27c6ef-7701-4a8f-b90e-9a6079f76d36&isCloudHosted=true
- Port Number: 443
- API URL: https://trial-api-plz-02.leapwork.cloud:9001/help/index
- Credentials: use the login information shared in the welcome email.
You will now have Leapwork version 2025.2.0 installed and configured.
I have a Mac and want to install Leapwork, can I do that?
Leapwork is a Windows-only platform. It cannot be installed natively on a Mac. However, Mac users can still run Leapwork by:
- Using virtualization (Parallels, VMware) to run Windows.
- Booting into Windows via Boot Camp.
- Connecting to a Windows machine or VM via remote desktop.
- Or using cloud-hosted Windows Agents to run Leapwork remotely.
I am getting the error “Could not connect to the Controller”. What do I do?
First, you check if the Leapwork Controller service is running.
You do that by opening the Services app (search for "services.msc" in the Run box). Then you locate the service named "LEAPWORK_CONTROLLER" and you check if the service is running. If it's not, start or restart it.
If (re-)starting Controller service didn’t resolve it, then verify network connectivity.
You do that by validating that the machine where you have Leapwork studio installed is able to communicate with the Leapwork controller machine. This can be quickly verified by performing a ping command to the IP address/machine name of the controller machine (Controller machine IP/Machine name is provided by Leapwork SDR as part of the email). Similarly, it should also be to communicate with the port 9000 which is used for connecting with the Leapwork Cloud controller machine. To do please refer to the below steps.
Test with telnet:
- Open the command prompt on Leapwork Studio machine.
- Use the command
telnet <Controller IP address> 9000in the command prompt. - If telnet is not recognized, please enable it referring to the steps in the article: How can we check connectivity among Leapwork Studio, Controller and Agent? and repeat the step 2.
Ping the Controller:
- Open the command prompt on Leapwork Studio machine.
- Use the command
ping <Controller IP address>to check if the Controller machine is reachable. - If the ping request times out, it means that Leapwork studio and the controller machine are not able to communicate with each other.
If you've tried these steps and are still unable to connect, contact Leapwork's Priority Support for further assistance.
I am getting the error: “No browser window is open so navigation cannot continue”. What do I do?
There are two common challenges that you can explore. First, verify that your browser works as expected. Secondly, check for a mismatch between your browser version and your driver version. If these do not resolve it, try the steps further down. Remember to retry running your flow after each of the steps.
Verify Browser functionality
Attempt to manually open the Edge or Chrome browser to ensure it launches successfully.
If you cannot open the browser manually, resolve the issue at the browser level before proceeding further.
If the browser opens without issues, proceed to checking for a mismatch between Browser and Driver versions.
Check for mismatch between Browser version and Driver versions
In Google Chrome
- Open Chrome
- Go to Menu (⋮) → Help → About Google Chrome
- Alternatively, enter
chrome://settings/helpin the address bar - Note the version number
In Microsoft Edge
- Open Edge
- Go to Menu (…) → Help and feedback → About Microsoft Edge
- Alternatively, enter
edge://settings/helpin the address bar - Note the version number
Then, you check the WebDriver version. This can be done using Selenium Manager (default part of Leapwork Studio) or manually.
Selenium Manager in Leapwork will automatically download the matching driver for your browser.
If you need to verify it manually, then navigate to the following path: C:\Users\UserName\.cache\selenium\chromedriver\win64 to confirm the driver version for Chrome.
If there is a mismatch between the Browser version and the Driver version, you need to resolve this. This is done by either by updating either the browser or the WebDriver.
Try alternative automation methods
Test the functionality using Selenium or through an extension method to see if it resolves the issue.
Expand start web browser block and try the below approaches:
Check selenium checkbox and run the flow to see whether selenium web driver is working or not.
Uncheck selenium checkbox and run the flow to see whether extension for (edge or chrome whichever browser that you have checked in browser to start field).
Increase Default Timeout
In some systems, performance slowness or other factors can cause delays. Increasing the default timeout setting can help resolve such issues.
In the Start Web block → Expand the block, increase the default timeout (e.g., 30 → 60 seconds).
Add User Data Directory Option
Modify the browser start options to include the following flag:
--user-data-dir=C:\temp
This method is known to resolve issues in various cases, such as profile-related errors or permission conflicts., one of them is
Adding options in the Start Web browser block
Other options you can try in start options of Start web Browser block: --incognito, --guest, --no-sandbox, --remote-debugging-port=9222
--incognito
Opens the browser with no saved data(no cookies, no cache).
--guest
Starts a temporary, throwaway profile with most extensions off.
--no-sandbox
Turns off a Chrome/Edge security feature so the browser can start on locked-down servers/VMs.
--remote-debugging-port=9222
Opens a DevTools port so the browser can be controlled/debugged.
Note: If you want to read more about the start options and their meaning, visit here.
Terminate Browser Processes
Kill all instances of Edge or Chrome using the Task Manager to ensure no background processes are interfering.
Enable Developer Mode in Edge
Open Edge and navigate to edge://extensions/
Enable Developer Mode by toggling the switch at the top right of the Extensions page.
Disable Startup Boost
Follow the instructions in this article to disable the Startup Boost feature: Leapwork Community Portal
Verify Proxy Settings
Ensure no proxy is configured in both Windows settings and the Leapwork application.
Check Policies
Verify that no policies are blocking communication between the browser and the WebDriver.
Verify User Permissions
Confirm that the user running the process has Administrator rights.
If not, this might cause access issues to the Edge WebDriver located in the C: drive. Ensure that permissions are correctly configured for the WebDriver.
Error: DevToolsActivePort file doesn’t exists
Add --remote-debugging-pipe to start options
Selenium Manager Unable to download driver
Check if following domains are whitelisted by pinging them:
- For chrome: googlechromelabs.github.io, storage.googleapis.com
- For edge: msedgedriver.azureedge.net
If the above whitelisting is fine, then follow below steps:
- Go to
C:\Program Files\Leapwork\Studio\selenium-manager\windowsor agent directory, wherever the issue is occurred. - Open CMD to this location.
- Run command :
selenium-manager.exe --browser chrome --debugand check if it is able to download the driver and place it in .cache folder, as shown below: - if the request is failed with an error: request or response body error: operation timed out, then connect with your IT team, to check why the driver download is not working.
- There is a possibility that your firewall or anti-virus might be causing this or the URL for downloading needs to be whitelisted to allow file download, because pinging the URL in above steps was working fine.
I am getting the error: “No browser window is open so navigation cannot continue” with a flow using Microsoft Edge running in IE Mode. What do I do?
Resolving IE Mode Issues in Edge Due to Protected Mode Settings
- The error typically occurs because Protected Mode settings in Internet Explorer (IE) mode are not configured at the same level across all security zones.
- Adjust Protected Mode Settings
- Step 1: Configure Settings in Internet Options
Open the Start menu, type Internet Options, and press Enter.
Navigate to the Security tab.
For all zones ( Internet, Local intranet, Trusted sites, Restricted sites, Custom):
- Ensure that Protected Mode settings are at the same level (e.g., mark all zones as "Low" if required).
- Step 2: Configure Settings in the Registry Editor
- Open the registry editor, and navigate to the following path: Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\
- For each of the five security zones (0–4):
- Check if there is a REG_DWORD value named 2500.
- If it does not exist, create it.
- Set the value data for 2500 to 0 (enables Protected Mode) or 3 (disables Protected Mode) for all zones.
- Step 1: Configure Settings in Internet Options
Check for TabProcGrowth Errors in Debug Logs
- If debug logs indicate issues with the TabProcGrowth registry key for Agent or Studio, follow these steps:
- Open the registry editor, go to
HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main - Ensure that the registry key TabProcGrowth is present
- If not, then at
HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\TabProcGrowth, create a new Reg_DWORD with data value 0
Special Case Resolving "No Browser Window" Incidents Caused by Windows Update KB5044273
- Issue Overview
- The “No Browser Window” error has been reported frequently due to the Windows update KB5044273. Follow the steps below to resolve the issue for both Preview Runs and Scheduled Runs.
- For Preview Run on the Local Machine
- Go to Studio.exe
- Go to C drive → Program Files → Leapwork → Studio
- Find the Leapwork Studio.exe
- Press Shift + Right-click on the exe file
- Click Run as a Different User
- Enter the credentials of the currently logged-in user (both Admin and non-Admin accounts will work)
- Go to Studio.exe
- For Remote preview run or scheduled run: It is only working if we provide admin user creds while adding an agent in Leapwork studio
Note: If the above steps don’t resolve the issue, then it needs to be investigated and you should contact Leapwork Priority Support.