cyberangles blog

How to Fix 'Chrome Version Must Be Between 71 and 75' Error After Updating to ChromeDriver 2.46

If you’ve recently updated ChromeDriver to version 2.46 and encountered the frustrating error message “Chrome version must be between 71 and 75”, you’re not alone. This error arises due to a mismatch between the version of Google Chrome installed on your system and the ChromeDriver version you’re using. ChromeDriver 2.46 is explicitly designed to work with Chrome browser versions 71–75, but if your Chrome browser has updated to a newer version (e.g., 76 or later), ChromeDriver 2.46 will fail to recognize it, triggering this error.

In this blog, we’ll break down why this error occurs, walk through common scenarios that cause it, and provide step-by-step solutions to fix it. We’ll also cover preventive measures to avoid similar issues in the future.

2026-02

Table of Contents#

  1. Understanding the Error
  2. Common Scenarios Triggering the Error
  3. Step-by-Step Solutions
  4. Preventive Measures to Avoid Future Errors
  5. Conclusion
  6. References

Understanding the Error#

What Causes the Error?#

ChromeDriver is a separate executable that Selenium WebDriver uses to control Google Chrome. ChromeDriver versions are tightly coupled with specific Chrome browser versions—each ChromeDriver release supports a fixed range of Chrome versions. For example:

  • ChromeDriver 2.46 is compatible with Chrome 71, 72, 73, 74, and 75.
  • ChromeDriver 76.0.3809.68 is compatible with Chrome 76, and so on.

If your Chrome browser updates to a version outside the supported range of your installed ChromeDriver (e.g., Chrome 76+ with ChromeDriver 2.46), ChromeDriver cannot communicate with the browser, resulting in the error:

session not created: This version of ChromeDriver only supports Chrome version 75  
Current browser version is 114.0.5735.199 with binary path [path]

Common Scenarios Triggering the Error#

The error typically occurs in these situations:

  1. Automatic Chrome Updates: Chrome often updates itself in the background. If Chrome updates to v76+ but your ChromeDriver is still 2.46 (for v71–75), the mismatch occurs.
  2. Manual ChromeDriver Update: You may have updated ChromeDriver to 2.46 without realizing it only supports Chrome 71–75, while your Chrome is already newer.
  3. Outdated Automation Scripts: If your Selenium scripts hardcode an older ChromeDriver path, they won’t automatically adapt to newer Chrome versions.

Step-by-Step Solutions#

Method 1: Identify Your Current Chrome and ChromeDriver Versions#

First, confirm the versions of Chrome and ChromeDriver installed on your system.

Check Chrome Browser Version:#

  1. Open Chrome.
  2. Click the three dots (⋮) in the top-right corner → Help → About Google Chrome.
  3. Note the version (e.g., 114.0.5735.199).

Check ChromeDriver Version:#

  • Windows: Open Command Prompt and run: 
    chromedriver --version
  • macOS/Linux: Open Terminal and run: 
    chromedriver --version

You’ll see output like:

ChromeDriver 2.46.628402 (536cd7adbad73a3783fdc2cab92ab2ba7ec361e1)

Method 2: Update ChromeDriver to a Compatible Version#

The best solution is to update ChromeDriver to a version that supports your installed Chrome browser.

Step 1: Find the Correct ChromeDriver Version#

ChromeDriver’s official download page lists compatibility. For example:

  • Chrome v114 → ChromeDriver v114.x.x.x
  • Chrome v112 → ChromeDriver v112.x.x.x

Tip: If your Chrome version is 114.0.5735.199, the first three numbers (114.0.5735) determine the ChromeDriver version to use.

Step 2: Download and Replace ChromeDriver#

  1. Go to the ChromeDriver Downloads page.

  2. Select the version matching your Chrome browser (e.g., 114.0.5735.90 for Chrome 114).

  3. Download the appropriate binary for your OS (Windows, macOS, Linux).

  4. Extract the ZIP file to get the chromedriver executable.

  5. Replace the old ChromeDriver (v2.46) with the new executable in your system’s PATH or your project directory.

    • Windows: Save chromedriver.exe to C:\Program Files\ChromeDriver\ and add this folder to your PATH (Control Panel → System → Advanced System Settings → Environment Variables).
    • macOS/Linux: Save chromedriver to /usr/local/bin/ (requires sudo privileges) or your project’s drivers folder.

Method 3: Downgrade Chrome to a Compatible Version (Last Resort)#

If updating ChromeDriver isn’t feasible (e.g., due to corporate restrictions), downgrade Chrome to v71–75.

Step 1: Uninstall Current Chrome#

  • Windows: Go to Settings → Apps → Apps & features, select “Google Chrome,” and uninstall.
  • macOS: Drag Chrome from Applications to the Trash.
  • Linux: Run sudo apt remove google-chrome-stable (Debian/Ubuntu) or sudo dnf remove google-chrome-stable (Fedora).

Step 2: Download an Older Chrome Version#

Use a trusted archive to download Chrome 71–75. Avoid untrusted sites to prevent malware. Recommended sources:

Select a version like 75.0.3770.142 (last version supported by ChromeDriver 2.46).

Step 3: Install and Disable Auto-Updates#

Install the older Chrome version. To prevent automatic updates:

  • Windows: Go to C:\Program Files\Google\Update\ and rename GoogleUpdate.exe to GoogleUpdate_old.exe.
  • macOS: Run defaults write com.google.Keystone.Agent checkInterval 0 in Terminal.

Method 4: Use WebDriverManager (Automated Solution)#

For developers, WebDriverManager (by Boni Garcia) automatically downloads and configures the correct ChromeDriver version. It eliminates manual version management.

Step 1: Add WebDriverManager to Your Project#

  • Maven (Java): Add this dependency to pom.xml:

    <dependency>  
    <groupId>io.github.bonigarcia</groupId>  
    <artifactId>webdrivermanager</artifactId>  
    <version>5.5.3</version> <!-- Check for the latest version -->  
</dependency>

  • Gradle (Java): Add to build.gradle:

    implementation 'io.github.bonigarcia:webdrivermanager:5.5.3'

  • Python: Install via pip:

    pip install webdriver-manager

Step 2: Update Your Selenium Script#

Use WebDriverManager to initialize ChromeDriver:

Java Example:

import org.openqa.selenium.WebDriver;  
import org.openqa.selenium.chrome.ChromeDriver;  
import io.github.bonigarcia.wdm.WebDriverManager;  
 
public class ChromeTest {  
    public static void main(String[] args) {  
        // WebDriverManager downloads the correct ChromeDriver  
        WebDriverManager.chromedriver().setup();  
        WebDriver driver = new ChromeDriver();  
        driver.get("https://www.google.com");  
    }  
}

Python Example:

from selenium import webdriver  
from webdriver_manager.chrome import ChromeDriverManager  
 
driver = webdriver.Chrome(ChromeDriverManager().install())  
driver.get("https://www.google.com")

Preventive Measures to Avoid Future Errors#

  1. Disable Chrome Auto-Updates Temporarily: Pause updates if you need stability for critical projects (Settings → About Chrome → “Pause updates”).
  2. Use WebDriverManager: Automate ChromeDriver management to avoid version mismatches.
  3. Check Compatibility Regularly: Refer to the ChromeDriver Release Notes before updating Chrome or ChromeDriver.
  4. Test in Isolated Environments: Use virtual machines (e.g., VirtualBox) or containers (Docker) to test with specific Chrome/ChromeDriver versions.

Conclusion#

The “Chrome version must be between 71 and 75” error is a common version mismatch issue between Chrome and ChromeDriver 2.46. The best solutions are updating ChromeDriver to a compatible version or using WebDriverManager for automated management. Downgrading Chrome should only be a last resort. By following these steps, you’ll resolve the error and ensure smooth Selenium automation.

References#