Hi ... this link will be help to you https://support.mozilla.org/en-US/kb/connection-settings-firefox

Can you be more specific? I can't see what connection settings have to do with turning off browser.launcherProcess through autoconfig.

I'm on Linux, so can't test this.

Did you check the Browser Console for possible error messages?

I'm not sure how this pref would work in this case because Firefox is already started when the profile is loaded.

See also:

• https://wiki.mozilla.org/Platform/Integration/InjectEject/Launcher_Process/

Its code cannot start nor rely on prefs, XPCOM, nsString, crash reporter, or other aspects of the Gecko runtime. Header-only code that does not depend on xul.dll (such as MFBT) is safe to use in the launcher process;

Can anyone help with a simple answer? I like to know if I as an IT admin for several non admin users can change the Firefox setting "browser.launcherProcess.enabled" which since Firefox 68 has been set to true. I thought that any config settings could be changed with autoconfig and a cfg file. The user can always open about:config and change the setting manually, but I like to automate this.

You need to make sure to use lockPref instead of just pref. Using just pref will only set the value, but it can still be changed by the user. Using lockPref will set the value and prevent the user from changing the value.

It sounds like you probably want to use the following code instead:

lockPref("browser.launcherProcess.enabled", false);

Hope this helps.

Using lockPref("browser.launcherProcess.enabled", false); did change the value from true to false, thanks Wesley, but is there no better solution besides using lockPref? Because now the user is unable to change it back. Why is just using the pref function not able to change the value of browser.launcherProcess.enabled?