X
Tap here to go to the mobile version of the site.

Support Forum

Firefox create too much profiles.

Posted

Hello,

after last update 67.0.2 (64-bit) or 67.0.0 (64-bit) in user profile we can see like this

installs.ini


[308046B0AF4A39CB] Default=Profiles/2nsvjtmx.default-release Locked=1


profiles.ini


[Install308046B0AF4A39CB] Default=Profiles/wt03pnep.default

[Profile0] Name=default IsRelative=1 Path=Profiles/wt03pnep.default Default=1

[General] StartWithLastProfile=1 Version=2


And three profiles in profile folder. Total 600 Mb! For roaming profile this is a to large profile.

What does it means information in ini files? Why user have more the one profile. They claim that their settings are not saved after logoff. Should we stop using Firefox for roaming profiles?

Hello, after last update 67.0.2 (64-bit) or 67.0.0 (64-bit) in user profile we can see like this installs.ini ------------------------------------ [308046B0AF4A39CB] Default=Profiles/2nsvjtmx.default-release Locked=1 ------------------------------------ profiles.ini ------------------------------------ [Install308046B0AF4A39CB] Default=Profiles/wt03pnep.default [Profile0] Name=default IsRelative=1 Path=Profiles/wt03pnep.default Default=1 [General] StartWithLastProfile=1 Version=2 ------------------------------------ And three profiles in profile folder. Total 600 Mb! For roaming profile this is a to large profile. What does it means information in ini files? Why user have more the one profile. They claim that their settings are not saved after logoff. Should we stop using Firefox for roaming profiles?
Attached screenshots

Chosen solution

I see three profiles listed in the screenshot. An old 4cayblil.default profile (last used 04.06) that was likely replaced by a new dedicated profile 2nsvjtmx.default-release profile (last used 05.06) when you updated to Firefox 67. Then a new wt03pnep.default profile has been created probably because you noticed that you had switched to the default-release profile. If you lost personal data then look in the oldest profile (4cayblil).

Firefox 67 and later can use a dedicated profile for each of the Firefox update channels and will lock the profile, so it can only be used by Firefox in a specific installation folder. For Release versions this profile would be a xxxxxxxx.default-release profile, profiles used in older Firefox versions usually used a xxxxxxxx.default profile (a refresh adds a time stamp).

The installs.ini file stores a hash of the installation path and locks a profile for this specific path to prevent other Firefox installations from using it. The profiles.ini file still stores all registered profiles and their paths and can include the data stored in installs.ini.

Read this answer in context 1
Quote

Additional System Details

Application

  • User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36

More Information

cor-el
  • Top 10 Contributor
  • Moderator
17278 solutions 156183 answers

Chosen Solution

I see three profiles listed in the screenshot. An old 4cayblil.default profile (last used 04.06) that was likely replaced by a new dedicated profile 2nsvjtmx.default-release profile (last used 05.06) when you updated to Firefox 67. Then a new wt03pnep.default profile has been created probably because you noticed that you had switched to the default-release profile. If you lost personal data then look in the oldest profile (4cayblil).

Firefox 67 and later can use a dedicated profile for each of the Firefox update channels and will lock the profile, so it can only be used by Firefox in a specific installation folder. For Release versions this profile would be a xxxxxxxx.default-release profile, profiles used in older Firefox versions usually used a xxxxxxxx.default profile (a refresh adds a time stamp).

The installs.ini file stores a hash of the installation path and locks a profile for this specific path to prevent other Firefox installations from using it. The profiles.ini file still stores all registered profiles and their paths and can include the data stored in installs.ini.

I see three profiles listed in the screenshot. An old 4cayblil.default profile (last used 04.06) that was likely replaced by a new dedicated profile 2nsvjtmx.default-release profile (last used 05.06) when you updated to Firefox 67. Then a new wt03pnep.default profile has been created probably because you noticed that you had switched to the default-release profile. If you lost personal data then look in the oldest profile (4cayblil). *https://support.mozilla.org/en-US/kb/recovering-important-data-from-an-old-profile Firefox 67 and later can use a dedicated profile for each of the Firefox update channels and will lock the profile, so it can only be used by Firefox in a specific installation folder. For Release versions this profile would be a xxxxxxxx.default-release profile, profiles used in older Firefox versions usually used a xxxxxxxx.default profile (a refresh adds a time stamp). The installs.ini file stores a hash of the installation path and locks a profile for this specific path to prevent other Firefox installations from using it. The profiles.ini file still stores all registered profiles and their paths and can include the data stored in installs.ini. *https://support.mozilla.org/en-US/kb/dedicated-profiles-firefox-installation *https://blog.mozilla.org/2019/01/14/moving-to-a-profile-per-install-architecture/
Was this helpful to you? 1
Quote
Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.