You are here

Firefox Portable

firefox67 static and portable with different profiles

Submitted by willi uebelherr on May 26, 2019 - 3:11am

Dear friends, i found here in the forum similar questions, but mostly with only portable FF67
My working environment:
- windows 10
- static FF67 installed
- portable FF67 with PortableApps

All users on this computer use the static version. I only use PortableApps with FF, TB and others. With version FF66, i opened the portable FF and all external link requests opened in a new tab in the portable instance.
Now, with version 67 it changed. A link start the static version with the default profile.

Firefox Portable 67-71 (standalone) leaves behind an empty folder called mozilla-temp-files.

Submitted by AlexMail on May 23, 2019 - 9:21pm

An example of steps to reproduce the issue on Windows PC:

1. Start Firefox.
2. Print a copy of any website.
3. Exit Firefox.

Upon exiting Firefox, an empty folder called mozilla-temp-files is left behind in \AppData\Local\Temp.

Another example to reproduce the issue is to watch a few YouTube clips and then exit Firefox.

The above behavior is observed on all Firefox Portable 67 and newer.

Running multiple instances/profiles at the same time

Submitted by lwc on May 22, 2019 - 7:05pm

v67 added support for running Multiple Instances:

A myriad of new features help make Firefox easier to use:
Users will be able to run different Firefox installs side by side by default so that you can run the beta and release versions simultaneously

https://www.mozilla.org/en-US/firefox/67.0/releasenotes/

Firefox 67+ launches with default profile when opening links from other applications

Submitted by armbold on May 15, 2019 - 6:17am

I have been using Firefox Portable on Windows for years, set as the system's default browser.
A few days ago I updated to version 67 (Developer edition), and I noticed the following:
when I click on a link from another application (for example a Thunderbird email) then Firefox starts but it uses a new profile (instead of my profile).
This is annoying beacuse I don't have access to bookmarks/extensions in this profile. In previous versions it would get launched with my profile.
Does it happens to you guys? Any workaround?

Portable Firefox Problem After New Update

Submitted by realxj on May 15, 2019 - 1:14am

This problem have happen after the fiasco of Add-On in Firefox. I have install a new Portable Firefox ver. 66.0.4, after open it, it is automatically updated itself before i know it. After restarting the browser can't be open anymore if i don't click yes to temporarily copied to local hard drive on dialog box that appear saying "the browser appears to be running from a location that is read-only. Would you like to temporarily copy it to the local hard drive and run it from there?" If i click yes and open the browser, it seem the browser have broken. Bookmarks can't be saved and imported.

[Fixed] Addons Icons Menu Dissapear when Moving Firefox to New Location

Submitted by gholygo on May 10, 2019 - 1:34am

When I move the portable firefox directory to a new location, after restarting Firefox, the addons icons menu bar has gone.
I can still access the addons through the Tools>Extensions menu and see that they are still installed. However, I cannot access the options for them that way.

Is there a file where the location of extensions/addon icons or shortcuts is stored that is maybe not getting rewritten when I transfer the portable firefox directory to another location or usb drive?

Many thanks.

Warning: 66.0.4 Resets Automatically Install Updates Setting

Submitted by Abraxian on May 6, 2019 - 10:14am

I was just stepping through my Options settings after the install of Firefox Portable 66.0.4 and noticed that 66.0.4 had in the 'General' settings enabled the setting "Automatically install updates (recommended)". I never ever allow Firefox Portable to do that, I only ever use the setting "Check for updates but let you choose to install them". So 66.0.4 must have reset that setting to the Mozilla default on install.

Same thing happened in my fully installed Firefox 66.0.4.

Pages