為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Switching architectures from x86 to x64

  • 2 回覆
  • 1 有這個問題
  • 48 次檢視
  • 最近回覆由 Mike Kaply

more options

Hello -

I'm looking to upgrade clients in my enterprise environment from x86 to x64. I've consulted the KB at https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles and I'm wondering if there is a way to launch this profile manager at launch, or a way to import the bookmarks from x86 to x64. In my testing, I have not seen this Profile Manager launch automatically on first run of an install of x64.

Hello - I'm looking to upgrade clients in my enterprise environment from x86 to x64. I've consulted the KB at https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles and I'm wondering if there is a way to launch this profile manager at launch, or a way to import the bookmarks from x86 to x64. In my testing, I have not seen this Profile Manager launch automatically on first run of an install of x64.

被選擇的解決方法

If you upgrade with Firefox, it will keep it in the Program Files (x86) directory, so this won't be an issue.

Alternatively you can use the LegacyProfiles policy or MOZ_LEGACY_PROFILES environment variable and the same profile will continue to be used.

從原來的回覆中察看解決方案 👍 0

所有回覆 (2)

more options

The main problem in this case that you launch a Firefox version that is installed in a different installation folder. Current Firefox releases lock a specific profile to a specific installation folder. You can see this in the profiles.ini file and in the installs.ini file. Firefox will create a new default profile because the 64 bit version is installed in a different location.

See:


I will move the thread to Firefox for Enterprise support.

more options

選擇的解決方法

If you upgrade with Firefox, it will keep it in the Program Files (x86) directory, so this won't be an issue.

Alternatively you can use the LegacyProfiles policy or MOZ_LEGACY_PROFILES environment variable and the same profile will continue to be used.