Installed Chrome or the Browz engine
The two engines a profile can use, what each controls, and when to choose which.
Error codes: signed_chrome.unsupported_setting, signed_chrome.blocklist_invalid, signed_chrome.not_admitted, signed_chrome.extra_switches_refused, engine.unsupported
Each profile chooses an engine when it is created. Browz Chromium is the Browz engine, shipped with the app; it suits most profiles and supports every profile control, including the distinct fingerprint policy.
Installed Chrome (experimental, limited controls) runs your own copy of Google Chrome for the profile. It controls CPU cores, timezone, languages and an experimental sRGB colour option. Rendering is native, so separate Installed Chrome profiles can still be linked. Managed extensions are unavailable.
- Installed Chrome needs Google Chrome installed on the computer. The Browz engine does not.
- Installed Chrome always requires a proxy.
- Some global settings are not supported by Installed Chrome. If one is changed from its default, Start is refused with a message saying the Installed Chrome backend does not yet support it, followed by the setting, for example Open maximised, Open fullscreen, window size, Autoplay, Download folder or Page zoom other than 100 percent. Restore those settings to their defaults, or use the Browz engine for that profile.
- Extra switches are refused on their own: if Settings, Browser, Extra switches is not empty, Start says Installed Chrome backend does not accept extra browser switches. Clear Extra switches, or use the Browz engine for that profile.
- Block images, startup pages and the website blocklist do work with Installed Chrome.
Installed Chrome needs a desktop session →
After Google Chrome updates itself →
Still stuck? Export diagnostics and contact support.