Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Disable creation of private browsing shortcut

  • 3 பதிலளிப்புகள்
  • 1 இந்த பிரச்சனை உள்ளது
  • 4 views
  • Last reply by Mike Kaply

Im working on a deployment package for Mozilla Firefox 106.0.1 when launching Firefox on a brand new user it automatically creates a shortuct for private browsing. Im looking for a way to disable this as the package im creating is an appv package and this new shortcut installs in users profile, so it won't be uninstalled. I have searched google but cant find any hits.

We have the following for customization: Application directory\defaults\pref: localsettings.js with these settings: pref("general.config.obscure_value", 0); // only needed if you do not want to obscure the content with ROT-13 pref("general.config.filename", "mozilla.cfg");

Application directory\mozilla.cfg with these settings: // Don't show WhatsNew on first run after every update pref("browser.startup.homepage_override.mstone","ignore");

// Don't show 'know your rights' on first run pref("browser.rights.3.shown", true);

// Disable Policy Notice on First Run pref("toolkit.telemetry.reportingpolicy.firstRun", false);

// Disable checkDefaultBrowser lockPref("browser.shell.checkDefaultBrowser", false);

Application directory\distribution\policies.json with the following settings: {

 "policies": {
   "DisableAppUpdate": true,

"DontCheckDefaultBrowser": true } }

Im working on a deployment package for Mozilla Firefox 106.0.1 when launching Firefox on a brand new user it automatically creates a shortuct for private browsing. Im looking for a way to disable this as the package im creating is an appv package and this new shortcut installs in users profile, so it won't be uninstalled. I have searched google but cant find any hits. We have the following for customization: Application directory\defaults\pref: localsettings.js with these settings: pref("general.config.obscure_value", 0); // only needed if you do not want to obscure the content with ROT-13 pref("general.config.filename", "mozilla.cfg"); Application directory\mozilla.cfg with these settings: // Don't show WhatsNew on first run after every update pref("browser.startup.homepage_override.mstone","ignore"); // Don't show 'know your rights' on first run pref("browser.rights.3.shown", true); // Disable Policy Notice on First Run pref("toolkit.telemetry.reportingpolicy.firstRun", false); // Disable checkDefaultBrowser lockPref("browser.shell.checkDefaultBrowser", false); Application directory\distribution\policies.json with the following settings: { "policies": { "DisableAppUpdate": true, "DontCheckDefaultBrowser": true } }

All Replies (3)

> Im looking for a way to disable this as the package im creating is an appv package and this new shortcut installs in users profile, so it won't be uninstalled.

Can you be more specific as to what you mean by it won't be uninstalled? Does AppV remove shortcuts when it's done? Or is it some other installer?

You can try setting the preference:

browser.privacySegmentation.createdShortcut

to true and we shouldn't create the shortcut.

AppV is basically virtualization of an application that runs in its own virtual bubble on windows. So the extra shortcut gets created in the local profile of the user launching the appv application, when uninstalling the appv application it dosent remove the local installed shortcut as its not a part of the package.

We did solve this after searching the config options and found: browser.privateWindowSeparation.enabled Setting it as follows solved our issue: lockPref("browser.privateWindowSeparation.enabled", false);

The setting: browser.privacySegmentation.createdShortcut Did not solve this issue as it was reset to default at each launch of mozilla firefox.

This did stop the shortcut from being created at launch. This question can be marked as completed.

Glad that worked.

Are you buy chance getting a profile at each startup?

That would reset the preference.