Looking for something in particular?

Resolving Failed to Create ChromeDriver Error

In some cases, you may experience compatibility issues when Google releases new versions of the Google Chrome browser. This can prevent your Automation tests from running correctly.

Users affected by this issue generally see a failed to create ChromeDriver error when attempting to execute test cases in any run mode, including via Apache Ant in conjunction with any continuous integration solution.

See the example error message below.

Image showing an example of the failed to create ChromeDriver error message

To resolve this issue, you should update your ChromeDriver version.

Disabling Auto-Update

Step 1: Disable Automation’s auto-update feature (ChromeDriver versioning) by entering the provar.ini file at the installed location. Typically, this is added at the end of the script.


Example (click to enlarge):

For Apache Ant execution, the user can use the following commands to set this variable:

For Windows Set ANT_OPTS to:


For Linux or Mac Export ANT_OPTS to:


Step 2: Delete any ChromeDriver folder inside the user home folder. {UserHome}/Provar/.chromeDriver.

Note: Ensure that there are no ChromeDriver processes running. Kill the processes if there are any.

Step 3: Execute the test case to launch the browser session.

What should I do if I don’t have permissions to update my provar.ini file?

Refer to this help page for an alternative way to override your ChromeDriver version using your project’s lib folder.

If you implement this solution and are still encountering difficulties, please get in touch with for additional help.

Review Provar on G2
Documentation library

Trying to raise a case with our support team?

We use cookies to better understand how our website is used so we can tailor content for you. For more information about the different cookies we use please take a look at our Privacy Policy.

Scroll to Top