## What this teaches

How to chrome team removes --load-extension switch on Chrome builds.

## The problem

Issue SeleniumHQ/selenium#15788 (closed, 55 comments): ### Description

They remove --load-extension that cause `.AddExtensions()` and other similar method broken

their commit [https://chromium.googlesource.com/chromium/src/+/290ed8046692651ce76088914750cb659b65fb17%5E%21/chrome/browser/extensions/extension_service.cc](https://chromium.googlesource.com/chromium/src/+/290ed8046692651ce76088914750cb659b65fb17%5E%21/chrome/browser/extensions/extension_service.cc)

Version affected: Chrome 137

### Reproducible Code

```cs
var options = new ChromeOptions();
options.AddExtensions(_extensionsPath);
var driver = new ChromeDriver(options);
```

###...

## What worked (verified answer)

Chrome 137 removed the `--load-extension` switch, which breaks `AddExtensions()` and similar methods. Temporary workaround that users confirmed: add this argument instead:

--disable-features=DisableLoadExtensionCommandLineSwitch

Longer term, the Selenium team's direction is WebDriver BiDi or Chrome for Testing. BiDi-based extension support landed for Java and Python in the reviewed thread, but not for .NET, so .NET users should stick with the workaround for now.

## Source

gh:SeleniumHQ/selenium#15788 - https://github.com/SeleniumHQ/selenium/issues/15788