Firefox Portable

I've always been able to check for updates manually in Firefox Portable. However, now when I go to Help and About Firefox, the program no longer checks for updates. It says Updates disabled by your system administrator.

Is there a way to fix this so I can check for updates again and continually updating the program?

Thanks!

I know there's been more than a few posts about multiple instances of FFP but I don't recall seeing one that was my specific question. Most involved different versions or an installed version and a portable version. I am wondering if it is possible to run multiple FFPs of the same version just from different folders. I have tried the AllowMultipleInstances=true parameter in the past but that just resulted in a link being clicked from outside FFP opening Firefox in a new window void of extensions and theme and all that. That isn't what I am after.

The installers for Firefox 84.0.1 in the languages Simplified Chinese and Turkish are corrupt / truncated on the server.
The Installers for other languages are all about 120 MB in size, but those two are 102 MB and 94 MB in size respectively and are failing their integrity check.

The hashes of the downloaded files are matching the listed hashes, but the files are corrupt, so, the problem is server side, not just a bad / incomplete download.

We are working with Firefox Portable ESR 78.6.0 on windows 10 OS

We need to detect the close event to override it, or disable it when the user try to close the browser from the taskbar.

With an older version of Firefox Portable ESR (52.2.0), we used the following code to detect browser closure:

var observerService = Components.classes ["@ mozilla.org/observer-service;1"OUND.getService(Components.interfaces.nsIObserverService);

observerService.addObserver (this, "quit-application-granted", false);

Running Firefox Portable 84.01 on a Windows 10 machine.

Suddenly yesterday, when launching Firefox Portable, I receive the error: "Another instance of Firefox is already running. Please close other instances of Firefox before launching Mozilla Firefox, Portable Edition."

Good Day,
Thank you for making this great product available. I have been able to get it working here on a few machines. To get it working I had to install Adobe Flash on the machines on which it will run. Then after Flash is installed I copy NPSWF64_32_0_0_465.dll to the firefoxportable\data\plugins folder.

Is this what others are doing? With this method will Flash continue to work post Jan 12? My understanding is that Adobe has a switch already present to prevent their installed FlashPlayer from working on Jan 12th.

Thank you

I see the article for Mozilla Firefox ESR, Portable Edition 68.9.0: https://portableapps.com/news/2020-06-03--firefox-portable-esr-68.9.0-re...

The download link in the article goes to the main page for Firefox ESR which (unfortunately for me) has the most recent version (78.6.0): https://portableapps.com/apps/internet/firefox-portable-esr

I've copied folder of the Firefox portable to another computer. Then I executed the application, setting of the update is reverted to automatic setting.
I re-set it to manulally at every time. How it can set to completely disable the update setting?

I just updated Firefox Developer Portable to 85.0 Beta 1, and I'm having the following issues in the address bar.

1. When you click Page Actions (3 horizontal dots), the pop-up shows an empty box.
2. Bookmark this page star button is missing.

Things I've tried.

1. In a new Windows Sandbox. I installed a new copy of Firefox Developer Portable 85.0 Beta 1 and still get the same behavior.
2. In a new Windows Sandbox. I installed a new copy of Firefox Developer 85.0b1 directly from Mozilla and do not get the same behavior. Everything works as it should.

In the latest Firefox (regular) and FF ESR the updating options have been changed. Now the only "option" is "automatically install updates". If you try to tick the other option "check for updates but let you choose to install them" this warning box pops up "Firefox encountered an error and didn’t save this change. Note that setting this update preference requires permission to write to the file below. You or a system administrator may be able resolve the error by granting the Users group full control to this file.

Could not write to file: {$path}"