On FF Portable 63, the Prompt to Update Cannot Be Disabled

Mozilla removes the option to disable auto updates in Firefox 63. To block auto updates, create a directory called distribution inside the Firefox 63 portable directory. Then create a file called policies.json with the following texts using a text editor:

{
"policies": {
"DisableAppUpdate": true
}
}

and put that file inside the distribution directory.

See below for references:
https://support.mozilla.org/en-US/kb/customizing-firefox-using-policiesjson
https://github.com/mozilla/policy-templates/blob/master/README.md

There could be other alternatives, perhaps John T. Haller or Gord Caswell could chime in. I understand that auto updates are good for security reasons. I really hope that PortableApps.com Platform offers a feature to block auto/forced updates for any apps for those advanced users who prefer to manually update their apps.

The FirefoxPortable.exe is configured to specifically wait for the updater to complete its run. There is a bug where it may not if you have about 300 or more processes running on your system, due to a bug in the FindProcDLL NSIS plugin. It also won't occur if you have the launcher configured not to wait for Firefox or set to allow multiple instances (aka all bets are off).

We can't distribute Firefox Portable with the updater fully disabled due to licensing. I could make an addition to disable it when run in conjunction with the PA.c Platform since it will handle your updates for you.

In 63 still available the not automatic update button...

If there's still some confusion with using the policies.json file here's what I did, with success. You can confirm the policies are in place and working, see below. Most of the help has been offered already, I'm only hoping to clarify some details.

I used Notepad++ to create policies.json (save-as .json), mostly because I'm familiar with NPP, but the syntax highlighting is nice to have, this will help with the json code.

The details below worked on the PortableApps version of Firefox, I'm running 63.0.3. There's a policies_json_readme_zip at github with help for various versions of firefox - search Google.

OK:

The Folder/File Location:
``````````````````````````````````
This is the location for the new \distribution folder (notice firefox.exe), drop the policies.json file in each folder.

...\PortableApps\FirefoxPortable\App\Firefox\distribution\
...\PortableApps\FirefoxPortable\App\Firefox64\distribution\

The Code:
```````````````
I paid attention to spacing (indentation), this may not matter but I noticed it in the readme. I believe the trick with multiple lines is the use of the comma (,) after each policy when there's multiple lines, not needed if you only want to disable app.update...

Note: The forum seems to remove indentation, again, it may not matter (I don't know), but in case.
-2- spaces -> "policies": {
--4-- spaces -> "DisableAppUpdate": true

*Simple Example:
````````````````````````

{
"policies": {
"DisableAppUpdate": true
}
}

**Complex Example:
````````````````````````````

{
"policies": {
"DisableAppUpdate": true,
"DontCheckDefaultBrowser": true,
"DisableBuiltinPDFViewer": true,
"DisableFirefoxStudies": true,
"DisablePocket": true,
"DisableTelemetry": true,
"DisableFirefoxScreenshots": true
}
}

Verifying Policies:
````````````````````````
about:policies
If you know how to find about:config, you'll also want to start using about:policies. This is a non-editable check, you only want to check your policy Name & Value are Active and without error. My window was simple, a more complex policy might show more details. If there's errors supposedly there's links to follow to get help.

about:config
I noticed after getting the policy file to work there were some Preferences with a Status of locked - here's a few I noticed, I'm sure there's more:

* toolkit.telemetry.enabled -- locked -- false
* pdfjs.disabled -- locked -- true
* extensions.pocket.enabled -- locked -- false
* extensions.screenshots.disabled -- locked -- false

Firefox Options
Some options will be grayed-out. Also, you'll see a message that "the ability to change some options has been disabled". See Firefox Updates, Data Collection & Use, etc.

Done!

Sorry for the length, I wanted to be somewhat thorough. I used the Complex file so the settings I found in Options, about:config, and about:policies might differ for you.

HTH

I've added the installer preserving this folder in both Firefox and Firefox64 for the upcoming releases built from today forward.

I haven't looked at this in several months, and I don't remember what behavior it has been doing/not-doing, but after having to click "Not Now" many times recently, I decided to take a look at my situation again. The Firefox and Firefox64 folders have the requisite distribution folder, and the policies.json file within it is as follows:
{
　"policies": {
　　"DisableAppUpdate": true
　}
}

But about:policies only says this (which I don't set and have never even heard of):
Certificates　　ImportEnterpriseRoots　　true

Has Mozilla done something new to prevent what we're trying to do? I'm currently on version 67.0.4.

Argh! While we can't seem to stop Firefox Portable from giving that update prompt (the policies.json trick gave us short-lived relief but hasn't worked for over a year), now Thunderbird Portable has started doing the same thing! Any solutions in 2020?

I tested Firefox 78 & 80, the policies.json appears to be working, the policies are in place and active. The About dialog states "the system administrator has disabled updates".

As expected, Mozilla changed or removed a few of my about:config tweaks, I had to add one of em, the rest I'm looking into.

Disabling Pocket was easier with 78 versus 80, FF 80 kinda disabled Pocket but I had to uncheck the feature from Options-Home (IIRC) - Pocket went away.

If I should be hounded to update either browser to the latest version I'll update the thread but it seems to me Firefox 78 & 80 are A-OK with abiding by the policies... time will tell.

Is there any further effort being made on this? It has been well over a year since the previous comment (which was also by me), but I still have to keep saying "Not now" over and over again in both Thunderbird and Firefox until PortableApps releases an update - am I the only one? Currently Thunderbird is in that limbo state - I have 78.14.0, which PortableApps thinks is current, but Thunderbird itself wants to update to 91.3.2 and hounds me about it. That's a huge difference in versions, but I don't want to risk updating outside of PortableApps. I just want Thunderbird (and Firefox) to stop hounding me.

I also need a fix for this super annoying popup notification. I don't see a way to subscribe to this thread without commenting.

need also to subsribe.
don't know if there is still some about:config working.
will say if have one.

Firefox Portable only gives users access to "Update Automatically" or "Check But Do Not Update".

I suppose "Update Automatically" will break the "Portable Apps" version. And those of us in this thread know that the "Check But Do Not Update" feature works just fine, along with it's 'nag bubble'.

The instructions provided elsewhere in this thread (Note: some assembly required - snark) does not turn off the 'nag bubble'. The Mozilla Preferences feature does show that update checks are failing. Perhaps that is due to some of my tweaking in the "About:Config" tool.

FYI - Mozilla Firefox is my last straw in Internet browser choices. Anything from Google or based on tech from Google is OUT, and that seems to rule out a lot of stuff. I use a PC not a Mac, so anything from Apple is a NO GO. Any of the "privacy oriented" derivatives of Mozilla always seem to have some repugnant feature that drives me away, either the 'forced UI' choice, or lack of ESR channel, or "hidden features" that cannot be disabled.

It is so sad to see the overall Internet browser ecosystem drop to a level of [NotSafeForForum, NSFF, words go here].