Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus
Résolu Archivé

32 to 64bit ESR Migration

Brian a répondu
Brian

Hello,

We are trying to automate updating Firefox ESR from 32bit to 64bit. There seems to be an issue with getting user's profiles to properly migrate for ESR. If we do a plain 32bit uninstall and 64bit installation, a new "default-esr-1" profile gets created (which is expected behavior from these Mozilla docs for new installs). But, when we set the MOZ_LEGACY_PROFILES=1 policy, this reverts to using the "default" profile instead of "default-esr" profile that was previously in use.

Are there any known ways around this which does not require user intervention to manually change back to the "default-esr" profile?

Thank you

Hello, We are trying to automate updating Firefox ESR from 32bit to 64bit. There seems to be an issue with getting user's profiles to properly migrate for ESR. If we do a plain 32bit uninstall and 64bit installation, a new "default-esr-1" profile gets created (which is expected behavior from these Mozilla docs for new installs). But, when we set the MOZ_LEGACY_PROFILES=1 policy, this reverts to using the "default" profile instead of "default-esr" profile that was previously in use. Are there any known ways around this which does not require user intervention to manually change back to the "default-esr" profile? Thank you

Toutes les réponses (2)

Additional observations... This is when use the "FirefoxSetupx.x.xesr-en-US-x64 /S" install command. When manually executing the x64 file, it performs an in place upgrade to 64 bit and keeps the same profile active (rather than stay side by side with the 32 bit version and create a new profile).

Solution choisie

Workaround is to add this install switch to force the 64bit version to overwrite in the 32bit folder: /InstallDirectoryPath="C:\Program Files (x86)\Mozilla Firefox"