I have seen some other questions on here (e.g., this and this), plus plenty of other pages on the web, offering various strategies for installing and running multiple versions of Firefox side by side. All of them are cumbersome and/or fragile.
They all basically boil down to one of two ways, each with its own problems.
-
Use Portable Firefox.
- Problem: Portable Firefox only has one profile. To use multiple profiles, you have install a separate program which creates a separate profile and has to be launched separately (i.e., you aren't managing the profiles using the normal Firefox profile manager).
-
Install a second version into its own directory.
- Problem: All such installed versions use the same appdata directory, which means they see the same profiles. You must make sure you launch each version with a profile specially designated for it, or it may modify or corrupt a profile that was being used by another version. This means that using multiple profiles for any of the installed versions is again a risky proposition, as if you accidentally select the wrong profile, one version may step on the toes of another.
What I would like is a way to really, truly, honest-to-goodness install multiple independent versions of Firefox. By independent I mean that they should never in any way know about, interact with, or interfere with one another. I should be able to create multiple profiles for any version, using that version's own profile manager, and the versions should have separate appdata directories, so that the entire set of profiles associated with any version is completely separate from the entire set of profiles associated with any other version.
I can envision two ways of doing this, based on the two ways I mentioned above:
-
If there were a real Portable Firefox, that would be great. By "real" I mean a portable version that actually has all the capabilities of a normally installed version, including in particular the profile manager and the ability to add/remove/select profiles without using an extra layer of PortableApps infrastructure.
-
If I could install a normal version of Firefox but give it a different appdata directory, then it wouldn't stomp on any of the profiles of any other versions.
Is there any way to do either of these things, or otherwise get myself to a situation where I have multiple versions of Firefox installed, each of which can do everything that a normally-installed version would do, but do it all totally independently of and without any effect whatsoever on any other versions that happen to be installed?
Best Answer
A bit late on replying to this question, but anyway there goes my 2 cents.
I've been using the multi-version + multi-profile dance with FF since version 2.0 or 3.0. An added bonus is profile portability between different computers and different Windows versions. Let's see the basics:
Install as many FF versions as you wish to, each in its own directory. 'C:\Program Files (x86)' is no longer the best option under Win7 (due to UAC), but I keep using it even so (out of WinXP bad habits). In this machine, for example, I have:
Have a dedicated folder to store your collection of FF profiles, with one sub-folder for each profile (hopefully named in whatever meaningful way, in order to avoid confusion). Again, in this machine I have:
Go inside each of the install directories and make multiple copies of firefox.exe (OFC with different names – again, meaningful names!). For example ...
C:\Program Files (x86)\Firefox_31\firefox.exe
What follows requires a healthy dose of attention to detail; not really complicated, but it needs lots of copy-pasting and careful search & replace: have a collection of .BAT files that will MATCH some given version of FF with some given profile folder. I have some very long and convoluted .BATs which I'm not posting in full right now, but some key elements follow:
The above setup allows you to run multiple combos of versions+profiles SIMULTANEOUSLY (OFC as long as the available RAM will allow).
Now, for each profile, you NEED to have all the following valid; otherwise, imminent BORK is guaranteed to occur, not only within one particular PROFILE folder but also within one particular INSTALL folder. You have been warned!
about:config
: extensions.update.enabled = falseHeavily recommended as a GLUE to the whole strategy:
More or less recommended (don't let the 'security experts' learn of this), depending OFC on your (mis)behaved browsing habits: resist the temptation to have ALL of FF's latest versions. You'd have to install each one in its own directory and have a NEW profile directory to match, as well.
Whenever you feel the urge to have a brand-new FF version, you'd have to follow this procedure:
clone your previous .BAT file into a new one, where you'll carefully replace the contents of the following variables:
run the newly cloned & edited .BAT file, so that a RENAMED firefox.exe from the NEWLY installed FF version will reference the NEW just-filled PROFILE folder (while OFC totally ignoring and preserving the previous FF versions and each of their corresponding profiles)
Since FEBE's settings contain a DESTINATION folder for profile backups, you should now change it from its previous value, so that from now on any new FEBE backups will get stored in a folder different from the backups of the previous FF version.
Generate TWO FEBE backups: one itemized and one all-in-one. Verify that both backup sets ended up in the NEW destination folder (i.e., NOT together with the backups from the previous profile-version combo).
Create – and test – a shortcut somewhere, pointing to the newly tested .BAT file.
Have a sigh of relief, and/or blame myself for such a complicated and involved procedure.
Cheers & good luck!
Edit on July 5, 2015, to clarify some issues raised in a comment by the OP to my proposed solution above:
A. If I "run one of the various firefox_xxx.exe files without specifying a profile on the command line" ... it would [try to] run the 'default' FF profile of my Windows user, i.e., the profile located inside "C:\Users\myusername". Results would be random, depending on which version is the current FF .exe running the default profile and on which version was the previous FF .exe that attempted a previous run on same default profile. Remembering, in my scheme of things, that:
B. The "check for updates" button is not meant to be pressed in my scheme of things. However, in a hypothetical situation where it would be pressed, the following would happen, approximately:
C. As I expect to have demonstrated above, your statement "If updating one install affects other installs ..." is not true, and therefore your conclusion "the installs are not fully independent" is invalid.
D. The lockpref approach which you've linked to is aimed to be used in an environment where there's an 'admin' which needs to prevent undesired actions by 'common users'. My solution, OTOH, is a construct created by a geek for its own use, and as such it assumes not only strict and careful usage parameters, but also an absence of other users who might bork it thru careless usage.