Yes, the `--disable-search-engine-choice-screen` flag is a standard Chromium/Chrome command-line switch (intended mainly for automation/testing). It is checked early in Chrome’s search engine choice logic and suppresses the DMA/EEA “Choose your search engine” modal when present.
Inteset Secure Lockdown supports custom Chrome switches through the **Switches** section under the Chrome Lockdown tab, so the flag should be passed through when Inteset launches Chrome.
Since you’ve already tried it (and the non-standard registry keys) without success, try these steps:
1. **Double-check the Switches entry**
Enter it on its own line. Test both forms:
`--disable-search-engine-choice-screen`
and
`disable-search-engine-choice-screen`
Also add `--no-first-run` (Chrome launcher docs note that the disable can be guarded behind this in some versions). Restart after saving.
2. **Chrome version**
Update Chrome. Early Chrome 127 builds had issues with the flag that were addressed in later releases (around M129+). Confirm the exact version under Help → About Google Chrome (or via `chrome://version` if accessible).
3. **Browser Reset / profile persistence**
If Inteset is set to clear history, cache, or reset the browser on inactivity/exit (Browser Reset options), the “choice completed” preference is wiped each time. The flag should still suppress the dialog on every launch, but verify the switches are actually reaching Chrome (see verification tip below).
4. **Preferred reliable method for kiosks – force a default search provider via policy**
The registry keys you tried (`SearchEngineChoiceSettings` / `SearchEngineChoiceEnabled`) are **not** official Chrome policies. Setting a managed default search provider causes Chrome to treat the choice as controlled by policy and skip the screen.
Under `HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome` (or the HKCU equivalent):
- `DefaultSearchProviderEnabled` = dword:1
- `DefaultSearchProviderName` = `Google` (or your preferred engine)
- `DefaultSearchProviderSearchURL` = `https://www.google.com/search?q={searchTerms}`
- Optionally `DefaultSearchProviderSuggestURL` = `https://www.google.com/complete/search?client=chrome&q={searchTerms}`
This is the standard enterprise approach and works well on locked-down/kiosk systems. (Policies are documented in Chrome’s policy templates.)
5. **Region note**
The modal is primarily shown for profiles detected as being in the EEA (Digital Markets Act). Outside the EEA it normally does not appear. Country detection can sometimes be influenced by locale or other factors.
**Verification tip**: Temporarily allow access to `chrome://version` (or check Chrome’s command line in Task Manager → Details → Command line column) to confirm the switches are actually present when Chrome starts under Inteset.
